Repository navigation
docs: backfill 4.2.9, 5.0.0 and 5.0.1 into the changelog - #213
Merged
Merged
Conversation
The root CHANGELOG.md jumped straight from 5.1.0-beta to 4.2.8. Three releases that actually shipped were missing from it: 4.2.9, 5.0.0 and 5.0.1. They were never lost, just recorded elsewhere. The root file is inherited from the strapi-plugin-rest-cache repository and stopped being maintained at 4.2.8, and the 5.x entries were kept in packages/plugin-rest-cache/CHANGELOG.md instead. Releases are now cut from the root, so the root file is the changelog and the gap became visible the moment 5.1.0-beta landed on top of it. Reconstructed from what shipped: the v5.0.0 GitHub release for the Strapi 5 migration and its breaking changes, the package changelog for 5.0.1, and the commits between v4.2.8 and v4.2.9. Two links are corrected too. The 5.1.0-beta heading compared monorepo-v5.0.1...monorepo-v5.1.0-beta, and neither tag exists - that naming came from the component bug fixed in #212. It now compares against v5.0.0. And 5.0.1 is no longer a compare link at all: it was published to npm without a tag or release, so there is nothing to compare against. Co-Authored-By: Claude <noreply@anthropic.com>
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.
Good catch. The root
CHANGELOG.mdjumped straight from5.1.0-betato4.2.8:4.2.9, 5.0.0 and 5.0.1 were all absent.
Why
Nothing was lost — it was recorded elsewhere. The root file is inherited from
the
strapi-plugin-rest-cacherepo and stopped being maintained at 4.2.8; the5.x entries were kept in
packages/plugin-rest-cache/CHANGELOG.mdinstead.Releases are now cut from the root, so the root file is the changelog — and
the gap only became visible once
5.1.0-betalanded on top of it.Reconstructed from what actually shipped
packages/plugin-rest-cache/CHANGELOG.md; npm publish datev5.0.0GitHub release — Strapi 5 migration and its breaking changesv4.2.8andv4.2.9The 5.0.0 breaking changes are worth having written down rather than only in a
release body: Couchbase provider removed, all three packages renamed under
@strapi-community/, and no Strapi 4 support.Two dead links fixed
5.1.0-betaheading comparedmonorepo-v5.0.1...monorepo-v5.1.0-beta.Neither tag exists — that naming came from the component bug fixed in
fix(release): tag releases v<version>, not monorepo-v<version> #212. Now compares against
v5.0.0.5.0.1is no longer a compare link. It was published to npm without a tag ora release, so there was nothing on the other end of it.
Result is continuous:
5.1.0-beta → 5.0.1 → 5.0.0 → 4.2.9 → 4.2.8 → …Note
The per-package
CHANGELOG.mdfiles are now orphaned — release-please onlymaintains the root one under the single-release config. Worth deciding
separately whether to delete them or leave them as a historical record; they
are not wrong, just frozen.
🤖 Generated with Claude Code