-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multiple releases per day in the smithy-rs repository #3875
Conversation
A new generated diff is ready to view.
A new doc preview is ready to view. |
This reverts commit fa0a188.
@@ -202,7 +208,7 @@ jobs: | |||
# to retry a release action execution that failed due to a transient issue. | |||
# In that case, we expect the commit to be releasable as-is, i.e. the changelog should have already | |||
# been processed. | |||
git fetch --unshallow | |||
git fetch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, specifying --unshallow
in a repository with fetch-depth: 0
will fail with the following error:
fatal: --unshallow on a complete repository does not make sense
A new generated diff is ready to view.
A new doc preview is ready to view. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good, two questions around if some validations are possible and one about improving an error message
Motivation and Context
Currently, we can only make one
smithy-rs
release per day, and this restricts our ability to respond to urgent issues. This PR lifts that limitation, allowing us to make multiple releases per day.Description
The core of this change is in the
render
subcommand ofchangelogger
. When generating a date-based release tag, it now checks for existing tags on the same day. If a tag already exists, therender
subcommand will append a numerical suffix to ensure the new tag is unique.In fact, appending a numerical suffix to make a release tag unique has been a workaround in our release pipeline (outside the
smithy-rs
repository) for quite some time. With the changes in this PR, we can eliminate that temporary solution from the release pipeline.Now that
changelogger
requires access to previous tags, CI steps that rungenerate-smithy-rs-release
need to checkout thesmithy-rs
repository with all tags (fetch-depth: 0
is for that purpose).Testing
changelogger
changelogger
into thinking that it has to bump a release tag)By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.