Repository navigation
Bump the version to 0.6.0 - #172
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
[Unreleased]in CHANGELOG.md holds 49 entries since v0.5.0 (a 0.x pre-release number, asdocs/releasing.mddescribes). This is the bump step of that document; nothing is tagged or released by merging it.Change
scripts/bump-version.sh --date 2026-11-12 0.6.0, then the generators:VERSION, thevar versiondefault inserver/main.goand inapp/cmd/re-psn-app/main.go, the version span inREADME.md.CHANGELOG.md: the Unreleased entries move under## [0.6.0] - 2026-11-12; a fresh empty Unreleased stays above.site/index.html,site/action.html,site/discuss.htmlandsite/data.json, regenerated bypython3 tools/site.py(they show the version and the newest changelog section), as in the v0.5.0 bump.One commit. No other change. The heading's date is the day of this bump; the tag is made separately and later, so the date may be one the maintainer wants to change before the merge.
Tests
scripts/check-release.shpasses for 0.6.0 andTestVersionAgreespasses (it covers the server and the desktop app defaults).go vetandgo test -race ./...inserver/, andgo vetandgo test ./...inapp/, pass.python3 tools/features.py,python3 tools/site.py --check,python3 tools/repo_check.pyandscripts/check-deploy.shpass.scripts/release-notes.sh 0.6.0builds the notes from the 49 entries (every entry has an area label); it was run on the same change, not published.Not in this change
No tag, no release, no change to
docs/features.tsv: itssincecolumn is updated after the tag, in the step that follows the release (docs/releasing.md, step 9). The Actions dry run of the release workflow has not been run.Overlap
None open.
Developed with AI agent assistance.