Closed nbsp closed 2 months ago
on PRs, for each change, add a file to .nanpa/
.kdl, that looks like this:
It'd be great to have automation for this, otherwise it'd be easy for devs to forget.
on PRs, for each change, add a file to .nanpa/.kdl, that looks like this:
It'd be great to have automation for this, otherwise it'd be easy for devs to forget.
i can always add this to the bot later (as a PR comment with a link), without any changes here
this adds support for versioning through nanpa, via the ilo GitHub bot.
usage guide
on PRs, for each change, add a file to
.nanpa/<unique-name>.kdl
, that looks like this:alternatively you may add the file to
./livekit-ffi/.nanpa/
, and then drop thepackage="livekit-ffi"
.type
s follow Keep a Changelog. you may add multiple lines per file.ilo will create an issue when there's changes in the main branch. use the checkboxes to pick which ones you want to bump. additionally, if you want to set a prerelease version on a package:
or to un-prerelease a package:
note that when updating a package and its dependent, you need to either bump them seperately, or manually update the dependency's Cargo.toml, and then edit the dependent's manifest to include the new dep version.
repo settings that need to change
NANPA_WORKFLOW
environmental variable topublish.yml
, for CI (not as a secret!)