chore(release): v0.13.0 - #50
Merged
Merged
Conversation
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.
What
Version bump only:
0.12.0->0.13.0. No source changes.Why this release matters
This is the release that carries #49 to the registry. Everything currently published -
0.3.0through0.12.0- is marked UNLICENSED on npm, so nothing already out there islegally usable by anyone outside the org. Those versions stay UNLICENSED permanently;
0.13.0isthe first MIT-licensed build, and the first to ship a LICENSE file in the tarball.
It also carries the rest of the external-readiness work: the npm-facing description, 16 keywords,
homepage-> ds.agentage.io,bugsURL, the rewritten README and the banner.Publish path
The squash-merge subject will be
chore(release): v0.13.0 (#50), which matches this repo'srelease-gate regex (
^chore\(release\)), sopublish.ymlfires on merge and runsnpm publish --access public --provenanceafter a fullverify.Note this repo's gate is not affected by the
agentage/clisquash-subject gotcha - the^chore\(release\)alternative is already present here. If the gate somehow skips anyway, thefallback is
gh workflow run publish.yml -R agentage/design-system.Verification
npm run verifyand the containerized Playwright suite both ran green on #49 at this exact tree(43/43 e2e including axe WCAG A/AA, 434 unit tests). This branch adds only the version field, and
publish.ymlre-runsverifybefore publishing regardless.Merging this publishes to npm. That is the intent of the PR.