feat: publishing via changeset#10
Merged
Merged
Conversation
The custom PublishPackages pipeline (conventional-commit version strategy, changelog writer, GitHub release, dependency locker) and Verdaccio testing setup are replaced by @changesets/cli. This aligns with how @webiny/di publishes and simplifies the release workflow to: yarn changeset → merge → automated publish via GitHub Actions. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Guided TDD workflow for adding features to @webiny/stdlib. Encodes the DI pattern, file conventions, testing patterns, and the golden rule that existing tests must never be modified. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Replace the custom publish pipeline with Changesets, aligning
@webiny/stdlibwith how@webiny/dialready publishes.What changed
Removed the entire custom publish infrastructure:
scripts/features/PublishPackages/— conventional-commit version strategy, changelog writer, npm registry client, GitHub release via Octokit, dependency locker (19 files)scripts/features/PublishToVerdaccio/— local Verdaccio publish flow (5 files)publishPackages.ts,publishToVerdaccio.ts__tests__/scripts/PublishPackages/(3 test files).verdaccio.yamlconfig@octokit/rest,semver,@types/semver,verdaccioAdded Changesets:
.changeset/config.json— public access, main branch, standard changelog format.github/workflows/publish.yml— automated publish triggered after CI passes onmain, usingchangesets/action@v1yarn releasescript (yarn build && changeset publish)@changesets/cliUpdated:
package.jsonversion set to0.0.1(Changesets manages the real version)AGENTS.md— replaced publish/verdaccio/changelog docs with Changesets workflow.gitignore— removedhtpasswdand.verdaccioentriesWhy
The custom pipeline worked but was a lot of code to maintain for a single-package repo. Changesets is battle-tested, handles versioning + changelog + npm publish + GitHub releases out of the box, and is already proven in
@webiny/di.Release workflow going forward
yarn changesetbefore opening a PR — describe the change and pick the bump type.changeset/*.mdfile with the PRmain, the publish workflow creates a "Version Packages" PRSetup required
NPM_TOKENsecret to the GitHub repository settings