← Back to community index
# contributor·Active

techmannih - @Seve The circuit-to-svg@0.0.429 r...

mention The circuit to svg@0.0.429 release containing the silkscreen fix failed to publish, which is blocking GLTF PR 219; please publish the release.

Started by techmannihSep 22, 20268 messages

Discussion

Last active 2 months ago · plain text
techmannihoriginal post
<@757706909351411845> The circuit-to-svg@0.0.429 release containing the silkscreen fix failed to publish, which is blocking GLTF PR #219; please publish the release.
techmannih
https://github.com/tscircuit/circuit-json-to-gltf/pull/219
Rishabh
What are you talking about?
techmannih
<@809856037376491570> 0.0.428 is published, but its actual npm bundle is missing the silkscreen fix from [#768](https://github.com/tscircuit/circuit-to-svg/pull/768) - The `.428` release used the earlier #766 checkout and built before syncing with updated `main`. - The release attempt for #768 selected `.429`, but [failed with a `package.json` rebase conflict](https://github.com/tscircuit/circuit-to-svg/actions/runs/35649325038). - The [green workflow on the `.428` commit](https://github.com/tscircuit/circuit-to-svg/actions/runs/35649369306) says “No changes detected, exiting”—it didn’t publish a corrected package. - I rechecked npm: `latest` is still `.428`, and `.429` returns 404.
Rishabh
fixed
techmannih
TY!!!
techmannih
<@809856037376491570> Can you check why the Vercel deployment is failing in RunFrame whenever the PCB Viewer version is updated? https://github.com/tscircuit/runframe/pull/5267
techmannih
And I raised a new PR where the Vercel deployment is passing. Can you check if it's the same build issue? https://github.com/tscircuit/runframe/pull/5269

Want to add to the conversation?

Reply in Discord so your notes stay connected to the source.
Continue in Discord ↗