-
Notifications
You must be signed in to change notification settings - Fork 188
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
Less release steps #1793
base: main
Are you sure you want to change the base?
Less release steps #1793
Conversation
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.
this file needed to be outside of the workflows
directory in order for the automation to be able to update it, so I went ahead and moved all of the scripts to the same place
env: | ||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
run: | | ||
current_version=$(grep "PREVIOUS_SPECIFICATION_VERSION=v.*" \ |
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.
Should this be getting the value ofLATEST_SPECIFICATION_VERSION
and replacing it on PREVIOUS_SPECIFICATION_VERSION
as the guide said?
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.
I'm not sure I totally follow, I think I removed the need for that step by only maintaining a single version in the file (which aligns with the version currently used in the links)
Automatically sends a PR to update spec repo links whenever there is a spec release.
Example PR: trask#7