release: public wrappers v0.60.0 - #10
Merged
Merged
Conversation
Pins the wrappers to runtime 0.60.0, which is where the buyer picker goes from 4 languages to 37 and stops inlining locale dictionaries into the bundle. Without this the wrappers stay pinned to `@seatlayer/js: "0.59.0"` EXACTLY, so every React, Vue and Angular customer would keep resolving the old runtime and see none of it — the languages would be live on the CDN and on npm for direct `@seatlayer/js` consumers only. This is step 2 of the forced release order and the release is not finished without it. Verified against the real published 0.60.0, not a workspace link: build, typecheck, 32 tests, attw/publint, check:version and the public boundary all green.
`minimumReleaseAge` rejects any package published in the last 24h, including ours: the v0.60.0 wrapper release failed in CI seconds after the runtime went out, because @seatlayer/core@0.60.0 and @seatlayer/js@0.60.0 were five minutes old. The repo already has the intended escape hatch — `minimumReleaseAgeExclude` lists every prior first-party version, 0.53 through 0.59, and `pnpm install` appended 0.60.0 to it. The previous commit simply left the file out. The policy still applies in full to every third-party dependency, which is what it is for.
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
2 participants
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.
Pins the React, Vue and Angular wrappers to runtime 0.60.0 — the release
where the buyer picker goes from 4 languages to 37 and stops inlining locale
dictionaries into the bundle.
Without this the wrappers stay pinned to
@seatlayer/js: "0.59.0"exactly,so every React, Vue and Angular customer keeps resolving the old runtime and
sees none of it. The languages would be live on the CDN and on npm for direct
@seatlayer/jsconsumers only.Also adds
0.60.0tominimumReleaseAgeExclude. That policy rejects anythingpublished in the last 24h, including our own packages — the first release run
failed because core/js were five minutes old. The allowlist is the repo's
existing mechanism for first-party versions (0.53 → 0.59 are already there); the
policy still applies in full to every third-party dependency.
Verified against the real published 0.60.0, not a workspace link: build,
typecheck, 32 tests, attw/publint,
check:versionand the public boundary.Already published from tag
v0.60.0— this bringsmainin line.