Skip to content

v2.7.0

Latest

Choose a tag to compare

@cloudposse-releaser cloudposse-releaser released this 27 Aug 19:24
3bf808a
fix: migrate .goreleaser.yml to GoReleaser v2 config schema Andriy Knysh (@aknysh) (#546) ## what
  • Migrate .goreleaser.yml from the GoReleaser v1 schema to v2:
    • Add version: 2 (required by GoReleaser v2)
    • Rename archives.formatarchives.formats (list; format is deprecated in v2)
    • Rename changelog.skipchangelog.disable (skip was removed in v2)

why

  • The release workflow's goreleaser-action defaults to latest, which now resolves to v2.18.0. GoReleaser v2 only accepts configs declaring version: 2 and failed the release with:
    only version: 2 configuration files are supported, yours is version: 0
    
  • The release job copies this repo's .goreleaser.yml into .configs/repo/ and uses it (it only falls back to the shared cloudposse/.github config when the repo has none), so our local config is what needs to be v2-compliant.
  • No behavioral change to the produced artifacts — only schema/field renames. Validated with goreleaser v2.18.0 check"1 configuration file(s) validated", no errors or deprecation warnings.

references

[!NOTE]
The canonical cloudposse/.github/.github/goreleaser.yml has the same v1-isms and will fail for every repo relying on the shared config now that latest = v2.18.0. A separate upstream fix to cloudposse/.github is warranted; this PR only unblocks this repo (which uses its own config).

Update Atmos to v1.227.0 Andriy Knysh (@aknysh) (#545) ## what
  • Update the embedded Atmos Go library from v1.221.1 to v1.227.0 in go.mod (and go.sum).
  • Add a new row to the Atmos ↔ cloudposse/utils compatibility matrix in docs/versions.md and its README.md mirror: Atmos v1.227.0 → provider v2.7.0.

why

  • Atmos v1.222.0 (PR cloudposse/atmos#2608) removed two public functions this provider depends on (pkg/aws.ExecuteAwsEksUpdateKubeconfig and pkg/utils.JSONToMapOfInterfaces), which pinned the provider to Atmos v1.221.1.
  • Atmos v1.227.0 restores those public API wrappers (PR cloudposse/atmos#2996), so the provider can track current Atmos again.
  • Keeping the embedded Atmos library version aligned with the Atmos CLI is required for deterministic YAML/JSON deep-merge results; the compatibility matrix documents the pairing so downstream users can pin correctly.
  • Validation: go build ./... passes; all internal/... unit suites pass (component, convert, describe, merge, provider, spacelift, stack). The only failing test is the utils_spacelift_stack_config example E2E, which requires a local Terraform dev-override provider build (9999.99.99) — environmental, not a code regression.

references