1
0
mirror of https://github.com/sharkdp/bat.git synced 2025-01-31 10:11:07 +00:00

Remove post-release section

This commit is contained in:
David Peter 2021-08-22 09:37:24 +02:00 committed by David Peter
parent 01fbedc246
commit 11bd523f7e

View File

@ -4,11 +4,11 @@
See this page for a good overview: https://deps.rs/repo/github/sharkdp/bat See this page for a good overview: https://deps.rs/repo/github/sharkdp/bat
- [ ] Optional: update dependencies with `cargo update`. This is also done - [ ] Optional: update dependencies with `cargo update`. This is also done by
by dependabot, so it is not strictly necessary. dependabot, so it is not strictly necessary.
- [ ] Check for outdated dependencies (`cargo outdated`) and decide for each - [ ] Check for outdated dependencies (`cargo outdated`) and decide for each of
of them whether we want to (manually) upgrade. This will require changes them whether we want to (manually) upgrade. This will require changes to
to `Cargo.toml`. `Cargo.toml`.
## Version bump ## Version bump
@ -18,8 +18,8 @@ See this page for a good overview: https://deps.rs/repo/github/sharkdp/bat
`grep '^\s*MIN_SUPPORTED_RUST_VERSION' .github/workflows/CICD.yml`. `grep '^\s*MIN_SUPPORTED_RUST_VERSION' .github/workflows/CICD.yml`.
- [ ] Update the version and the min. supported Rust version in `README.md` and - [ ] Update the version and the min. supported Rust version in `README.md` and
`doc/README-*.md`. `doc/README-*.md`.
- [ ] Update `CHANGELOG.md`. Introduce a section for the new release and prepare - [ ] Update `CHANGELOG.md`. Introduce a section for the new release and
a new (empty) "unreleased" section at the top. prepare a new (empty) "unreleased" section at the top.
## Update syntaxes and themes (build assets) ## Update syntaxes and themes (build assets)
@ -55,9 +55,4 @@ See this page for a good overview: https://deps.rs/repo/github/sharkdp/bat
- [ ] Check if the binary deployment works (archives and Debian packages should - [ ] Check if the binary deployment works (archives and Debian packages should
appear when the CI run for the Git tag has finished). appear when the CI run for the Git tag has finished).
- [ ] Publish to crates.io by running `cargo publish` in a *clean* repository. - [ ] Publish to crates.io by running `cargo publish` in a *clean* repository.
The safest way to do this is to cloning a fresh copy. The safest way to do this is to clone a fresh copy.
## Post release
- [ ] Optional: Inform package maintainers about the update:
- https://www.archlinux.org/packages/community/x86_64/bat/