automate patch-level release #1515
Closed
Conversation
This file contains 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
By this commit, we're now able to cut a patch-level release easily by using github labels. Some labels are available: "release/patch" - If the pull request has this label and gets merged, new patch version will be released. "release/candidate" - If the pull request has this label and gets merged, new version will be released as release-candidate. "release-note" - The automation script will automatically generate CHANGELOG entry. - The script will collect pull requests for generating entry by whether the label has been attached or not.
Closed
jkowens
approved these changes
Aug 20, 2019
| load "ci/release.rb" | ||
| sh <<-SH | ||
| echo "---\n:rubygems_api_key: #{ENV['RUBYGEMS_API_KEY']}" > ~/.gem/credentials | ||
| cat ~/.gem/credentials |
There was a problem hiding this comment.
Does this need output here?
There was a problem hiding this comment.
I totally forgot about this, but seems a debug code to me
There was a problem hiding this comment.
I'll try to take a look in a few days.
There was a problem hiding this comment.
I just went over this again, and noted our conversation here. Good to see your avatar again. Hope things are good! 👋
|
Closing this as we should use Github Actions now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello @sinatra friends!
I've been working on the automation recently, and right now I confirmed the automation works correctly, so I would like to get your feedback!
Background: #1510
This change offers two features.
CHANGELOG.mdandVERSIONfor next patch level release.rake release:allto publish all gems.We're now able to cut a patch-level release easily by using github labels:
release/patchv2.0.6)release/candidatev2.0.6.rc)release-noteBefore merging this, we need to check some points for reducing troubles.
We need to check that required access has been granted for @sinatra-bot.
@sinatra-bot should be:
collaborator(read/write) into this repositorysinatra,sinatra-contribandrack-protectiongems in rubygems.org.Then, I have a private key for @sinatra-bot, and it must be encrypted and be committed to this repository for accessing to this repository from travisci, so we need encrypt the private key by
travis encrypt-file [PEM]. You can see more details in .travis.yml and release.sh.Last, thanks for taking a look at this pull request. If you have more time, please review the codes, the structure, and actual automation workflow at https://github.com/sinatra-bot/sandbox.
I'm looking forward to get your feedback!
Thanks,