Repository navigation
Release with verwalter instead of changesets/action - #2279
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
Contributor
size-limit report 📦
|
…hed version Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
1egoman
approved these changes
Nov 16, 2026
…ish per tag Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Contributor
|
FYI, some of the comments that shijing left on the livekit/node-sdks#784 PR also may apply here:
|
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ve latest back Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…s-verwalter-aa568f # Conflicts: # pnpm-lock.yaml
…ify job, RELEASING.md Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <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
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.
This repository releases with changesets/action today. This PR moves the release to verwalter, which keeps one release PR open from the changeset files and tags, releases and publishes after that PR merges. Version numbers, tags (
v{version}) andCHANGELOG.mdcontinue without a gap. The pending changesets carry over unchanged.Change
verwalter.tomldescribes one package,livekit-client, at the root, published to npm.release.yamlruns after the release PR merges, on any base branch. The file name stays the same, because npm trusted publishing names it. Its jobs run in this order:buildtype-checks and builds the merge commit before any tag exists, and handsdistto the publish job.releasecreates the tag and the draft GitHub release.publishpublishes thatdistto npm and makes the release public. All publish runs share one concurrency group, so an older run cannot move thelatestdist-tag back.verifyfails if the tag, the public GitHub release or the npm version is missing.docsuploads the API docs. It runs only for a final version released frommain.release.yamlby hand takes arefinput. Set it to the release tag: verwalter refuses to publish source that changed since the tag.release-pr.yamlregenerates the release PR on every push tomain.pre-release.yamlopens an rc PR against the branch it runs on. An rc publishes under thenextdist-tag.changeset-check.yamlfails a PR that changes the package without a changeset. Theinternallabel skips the check.release.yaml. It sets0.0.0-<prefix>-<timestamp>withnpm versionbefore the build, so the bundle reports the snapshot version.RELEASING.mddescribes the workflows and what to do when a release fails..changeset/config.json,@changesets/cli,@livekit/changesets-changelog-githuband theci:publishscript are removed.Different afterwards:
mainregenerates it.Verified
verwalter status:2.24.1 tag:both release:published registry:yes 8 pending, and the next release PR is for 2.25.0.pnpm install --frozen-lockfilepasses after the removal of the changesets packages.For reviewers
verwalter-releaseGitHub App must be installed on this repository and must be able to bypass the rulesets onmainand on tags.changeset-release/main.changeset-check.yamldoes that job now.Not done yet
mainafter the merge is the first real run.release/*branch is not blocked. An environment with required reviewers on the publish job would close that.🤖 Generated with Claude Code