Skip to content

Release with verwalter instead of changesets/action - #2279

Merged
lukasIO merged 8 commits into
mainfrom
claude/release-process-verwalter-aa568f
Nov 19, 2026
Merged

lukasIO merged 8 commits into
mainfrom
claude/release-process-verwalter-aa568f

Conversation

@lukasIO

@lukasIO lukasIO commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

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}) and CHANGELOG.md continue without a gap. The pending changesets carry over unchanged.

Change

  • verwalter.toml describes one package, livekit-client, at the root, published to npm.
  • release.yaml runs 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:
    • build type-checks and builds the merge commit before any tag exists, and hands dist to the publish job.
    • release creates the tag and the draft GitHub release.
    • publish publishes that dist to npm and makes the release public. All publish runs share one concurrency group, so an older run cannot move the latest dist-tag back.
    • verify fails if the tag, the public GitHub release or the npm version is missing.
    • docs uploads the API docs. It runs only for a final version released from main.
  • A run of release.yaml by hand takes a ref input. Set it to the release tag: verwalter refuses to publish source that changed since the tag.
  • release-pr.yaml regenerates the release PR on every push to main.
  • pre-release.yaml opens an rc PR against the branch it runs on. An rc publishes under the next dist-tag.
  • changeset-check.yaml fails a PR that changes the package without a changeset. The internal label skips the check.
  • The snapshot release stays as a job in release.yaml. It sets 0.0.0-<prefix>-<timestamp> with npm version before the build, so the bundle reports the snapshot version.
  • RELEASING.md describes the workflows and what to do when a release fails.
  • .changeset/config.json, @changesets/cli, @livekit/changesets-changelog-github and the ci:publish script are removed.

Different afterwards:

  • Nobody pushes fixes onto the release PR. Each push to main regenerates it.
  • The tag is created before the npm publish. If the publish fails, re-run the failed jobs: the publish skips a version npm already has.
  • The changelog entries come from verwalter, not from the changelog plugin.

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-lockfile passes after the removal of the changesets packages.
  • All four workflow files parse as YAML.

For reviewers

  • The verwalter-release GitHub App must be installed on this repository and must be able to bypass the rulesets on main and on tags.
  • At merge, close the open changesets release PR Version Packages #2274 and delete its branch changeset-release/main.
  • The changeset-bot App can be removed: changeset-check.yaml does that job now.

Not done yet

  • No release workflow ran in CI. The first push to main after the merge is the first real run.
  • A run by hand from an unmerged release/* branch is not blocked. An environment with required reviewers on the publish job would close that.

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@lukasIO lukasIO self-assigned this Nov 16, 2026
@changeset-bot

changeset-bot Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 5db0296

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

size-limit report 📦

Path Size
dist/livekit-client.esm.mjs 118.36 KB (0%)
dist/livekit-client.umd.js 127.88 KB (0%)
dist/core/core.mjs 79.79 KB (0%)

devin-ai-integration[bot]

This comment was marked as resolved.

…hed version

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ish per tag

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@1egoman

1egoman commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

FYI, some of the comments that shijing left on the livekit/node-sdks#784 PR also may apply here:

  1. A manual re-run can publish newer code under an old version (xianshijing-lk's P1). This is the most important one.
  • When you start release.yaml by hand, every checkout uses merge_commit_sha || github.sha, which is the branch's latest commit.
  • Suppose a failed run left tag v2.x.y at commit A, and main has since moved to B without another version bump. A manual run builds B's dist and publishes it as 2.x.y.
  • verwalter v0.30.0 only checks that the tag exists. The fix in verwalter (Fail a publish whose source changed since its tag verwalter#105) is still an open PR and hasn't been released.
  • node-sdks fixed this by adding a ref input, using merge_commit_sha || inputs.ref || github.sha in every checkout, and adding a comment that says to use "Re-run failed jobs" first and to run by hand only with ref set to the release tag.
  • Release with verwalter instead of changesets/action #2279 should do the same in its build, release, publish and docs jobs, and bump the verwalter pin once Remove unnecessary line #105 ships.
  1. Two publish runs can overlap and move npm's latest back to an older version (non-blocking).
  • Release with verwalter instead of changesets/action #2279 uses group: publish-, so runs for different versions don't wait for each other. An older run can finish last and move latest back to its version.
  • node-sdks switched to one shared group:
    concurrency:
    group: npm-publish
    cancel-in-progress: false
    queue: max
    A waiting run then checks out only after the running one ends, sees the newer tag, and verwalter gives the older version a different dist-tag instead of latest.
  1. Docs deployment isn't limited to main (part of xianshijing-lk's P2).
  • In Release with verwalter instead of changesets/action #2279, the docs job checks only that livekit-client was published and that outcomes doesn't contain -rc.. It doesn't check the branch.
  • A stable publish started by hand from a maintenance branch would overwrite the docs site, which holds only one version.
  • node-sdks added github.event.pull_request.base.ref == 'main' || github.ref == 'refs/heads/main' to the docs job's condition. The risk is lower here, because release PRs are only opened from main, but adding the same guard costs little.
  • The other half of P2 (a release of only the other package) doesn't apply, since this repo has one package.

lukasIO and others added 2 commits November 18, 2026 10:42
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ve latest back

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
lukasIO and others added 3 commits November 18, 2026 17:59
…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>
@lukasIO
lukasIO merged commit 69ef4ae into main Nov 19, 2026
10 checks passed
@lukasIO
lukasIO deleted the claude/release-process-verwalter-aa568f branch November 19, 2026 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants