chore(release): bump feat/workspace-team to 0.16.2 - #6188
Merged
Conversation
The published beta feed is self-inconsistent: metadata.json carries
baseVersion 0.16.1 alongside betaVersion 0.16.2-beta.144, because
0.16.2-beta.144 was published with an explicit release_version override
while every manifest on this branch still said 0.16.1. Every subsequent
beta build now fails its own consistency check:
[release-beta] beta metadata.json baseVersion 0.16.1
does not match betaVersion 0.16.2-beta.144
`force` does not help — it only waives "base must exceed latest stable",
not the baseVersion/betaVersion match.
Raising the branch's base version to 0.16.2 makes the next beta
(0.16.2-beta.145) consistent with its own metadata, and removes the need
to pass force at all. Same 18 manifests the release bot touched in
23f9fca; test fixtures that mention 0.16.1 as data are left alone, as
that commit also left them.
Contributor
🚀 Landing page previewThis PR is deployed to a Cloudflare Pages preview — not staging or production:
|
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.
Why
The beta feed cannot be published to any more. Both attempts tonight died at
Prepare beta metadata:The first is waivable with
force. The second is not: this afternoon0.16.2-beta.144was published using an explicitrelease_versionoverride while every manifest on this branch still read0.16.1, which left the publishedmetadata.jsonself-inconsistent. Any later build validates that file and refuses.This is my own mistake coming back — the override produced a version number the repo could not substantiate.
What changed
0.16.1→0.16.2in the same 18 manifests the release bot touched in23f9fcaac(chore(release): bump main to 0.16.2 ahead of stable 0.16.1). Nothing else. Two test files mention0.16.1as fixture data (WhatsNewPopup.test.tsx,packaged-launcher-update-loop.test.ts); that commit left them alone and so does this one.After this,
0.16.2-beta.145is consistent with its own metadata andforceis no longer needed for the base-version check.What users will see
Nothing directly. It unblocks publishing dogfood betas from this branch with a version number that does not go backwards — the auto-resolver currently proposes
0.16.1-beta.1, which is behind the0.16.2-beta.144already circulating.Surface area
package.json/ workspace manifestsNotes for the reviewer
This raises the branch only;
mainremains at0.16.1and is untouched. If the intent is instead to bumpmainon the normal release cadence, close this — but then tonight’s beta cannot be published with a forward-moving version.