Correct a CHANGELOG note for 0.2.0-rc.1
release / release (push) Successful in 7m19s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
adamandClaude Opus 5.5 committed 2026-10-09 15:29:01 +00:00
1 parent e1bcb5d479
commit d961cb8792
1 file changed
+3 -2
+3 -2
View File
@@ -93,8 +93,9 @@ All notable changes to Jarl are documented here. The format follows
- `jarld version`, `jarl --version`, `jarl status` and `jarl whoami` give - `jarld version`, `jarl --version`, `jarl status` and `jarl whoami` give
a version number only for release builds. Other builds say they are a version number only for release builds. Other builds say they are
development builds and how far past the last tag they are: `dev development builds and how far past the last tag they are: `dev
ca0f148b78b6 (3 commits after v0.2.0-rc.1)`. In 0.2.0-rc.1 they still ca0f148b78b6 (3 commits after v0.2.0-rc.1)`. Before, they printed the
printed `0.2.0-rc.1 (ca0f148b78b6)`. version and the commit (`0.2.0-rc.1 (ca0f148b78b6)`), which read like a
release.
- `make deb` gives development builds their own package version after - `make deb` gives development builds their own package version after
the last tag (`0.2.0~rc.1+git3.gca0f148`, plus the build time with the last tag (`0.2.0~rc.1+git3.gca0f148`, plus the build time with
uncommitted changes). Installing one over the RC or an older build is uncommitted changes). Installing one over the RC or an older build is