For general contribution and community guidelines, please see the community repo.
- Fork the project
- Clone your fork
- Make local changes to your fork by editing files
- Commit your changes
- Push your local changes to the remote server
- Create new Pull Request
From here your pull request will be reviewed and once you've responded to all feedback it will be merged into the project. Congratulations, you're a contributor!
- Examine the changelog and decide on the version bump rank (major, minor, patch).
- Change the title of Unreleased section of the changelog to the target version.
- Be sure to add the date (ISO 8601 format) to the section header.
- Add a new, empty Unreleased section to the changelog.
- Remember to update the references at the bottom of the document.
- Update
VERSION
andversion.go
files to reflect the version change. - Commit these changes.
Bump version to x.y.z
is an acceptable commit message. - Push your changes to a branch, and get the PR reviewed and merged.
- Tag the version on the master branch using
git tag -s vx.y.z -m vx.y.z
. Note this requires you to be able to sign releases. Consult the GitHub documentation on signing commits to set this up. - Push the tag:
git push vx.y.z
(orgit push origin vx.y.z
if you are working from your local machine).
- Create a new release from the tag in the GitHub UI.
- Add the changelog for the current version to the release description.
- Retrieve the following artifacts from the Jenkins build on the tagged branch,
and attach them to the release:
SHA256SUMS.txt
summon-aws-secrets-darwin-amd64.tar.gz
summon-aws-secrets-darwin-arm64.tar.gz
summon-aws-secrets-freebsd-amd64.tar.gz
summon-aws-secrets-linux-amd64.tar.gz
summon-aws-secrets-netbsd-amd64.tar.gz
summon-aws-secrets-openbsd-amd64.tar.gz
summon-aws-secrets-solaris-amd64.tar.gz
summon-aws-secrets-windows-amd64.tar.gz
- Create a PR in
cyberark/homebrew-tools
to updatesummon-aws-secrets.rb
formula using the filedist/summon-aws-secrets.rb
retrieved from Jenkins artifacts.- Make sure the SHA hashes for the artifacts match the values in the
SHA256SUMS.txt
file attached to the release.
- Make sure the SHA hashes for the artifacts match the values in the