Release the Python package's vendored client, two minors behind - #53
Merged
Conversation
`nimblebrain-synapse` 0.3.0 ships `_assets/synapse-ui.iife.js` built at `@nimblebrain/synapse` 0.12.0. The vendored asset in this repo has moved with every npm release since, but `pyproject.toml` never did — and the PyPI artifact is what a Python consumer actually gets, so they have been on a 0.12.0 client through 0.12.1, 0.12.2, 0.13.0 and 0.14.0. Nothing caught it. CI gates `__client_version__` against `package.json` and diffs the vendored IIFE against the current build, both of which pass on a tree whose Python version is stale; what is ungated is the *released* PyPI artifact against the released npm one. The two packages version independently and are tagged independently (`nimblebrain-synapse-v*` vs `v*`), so an npm release simply does not carry the Python one along. 0.4.0 rather than 0.3.1: the Python API is untouched, but the client this package exists to ship changes cascade behaviour for any component CSS that declares one of the backed color tokens, and adds host font faces.
mgoldsborough
added a commit
that referenced
this pull request
Jul 28, 2026
Three releases landed on main after this branch's last push: the cascade layer (#50) and its framing (#52), cut as npm v0.14.0, and the Python package's catch-up release (#53), cut as nimblebrain-synapse-v0.4.0. npm 0.14.0 is published, so the warm removal stays under `[Unreleased]` and releases as 0.15.0. The migration note's unaffected range widens to `^0.11.0`-`^0.14.0` to match what consumers can now be pinned to. The vendored Python IIFE is rebuilt from the merged source rather than resolved to either side, since #50 changed the build output. Both nimblebrain-synapse-v0.4.0 and v0.14.0 are tagged at commits that predate this merge, so both shipped artifacts still carry the warm channel their changelogs describe. theme-defaults.ts auto-merged: #50's cascade-layer docblock and this branch's correction to the neutrality claim are different hunks.
This was referenced Jul 28, 2026
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.
The gap
PyPI
nimblebrain-synapse0.3.0 ships_assets/synapse-ui.iife.jsbuilt at@nimblebrain/synapse0.12.0. The vendored asset in this repo has moved with every npm release since —maincurrently carries the 0.14.0 build — butpython/pyproject.tomlnever moved, so nothing published it. A Python consumer has been on a 0.12.0 client across four npm releases (0.12.1,0.12.2,0.13.0,0.14.0).Why nothing caught it
ci.ymlhas two relevant gates and both pass on a tree with a stale Python version:__client_version__is gated againstpackage.json.Neither compares the released PyPI artifact to the released npm one. The packages version independently and tag independently (
nimblebrain-synapse-v*vsv*), so taggingv0.14.0does not carry Python along — by design, but with no signal when the two drift.Worth considering as a follow-up: a gate that fails when
main's__client_version__differs from the client version in the latestnimblebrain-synapse-v*tag, i.e. "the Python package owes a release."Why 0.4.0, not 0.3.1
The Python API is untouched. But the client this package exists to ship changes observable behaviour:
documentElementinto@layer synapse-defaults, so a component's own:rootrule now wins where it previously needed!importantor could not win at all.@font-facedescriptors arrive oversynapse/fontFaces.A consumer whose component CSS declares one of the backed tokens sees a different result after this bump. That is a minor.
Verification
pytestgreen — 18 passed. No source change beyond the version and the changelog entry; the vendored asset is already current onmainand gated by CI's freshness diff.Release after merge with a
nimblebrain-synapse-v0.4.0tag.