docs: update release instructions#1440
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1440 +/- ##
============================================
+ Coverage 73.06% 73.09% +0.02%
- Complexity 4381 4382 +1
============================================
Files 475 475
Lines 14244 14244
Branches 1447 1447
============================================
+ Hits 10408 10412 +4
+ Misses 2977 2974 -3
+ Partials 859 858 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
seratch
left a comment
There was a problem hiding this comment.
Thanks! I've added additional information about the signing process prep.
.github/maintainers_guide.md
Outdated
| * Make sure there are no build failures at https://github.com/slackapi/java-slack-sdk/actions | ||
| * Set a new version | ||
| * If you don't have `gnu-sed`, run `brew install gnu-sed` first | ||
| * If you don't have `gnu-sed`, run `brew install gnu-sed` & `brew install gnupg` first |
There was a problem hiding this comment.
Just installing GnuPG is not enough. Before making the release, there are a few steps to complete:
- Set up your key: https://central.sonatype.org/publish/requirements/gpg/
- Make sure if your account has the permission to make releases under com.slack groupId (note that this page requires login as the account)
- Update your $HOME/.m2/settings.xml
- generate user token: https://central.sonatype.org/publish/generate-token/
- set the user token id/password: https://central.sonatype.org/publish/publish-manual/#signing-components
There was a problem hiding this comment.
Good point I moved this to prerequisites 💯
mwbrooks
left a comment
There was a problem hiding this comment.
✅ Everything reads well and the instructions are clear. I've left one minor suggestion on formatting, but it's a non-blocker.
Co-authored-by: Michael Brooks <[email protected]>
This PR aims to update the release instructions in the maintainers guide
Category
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you agree to those rules.