Repository navigation
Record the unlogged changes since 1.0.0 in the changelog - #44
Merged
Merged
Conversation
Five merges since the 1.0.0 release changed what users or contributors see without a CHANGELOG entry: the README image (#29), the CONTRIBUTING build step (#28), the dev prerelease wording (#33), the CONFIG.md permission text (#34) and the PluginDescriptionFile manifest tests (#41). The Unreleased section even logged a fix to the image's caption without ever logging the image. Add the missing entries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
Self-review (rubric)The Copilot reviewer could not be added (
Judgment call (not blocking):
This review was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener). drafted by Claude on behalf of Daniel Stephenson |
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.
Summary
A documentation accuracy sweep (Stage A) found no drift between the docs and the source.
USER_GUIDE.md,COMMANDS.md,CONFIG.md,README.mdandCONTRIBUTING.mdwere each checked againstMain.java,plugin.yml,pom.xml,minecraft-versions.jsonand the three workflows. The one gap was inCHANGELOG.md: five merges since the 1.0.0 release changed what users or contributors see but have no## [Unreleased]entry, although every other doc change since #37 has been logged there. The section even listed a fix to the README image's caption (#38) without ever listing the image.Entries added under
## [Unreleased]:/flyoutput (Add a hero image of real in-game output to the README #29);CONTRIBUTING.mdbuild-and-test step (Tell contributors to build and test before opening a PR #28);CONFIG.mdexplanation of who may use/fly(Say how the fly permission is granted in CONFIG.md #34).plugin.ymlwithPluginDescriptionFileand check name andapi-version(Check plugin.yml with the parser a server uses #41).dev(State exactly which pushes republish the dev prerelease #33).Each entry was written from
git showof the merge it cites, not from the PR title alone.No tracking issue: the gap was found during the sweep.
Validation
mvn -B clean packagewas run locally on this branch and passed:DocumentationTest3/3,FlyCommandTest4/4,PluginManifestTest6/6, 0 failures and 0 errors, withtarget/FlyCommand-1.0.1.jarbuilt. No test readsCHANGELOG.md, so this only confirms nothing else broke.git show --statand the diffs of 48bd1f7 (Add a hero image of real in-game output to the README #29), 06467e1 (Tell contributors to build and test before opening a PR #28), 98a0464 (State exactly which pushes republish the dev prerelease #33), 1a1e71f (Say how the fly permission is granted in CONFIG.md #34) and 353d7f9 (Check plugin.yml with the parser a server uses #41).CHANGELOG.mdchanges (+7 lines). No Java, manifest or workflow files are touched.Issues not picked this cycle
/flydoes to creative, spectator and airborne players): needs someone to confirm the behaviour on a real server and a maintainer to choose between documenting it and changing the code. Not doable autonomously.pom.xmlstuck at release version1.0.1): needs a maintainer to decide whether to publish 1.0.1 or go back to-SNAPSHOT. These entries stay under[Unreleased]until that decision is made.This PR description was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).
🤖 Generated with Claude Code
drafted by Claude on behalf of Daniel Stephenson