-
Notifications
You must be signed in to change notification settings - Fork 143
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
Automate Release Process with New Versioning Script #602
base: main
Are you sure you want to change the base?
Conversation
WalkthroughThe changes introduce a new Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 1
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- release.sh (1 hunks)
Additional comments not posted (6)
release.sh (6)
1-4
: LGTM!The code changes are approved.
6-18
: LGTM!The code changes are approved.
20-33
: LGTM!The code changes are approved.
35-44
: LGTM!The code changes are approved.
50-60
: LGTM!The code changes are approved.
62-67
: LGTM!The code changes are approved.
# Prompt user to create a release manually on GitHub | ||
echo "Please create a release on GitHub from the tag here: https://github.com/pyupio/safety/releases/new" | ||
echo "Attach the relevant binaries to the release before publishing." | ||
|
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.
Consider automating the release creation.
The code changes are approved. However, consider automating the release creation step using the GitHub CLI to further streamline the process.
You can use the gh release create
command to create a release from the pushed tag. For example:
# Create a release on GitHub from the tag
echo "Creating a release on GitHub..."
gh release create "$NEW_VERSION" --title "Release $NEW_VERSION" --notes "Release notes for version $NEW_VERSION"
This command creates a new release with the specified title and release notes. You can also attach binaries to the release using the --asset
flag.
This PR introduces a new script to automate our release process. The script streamlines version tagging, building, and publishing, significantly improving the efficiency of our release workflow. By automating these steps, we reduce manual errors, save time, and enhance our overall velocity. This improvement will allow the team to focus more on development and less on repetitive release tasks, ultimately accelerating our delivery of new features and fixes.
Summary by CodeRabbit
New Features
Bug Fixes