chore(release): binding-only re-release 0.0.37-beta.7-1#107
Closed
jagguji wants to merge 1 commit into
Closed
Conversation
Publishes the regenerated bindings that are already on main but never shipped: 0.0.37-beta.7 is unchanged blend, so the bindgen bumps (beta.4/beta.5, #106) regenerated src/ without a version change — and release.yml skips publishing a version that's already on npm. This `-N` suffix (per the sync checklist's binding-only re-release convention) gives a fresh, higher prerelease so the improvements actually reach consumers: - BlendChart, ChartV2 bindings (previously missing) - descriptive helper-type names - rescript-webapi moved to peerDependency (#104) Same blend version (0.0.37-beta.7); bindings only. Publishes under the `beta` dist-tag. Build green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
Author
|
Closing — pivoting from the beta.7 line to a beta.5 binding-only re-release (0.0.37-beta.5-1), since the consuming repo is on the beta.5 blend line. That ships via the new on-demand re-release workflow (#108) off release/blend-0.0.37-beta.5-1, not through main. |
jagguji
added a commit
that referenced
this pull request
Jul 10, 2026
Validate rescript-bindgen PR #132 ("fix/107-error-any-flag", f00318d) against
Blend. PR 132 stops the generator from silently emitting a polymorphic `'a`
for an UNRESOLVABLE type reference (the TS checker's error-`any` from a broken
import in a package's .d.ts); it now emits a flagged `string` placeholder with
a 🛑 BROKEN note pointing at the broken import. Also refines report wording and
bumps the upstream benchmark's blend pin to 0.0.37-beta.8.
No effect on Blend at beta.8: src/ byte-identical. The PR's target case
(ThemeProvider.foundationTokens: ThemeType via the shadowed `../tokens` path)
RESOLVES in beta.8 — foundationTokens binds to
TokensTypes.foundationTokenType, not `'a` — so the new error-any branch never
fires here. 222/222 usable, 0 review, 0 broken, compiles clean (298 modules),
passes format:check.
Defensive/honesty improvement upstream (no more silent unsound `'a`); a no-op
for us until/unless a future blend version ships an unresolvable import.
Upstream: 90/90 golden (one new error-any case) + compile, smoke, 9/9
benchmark baselines pass.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jagguji
added a commit
that referenced
this pull request
Jul 10, 2026
Validate rescript-bindgen PR #134 ("fix/107-unresolved-intrinsic", c24f769),
a one-line follow-up to #107: the error-any guard now also matches TS's
`unresolved` intrinsic, not just `error` — some unresolvable-reference paths
report the sibling name. Broadens the same flag-don't-emit-silent-'a fix.
No effect on Blend at beta.8: src/ byte-identical. As with #132, the broken-
import case it guards against doesn't occur here (ThemeType resolves), and no
Blend type produces the `unresolved` intrinsic either. 222/222 usable, 0
review, 0 broken, compiles clean (298 modules), passes format:check.
Upstream: 90/90 golden + compile, smoke, 9/9 benchmark baselines pass.
Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Version-only bump
0.0.37-beta.7→0.0.37-beta.7-1to publish the regenerated bindings that are already onmainbut never shipped.Why this is needed
0.0.37-beta.7is already on npm. The recent bindgen bumps (beta.4/beta.5, #106) regeneratedsrc/without changing the package version (blend version is unchanged), sorelease.ymlskipped re-publishing (it won't re-publish an existing version). Result: the improvements sit onmaingit but aren't installable from npm.The
-Nsuffix is the binding-only re-release convention from the sync checklist — a fresh, higher prerelease of the same blend version.What ships in this re-release
BlendChart+ChartV2bindings (were missing — fix(sync): pin devDependency for beta syncs + decouple stable-poll baseline #92/chore(deps): bump @juspay/rescript-bindgen to ^1.2.5-beta.0 #93 forwardRef fix)rescript-webapi→peerDependency(fix(deps): make rescript-webapi a peerDependency to dedupe in consumers #104) — fixes the "Duplicated package" error in consumersMechanics
0.0.37-beta.7-1semver-sorts above0.0.37-beta.7(numeric7< alphanumeric7-1), so thebetadist-tag moves forward correctlyrelease.ymlmaps this prerelease →betadist-tag (no workflow change)betaConsume it (after merge)
Build green; diff is version-only (package.json + lock).
🤖 Generated with Claude Code