ci/woodpecker/pr/config Pipeline was successful
ci/woodpecker/pr/hledger Pipeline was successful
ci/woodpecker/pr/jobs Pipeline was successful
ci/woodpecker/pr/snapshots Pipeline was successful
ci/woodpecker/pr/web Pipeline was successful
ci/woodpecker/pr/worker Pipeline was successful
ci/woodpecker/push/config Pipeline was successful
ci/woodpecker/push/hledger Pipeline was successful
ci/woodpecker/push/jobs Pipeline was successful
ci/woodpecker/push/snapshots Pipeline was successful
ci/woodpecker/push/web Pipeline was successful
ci/woodpecker/push/worker Pipeline was successful
13 lines
574 B
Markdown
13 lines
574 B
Markdown
# Changesets
|
|
|
|
Add one short note per coherent change. Describe its effect plainly, not its
|
|
implementation history. Record shared-package changes under the affected app;
|
|
web and worker are versioned together.
|
|
|
|
Use `pnpm changeset` to add a note and `pnpm changeset status` to inspect pending
|
|
releases. Adding a note does not release anything.
|
|
|
|
Releases require explicit approval: run `pnpm version:apps`, review and commit the
|
|
version/changelog changes, then use `pnpm tag:apps` and push the approved app tags.
|
|
Tags publish container images, not npm packages or deployments.
|