Manage releases and versioning
release-managementskillsetup L2★127
eser/stack ↗What it does
Bump synchronized package versions, update changelogs, and publish JSR/npm releases
Best for
Monorepos with 10+ synchronized packages where independent versioning would fracture the release train.
Inputs
- · Deno task command
- · Version bump type (patch|minor|major)
- · CHANGELOG entries
Outputs
- · Updated versions in all 29+ packages
- · New CHANGELOG section
- · JSR/npm publish triggered
Requires
- · deno task
- · JSR
- · npm registry
Preconditions
Clean working tree; all packages share one version; CHANGELOG.md exists
Failure modes
- · Manual version edits on single package → synchronization broken
- · Skip changelog update → no traceability for release
- · Publish without PR merge → release not tagged
Trust signals
- · Version script (deno task cli codebase versions) forces monorepo discipline
- · JSR primary (OIDC auth), npm secondary for backwards compat
- · Tag format vx.y.z auto-triggers release-notes-sync workflow