v0.11.2

chore: upgrade actions to Node 24 runtime (SHA-pinned) (#44) Igor Rodionov (@goruha) (#46)

## what

• Bump GitHub Actions references to Node 24 runtimes, SHA-pinned with precise version comments:
  • actions/checkout@v4 → @3d3c42e5... # v7.0.1
  • nick-fields/assert-action@v2 → @0efd6166... # v4.0.1
  • cloudposse/github-action-jq@0.4.0 → @aff18a1f... # v0.4.1 (0.4.0 runs node20; v0.4.1 is node24)

why

• GitHub is deprecating the Node 20 runtime; these refs emit deprecation warnings for every
  consumer and are being force-migrated to Node 24
• SHA pinning with verified tag comments matches the org's supply-chain direction
  (cloudposse/.github#261); every pinned SHA was verified against its upstream tag
• Opened from a fork — direct branch push to this repo is not permitted for this account

references

• https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
• Supersedes Renovate #42 (checkout v7) and #41 (assert-action v4)

still on Node 20

• 1arp/create-a-file-action@0.3 in action.yml — no node24 release exists (latest 0.4 is
  node20); needs replacement, tracked org-wide

🤖 Automatic Updates

Replace Makefile with atmos.yaml Erik Osterman (Cloud Posse) (@osterman) (#37)

## what - Remove `Makefile` - Add `atmos.yaml`

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

Replace Makefile with atmos.yaml Erik Osterman (Cloud Posse) (@osterman) (#35)

## what - Remove `Makefile` - Add `atmos.yaml`

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

Update .github/settings.yml Erik Osterman (Cloud Posse) (@osterman) (#32)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub