-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Prep for v0.19.0 #2016
Prep for v0.19.0 #2016
Conversation
It feels out of place to have between `--acknowledgements` and `--help`.
Note that I introduced a new post-release section since I think we don't want to ship the unreleased section in production releases? Seems better to add that section right after the release has been made, I think? |
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.
Thank you very much. Looks great!
Great! I'll go on and make the release then 👍 I have confirmed that bat v0.19.0 requires users of bat v0.18.3 to rebuild custom assets (which is needed due to lazy-loading of themes):
|
Release checklist
Dependencies
See this page for a good overview: https://deps.rs/repo/github/sharkdp/bat
cargo update
. This is also done bydependabot, so it is not strictly necessary.
for outdated dependencies with
cargo outdated --root-deps-only
anddecide for each of them whether we want to (manually) upgrade. This will
require changes to
Cargo.toml
.Version bump
Cargo.toml
. Runcargo build
to updateCargo.lock
.Make sure to
git add
theCargo.lock
changes as well.grep '^\s*MIN_SUPPORTED_RUST_VERSION' .github/workflows/CICD.yml
.README.md
anddoc/README-*.md
. Check withgit grep -i 'rust.*1\.'
andgit grep -i '1\..*rust'
.CHANGELOG.md
. Introduce a section for the new release.Update syntaxes and themes (build assets)
cargo install -f --path .
) and makesure that it is available on the
PATH
(bat --version
should show thenew version).
assets/create.sh
and check in the binary asset files.Documentation
-h
and--help
textsman
pagePre-release checks
next section).
this, install the latest
bat
version again (to include the new syntaxesand themes).
cargo publish --dry-run --allow-dirty
to make sure that it willsucceed later (after creating the GitHub release).
Release
git tag vX.Y.Z; git push origin tag vX.Y.Z
.This will trigger the deployment via GitHub Actions.
release. Select the new tag and also use it as the release title. For the
release notes, copy the corresponding section from
CHANGELOG.md
andpossibly add additional remarks for package maintainers.
Publish the release.
appear when the CI run for the Git tag has finished).
cargo publish
in a clean repository.The safest way to do this is to clone a fresh copy.
Post-release
CHANGELOG.md
.