Skip to content

Say 2.2.0 where the multistore change says 2.3.0 - #156

Merged
jakwinkler merged 1 commit into
mainfrom
fix/2.2.0-version-mentions
Sep 28, 2026
Merged

jakwinkler merged 1 commit into
mainfrom
fix/2.2.0-version-mentions

Conversation

@jakwinkler

Copy link
Copy Markdown
Contributor

Follow-up to #155. The release was renumbered from 2.3.0 to 2.2.0 before merging, but the corrected wording never made it into the commit, so main shipped docs that name a version that does not exist.

  • Configuration reference: "Renamed in 2.3.0" becomes "Renamed in 2.2.0".
  • FAQ: "Up to 2.2 … From 2.3.0" becomes "Up to 2.1 … From 2.2.0". The old text claimed MageBox sent MAGE_RUN_CODE=default up to 2.2, which 2.2.0 itself contradicts.
  • Two code comments in the config loader and types.

No behaviour change. VERSION and CHANGELOG.md were already correct. The v2.2.0 tag will be placed on this commit so the release is built from correct sources.

🤖 Generated with Claude Code

The release was renumbered from 2.3.0 to 2.2.0 before merging, but the
corrected wording in the configuration reference, the FAQ and two code
comments stayed out of the commit. The FAQ also claimed MageBox sent
MAGE_RUN_CODE=default "up to 2.2", which 2.2.0 itself contradicts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

📦 PR build artifacts

Built from 1705b1a — view run. Artifacts expire in 14 days.

Note: artifact download links require being signed in to GitHub with access to this repository.

@jakwinkler
jakwinkler merged commit bb7df00 into main Sep 28, 2026
12 checks passed
@jakwinkler
jakwinkler deleted the fix/2.2.0-version-mentions branch September 28, 2026 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant