fix: explicitly set tag_name in release workflow#197
Merged
scottschreckengaust merged 3 commits intomainfrom Apr 20, 2026
Merged
fix: explicitly set tag_name in release workflow#197scottschreckengaust merged 3 commits intomainfrom
scottschreckengaust merged 3 commits intomainfrom
Conversation
Without explicit tag_name, softprops/action-gh-release relies on GITHUB_REF being correct at runtime. If anything goes wrong (re-runs, race conditions with tag deletion/recreation), the release ends up untagged (e.g. untagged-bfb61f621c7818a82994). Also pins the CHANGELOG.md link to the tag so it resolves correctly in draft releases before publication.
scottschreckengaust
requested review from
a team,
harmjeff,
raj-jain-aws,
scoropeza and
spraja08
Ensures the contributor statement required by CI is always included when creating PRs via Kiro CLI.
github-actions
Bot
added
the
documentation
leandrodamascena
approved these changes
Apr 20, 2026
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
3 participants
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.
Summary
Fixes the v0.1.8 draft release being created with an
untagged-*slug instead of being associated with thev0.1.8tag, and adds a Kiro steering file to prevent missing the contributor statement in future PRs.Changes
1. Fix release workflow tag association
The v0.1.8 draft release was created as
releases/tag/untagged-bfb61f621c7818a82994instead ofreleases/tag/v0.1.8. This caused the relativeCHANGELOG.mdlink to resolve incorrectly.Root cause:
softprops/action-gh-releasewithout an explicittag_nameparameter relies onGITHUB_REFbeing correct at runtime. Race conditions (tag deletion/recreation) or re-runs can cause the release to end up untagged.Fix:
tag_nameparameter to ensure correct tag associationCHANGELOG.mdlink to an absolute URL with the tag ref2. Add Kiro steering file for PR conventions
Adds
.kiro/steering/pr-conventions.mdso that Kiro CLI always includes the required contributor statement when creating PRs for this repo.Test Plan
v0.1.8tag — it should produce a properly tagged draft releaseBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.