chore: release dds 0.4.1 - #33
Merged
Merged
Conversation
jlc488
added a commit
that referenced
this pull request
Sep 3, 2026
* ci: release on every push to main through changesets/action Until now release.yml only ran when someone pushed a `dds-v*` tag by hand. Nothing created that tag: two release commits (0.4.0 in #31, 0.4.1 in #33) sat on main while npm stayed at 0.3.0, and the landing that was waiting on site-kit 0.4.1 shipped behind a `<select>` instead of the flag picker. The workflow now runs on every push to main, passes the same verification gate as before, and hands off to changesets/action: with changeset files waiting it opens the "chore: release dds" version PR; with none waiting (the version PR just merged) it runs `changeset publish`, which publishes whatever is on main but not yet on npm and tags each package. Re-runs are safe because versions already on npm are skipped. Provenance and the NPM_TOKEN secret are unchanged. The README pair describes the flow. * ci: let the release verifiers pass when the version is already on npm verify:solid:release and verify:site-kit:release end with `npm publish --dry-run`, and npm refuses a dry-run of a version that is already published. That made CI on main red from the moment a release went out until the next version bump — exactly the state the new release workflow runs in on every push. The pack, the manifest and the fresh-consumer install are what these gates check; an "already published" answer from the registry is now logged and counted as passed, and every other dry-run failure still throws. verify:release never hit this because it runs npm offline.
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.
Summary
.changeset/flags-subpath.mdpatch changeset (fix(site-kit): flag data on a ./flags subpath + review follow-ups #32, merged to main at 12edb60), bumping the fixed release group (dds-tokens,dds-css,dds-icons,dds-solid,site-kit) from 0.4.0 to 0.4.1.pnpm-lock.yamlafterchangeset version.tests/foundation-contracts.test.mjsthat still expected0.4.0.Test plan
pnpm run verify— build + check across all workspace packages, greenpnpm run verify:site-kit:release— foundation core tests, dds-solid/site-kit builds, pack + publish dry-run + fresh consumer import, greendds-v0.4.1after merge to publish