fix: migrate org goreleaser config to v2 schema

[John C. Bland II (johncblandii)]

what

• Migrate the org-wide fallback GoReleaser config (.github/goreleaser.yml, used by
  shared-go-auto-release.yml for repos without their own .goreleaser.yml) to the v2 schema:
  • add version: 2 (required by GoReleaser v2 — configs without it are rejected outright)
  • archives[].format → archives[].formats (v1 field, removed/deprecated)
  • changelog.skip → changelog.disable (v1 field removed in v2)

why

• chore: upgrade actions to Node 24 runtime and enforce SHA pinning #261 bumped goreleaser/goreleaser-action v5 → v7 in shared-go-auto-release.yml; under v7,
  version: latest installs GoReleaser v2, which rejects this v1-era config — so every
  downstream repo relying on the org fallback config would fail its next release
• Discovered empirically in the same migration: github-status-updater, slack-notifier, and
  github-commenter CI broke exactly this way with their repo-local configs (fixed in their PRs);
  repos with their own v1 .goreleaser.yml still need individual migrations
• Validated with the same binary CI installs: goreleaser check (v2.17.1) passes on the migrated
  config

references

• https://goreleaser.com/deprecations/
• chore: upgrade actions to Node 24 runtime and enforce SHA pinning #261

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[mergify]

Important

Cloud Posse Engineering Team Review Required

This pull request modifies files that require Cloud Posse's review. Please be patient, and a core maintainer will review your changes.

To expedite this process, reach out to us on Slack in the #pr-reviews channel.

[Erik Osterman (Cloud Posse) (osterman)]

Approving. Audited the merged file rather than just the diff — all three v1→v2 mappings are correct (version: 2, archives[].formats as a list, changelog.disable) and nothing else in the config is v1-only: builds, checksum, signs, and the full release block are all v2-valid. No rlcp, no builds[].skip.

Two things to keep on the radar, neither blocking:

• archives[].formats landed in GoReleaser v2.4. shared-go-auto-release.yml installs version: latest so this is fine today, but any downstream repo pinning goreleaser-action below v2.4 would break on formats.
• Repos carrying their own v1 .goreleaser.yml are still broken by #261 and need individual migrations. Worth an issue to track the remainder.