-
Notifications
You must be signed in to change notification settings - Fork 194
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
Added version-bump workflow #65
Conversation
Hey Andrew sorry sorry sorry for not picking this up earlier. I missed your message and I do not monitor this repository. I'll get my review glasses on. 👓 |
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've added some initial thoughts! Feel free to poke me on Discord if I go silent again
Signed-off-by: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
a80cde0
to
a35a575
Compare
Signed-off-by: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
@jhaals ready for another review :) |
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.
Nice work @awanlin 👏
Signed-off-by: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
@jhaals ready to approve and merge now 🚀 |
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.
🎉
Awesome! Thanks @jhaals. Now we wait till next Wednesday for the PR 🚀 |
Signed-off-by: Andre Wanlin 67169551+awanlin@users.noreply.github.com
Hey, I just made a Pull Request!
Added a new action/workflow that automates the version bump process to keep the demo site up to date and can also be used as an example for the large Backstage Community.
When this action/workflow runs it will run the
yarn backstage-cli versions:bump
command which will upgrade all the packages as needed and then create a Pull Request with the changes. The PR description will include the new version and links to the release's Changelog and to the Upgrade Helper with current and new version set. There is also a link to the action/workflow that created the PR.Finally a GitHub PAT will need to be provided as this will allow the new version-bump workflow/action to trigger the related CI build to validate the changes. This needs to be added as secret with the name
VERSION_BUMP_TOKEN
and will need "Full control of private repositories" access, but this might be adjusted as I haven't fully tested reduced accessHere's a screen shot of the Pull Request:
Closes #63