Skip to content

feat: use semver with floating major tag - #152

Open
reedham-aws wants to merge 2 commits into
aws-actions:mainfrom
reedham-aws:versioning
Open

reedham-aws wants to merge 2 commits into
aws-actions:mainfrom
reedham-aws:versioning

Conversation

@reedham-aws

Copy link
Copy Markdown

Which issue(s) does this change fix?

#112, #151

Description

Previously, this repository had been using a floating major tag and had been force pushing that tag for every new commit. This a) didn't follow the principles of semantic versioning (because there was only ever major releases) and b) didn't allow for immutable releases. This commit changes this by creating a new release for a specific version every time a semver tag is pushed. To maintain the floating tag if a user wants the latest version, we still move around the v<major version> tag.

I've also enabled immutable releases in the settings of the repository.

In #112, it's suggested by @roger-zhangg to use versioning based off of SAM CLI's version, but I opted against that here because of the ability to pin a SAM CLI version like so:

- uses: aws-actions/setup-sam@v3
  with:
      version: 1.170.0

Without the version specified, the version will update to latest regardless.

Checklist

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 License.

@reedham-aws
reedham-aws requested a review from a team as a code owner October 23, 2026 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant