chore: migrate .goreleaser-plugin.yaml to goreleaser v2 archives schema#176
Merged
scotwells merged 1 commit intoJul 10, 2026
Conversation
Replace the deprecated archives keys (archives.builds, archives.format, archives.format_overrides.format) with their current equivalents (archives.ids, archives.formats, archives.format_overrides.formats) so plugin releases stop emitting deprecation warnings and keep working when a future goreleaser major removes the old keys. Verified with goreleaser 2.16.0: snapshot release produces the same six platform archives with identical names and zero deprecation warnings. Fixes #124 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
scotwells
force-pushed
the
chore/goreleaser-plugin-archives-schema
branch
from
f7ab306 to
9aeb59e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Keeps
datumctl-computeCLI plugin releases reliable. Every plugin release currently emits three goreleaser deprecation warnings, and a future goreleaser major that drops the old keys would break the release pipeline outright — blocking users from receiving CLI plugin updates. Migrating now removes that time bomb with zero change to the published artifacts.Note
This PR targets
feat/datumctl-compute-pluginrather thanmainbecause.goreleaser-plugin.yaml(and the plugin source it builds,cmd/datumctl-compute) only exist on that branch, which is where plugin releases are cut from.What changed
Migrated
.goreleaser-plugin.yamlto the current goreleaser v2 archives schema per https://goreleaser.com/deprecations:archives.buildsarchives.idsarchives.formatarchives.formats(list)archives.format_overrides.formatarchives.format_overrides.formats(list)No other deprecated keys are present in the file (confirmed via
goreleaser checkand a clean release run).Verification
Ran
goreleaser release --snapshot --clean --skip=publish --config .goreleaser-plugin.yaml(goreleaser 2.16.0) before and after the change, re-verified after rebasing onto the latest base branch.Before: three deprecation warnings:
After: zero deprecation warnings,
goreleaser checkpasses, and the snapshot produces the same six platform archives with byte-identical names:golangci-lint run(v2.12.2, the CI-pinned version) reports 0 issues on the rebased head. An earlier revision of this PR carried lint fixes for the branch; those landed on the base branch independently (cb02956), so this PR is now the goreleaser migration only.Fixes #124
🤖 Generated with Claude Code