ci(solid-adapter): add release-solid.yml + document adapter releases#248
Merged
Conversation
…releases
Two changes that complete the release infrastructure for the five
framework adapters:
1. New .github/workflows/release-solid.yml — mirrors release-vue.yml
(Solid uses plain tsc, same build shape as Vue). Triggers on
solid-v* tags. Regenerates adapter sources, fails on git-diff
drift, builds with tsc, publishes @vanelsas/baredom-solid to npm
with --access public, and creates a GitHub Release.
2. Extended docs/RELEASING.md from core-library-only (17 lines) to
cover the adapter release process. Adds:
- Per-adapter workflow table with tag patterns
- 3-step adapter release procedure
- First-time-publish NPM_TOKEN permission section explaining
Automation vs Granular tokens and the 403 / EOTP failure modes
Pre-flight verified locally:
- bb scripts/generate_solid.bb -> 104 wrappers
- git diff --exit-code adapters/solid/ -> clean (workflow's drift guard passes)
- cd adapters/solid && npx tsc -> exit 0
After this PR merges, the adapters can be released with
`git tag <name>-v0.1.0 && git push origin <name>-v0.1.0`. First-time
publish requires confirming NPM_TOKEN permission for the new package
names — see the RELEASING.md section.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 26, 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
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.
Summary
Completes the release infrastructure for the five framework adapters.
What's published vs not (from investigation)
@vanelsas/baredomrelease.yml@vanelsas/baredom-reactrelease-react.yml@vanelsas/baredom-angularrelease-angular.yml@vanelsas/baredom-vuerelease-vue.yml(ready, awaiting tag)@vanelsas/baredom-svelterelease-svelte.yml(ready, awaiting tag)@vanelsas/baredom-solidChanges
New
.github/workflows/release-solid.yml— mirrorsrelease-vue.yml(Solid uses plaintsc, same build shape as Vue). Triggers onsolid-v*tags. Regenerates adapter sources, fails on git-diff drift, builds withtsc, publishes@vanelsas/baredom-solidto npm with--access public, and creates a GitHub Release.Extended
docs/RELEASING.mdfrom core-library-only (17 lines) to cover the adapter release process. Adds:Pre-flight verification (locally)
bb scripts/generate_solid.bb→ 104 wrappers generatedgit diff --exit-code adapters/solid/→ clean (workflow's drift guard will pass)cd adapters/solid && npx tsc→ exit 0After this PR merges
Adapter publishes will be:
First-publish caveat: confirm
NPM_TOKENpermission for the new package names before tagging. If it's a Granular token with a fixed allowlist, the new names need adding on npmjs.com (or grant scope-level write on@vanelsas). See the new RELEASING.md section.Test plan
bb scripts/generate_solid.bbproduces output identical to what's committedgit diff --exit-code adapters/solid/clean — workflow's drift guard will passcd adapters/solid && npx tscexits 0 — workflow's build step will passrelease-vue.yml(Solid is the closest analog — both use plain tsc)svelte-v0.1.0as canary, confirm npm publish succeeds, then push solid and vue tags🤖 Generated with Claude Code