Repository navigation
chore(release): prepare 2.2.0 - #3
Merged
Merged
Conversation
Turn the CHANGELOG Unreleased section into 2.2.0 (2026-11-22) and bring release-dependent wording in docs and docblocks in line with it. No behaviour changes.
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
Prepare the 2.2.0 release: the CHANGELOG
Unreleasedsection becomes2.2.0(2026-11-22), and wording in docs and docblocks that referred to an unreleased version is updated to match. The tag, release and Packagist publication follow after this PR is merged.Type of change
Linked issues
N/A
How was this tested?
Documentation, CHANGELOG and comment changes only; CI runs on this PR.
Breaking changes
N/A (the breaking changes were merged earlier and are listed in the CHANGELOG)
Checklist