You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
pom.xml has sat at release version 1.0.1 since #30 with no v1.0.1 release #36
pom.xml was bumped from 1.0.1-SNAPSHOT to the release version 1.0.1 in #30 (fdedc0e, 2026-10-19), whose commit message says the release "is published only after the candidate passes the boot gate". As of 4997c96 (2026-10-30):
No v1.0.1 tag exists on the repository (git fetch --tags returns only v1.0.0 and dev).
CHANGELOG.md has no ## [1.0.1] heading; the 26.3 support from Support Minecraft 26.3 #25 still sits under ## [Unreleased].
README.md's Project Status still names 1.0.0 as the latest stable release, which is consistent with the missing tag.
After the 1.0.0 release, the build was moved to 1.0.1-SNAPSHOT within minutes by #23, "so development builds are told apart from the installed stable release". That separation has been missing for 11 days.
Decision needed
One of these, to be chosen by a maintainer:
Publish 1.0.1 (if the boot gate is just pending or was never run): run the release, add a ## [1.0.1] - <date> heading to CHANGELOG.md above the current Unreleased entries, update README Project Status, then bump pom.xml to 1.0.2-SNAPSHOT.
Abandon or postpone the 1.0.1 candidate (if it failed the boot gate): set pom.xml back to 1.0.1-SNAPSHOT so dev builds stop claiming the release version.
This cannot be resolved by a docs cycle, because the release is published outside this repository's workflows.
This issue was skipped by the 2026-11-05 FlyCommand dev-loop cycle because it needs the maintainer's choice between publishing 1.0.1 and abandoning the candidate; a docs cycle cannot resolve it. As of 7682da8 the situation described above is unchanged: pom.xml is still at 1.0.1, and git ls-remote --tags shows only v1.0.0 and dev.
One addition for whichever option is chosen: the documentation accuracy PR opened in the same cycle adds a sentence to README.md and USER_GUIDE.md saying 1.0.0 was not booted on Minecraft 26.3. That sentence should be removed when the next stable release is published.
Activity
dmccoystephenson commentedon Nov 5, 2026
This issue was skipped by the 2026-11-05 FlyCommand dev-loop cycle because it needs the maintainer's choice between publishing 1.0.1 and abandoning the candidate; a docs cycle cannot resolve it. As of
7682da8the situation described above is unchanged:pom.xmlis still at1.0.1, andgit ls-remote --tagsshows onlyv1.0.0anddev.One addition for whichever option is chosen: the documentation accuracy PR opened in the same cycle adds a sentence to
README.mdandUSER_GUIDE.mdsaying 1.0.0 was not booted on Minecraft 26.3. That sentence should be removed when the next stable release is published.This comment was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).
drafted by Claude on behalf of Daniel Stephenson