Repository navigation
Conversation
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
| @@ -0,0 +1,3 @@ | |||
| # Changelog | |||
There was a problem hiding this comment.
So this file will accumulate changelogs or just hold the ones from the last release? Is this a 1:1 copy from the changeset files in the end?
There was a problem hiding this comment.
This will accumulate and end up looking like this https://github.com/livekit/client-sdk-js/blob/main/CHANGELOG.md
| "package.json", | ||
| { path = "package.json", regex = 'releases/tag/v(?<version>[^"]+)' }, | ||
| { path = "README.md", regex = '`#v(?<version>\d[^`]*)`' }, |
There was a problem hiding this comment.
Why is package.json listed here once standalone and once in the { path, regex } pattern? Is the standalone using a default regex?
There was a problem hiding this comment.
exactly. package.json -> version is covered as a well-known default.
Unity's package.json extensions also have the changeLogUrl which isn't part of the plain package.json manifest, so it gets its own regex expression. Jacob has some ideas to make this more robust in the future (regex could match multiple today without anyone noticing).
A release today is a manual sequence: run
Scripts~/prepare_release.pywith the new SDK version, open a PR, then push the tag and write the GitHub release by hand. The release notes depend on what the maintainer remembers. The 2.1.1 notes are one line.Change
verwalter now releases the package.
.changeset/.changeset-check.ymlfails a PR without one, unless it has theinternallabel.mainupdates one release PR (release-pr.yml). It bumpspackage.json, thechangelogUrlin it and the tag example in the README, and writesCHANGELOG.md.vX.Y.Zand creates the GitHub release (release.yml). The tag format does not change, so git URL installs and OpenUPM continue to work.pre-release.ymlopens an rc PR on demand.Scripts~/prepare_release.pynow takes the FFI version only. It still updatesversion.ini, the binaries, the submodule and the protobuf code, but it no longer writespackage.json.CHANGELOG.mdstarts with the next release. Earlier notes stay on the releases page. The README example moves from#v1.3.5to#v2.1.1.The release PR gets the
releaselabel.ci.ymlalready reads that label and tests against the committed FFI binaries, which is correct for a release PR.Verified
verwalter plan: 1 package, 0 pending changesets, no warnings.verwalter status:2.1.1, tag and GitHub release present, up to date.verwalter pr --dry-runwith a temporaryminorchangeset: the release branch movedpackage.json,changelogUrland the README example to2.2.0and added the changelog entry.For reviewers
internallabel and add it to this PR. The changeset check fails until then.releaselabel with "Release PR managed by verwalter".Not done yet
mainafter the merge is the first real run.🤖 Generated with Claude Code