Release 3.1 - #21
Merged
Merged
Conversation
Close the Unreleased heading, set the release string and bump the version so sites see the new build, and mark 3.1 current in the compatibility table. The 2.x upgrade steps are repeated in the 3.1 notes rather than left behind in 3.0's: 3.0 is a day old, so a site still on 2.x now lands here, and it should not have to read back a release to find out that managers gained the reports and that $CFG->cleanup_* lines in config.php are dead. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ugk6HWGJ5gcHdXZUnZ3NZX
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
1 participant
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.
What and why
Closes the
[Unreleased]heading opened by #20 and cuts 3.1.CHANGELOG.md—## [Unreleased]→## [3.1] - 2026-08-31, with a short introversion.php—$plugin->release = '3.1',$plugin->versionbumped to2026083101so sitessee the new build
Upgrading from 2.x, repeated in the 3.1 notes
3.0 is a day old, so a site still on 2.x lands on 3.1 rather than on 3.0. The 3.1 entry now
carries the short version of what that jump involves — the two breaking changes (settings moved
to the
local_cleanup/namespace, step classes renamed and moved) and the four things to checkafterwards (managers can open the reports, only administrators can delete, unlinked files wait
out
ghostgracedays, leftover$CFG->cleanup_*lines inconfig.phpare dead) — with a pointerto 3.0 for the full account. Nobody upgrading
should have to read back a release to find that out.
README.mdis unchanged: its own Upgrading from 2.x section already says all of this, and itslink points at the 3.0 entry, which is still where the complete list lives.
Testing
php -lonversion.php; the changelog is prose. The release workflow's own checks are whatmatter here, and they run on the tag: it validates that the tag matches
$plugin->release(3.1either side) and that
[3.1]appears inCHANGELOG.md. Both are in place.Notes
The tag is not pushed. Pushing
3.1triggers the release workflow, which builds andpublishes the package, so that is left as a deliberate step after this merges.