deno_changesets

🦕 Deno native way to manage versioning and changelogs.

deno run --unstable --allow-read --allow-write --allow-run https://deno.land/x/deno_changesets/main.ts --help

Getting started

Currently deno_changesets comes with some opinions and constraints:

• Versioning follows semver
• Changelogs follow keep a changelog
• Versions are stored in git tags
• Enforces minor bumps when pre-1.0
• All modules are versioned together, there is no way currently to version independently

See: Adding a module on Deno’s docs.

Creating a changeset

Creates a new changeset inside the .changeset folder.

➜  deno run --unstable --allow-read --allow-write --allow-run https://deno.land/x/deno_changesets/main.ts create
 ? Select a module (deno_changesets) › deno_changesets
 ? What type of change? › added
 ? Description › Prompts when creating a changeset now come with hints.
 ? Confirm (y/n) › Yes

Options

Releasing

Releasing collects all previously created changsets, translates them to a version bump (patch, minor, major) with the highest taking precedence, updates changelogs, and then pushes to remote.

➜  deno run --unstable --allow-read --allow-write --allow-run https://deno.land/x/deno_changesets/main.ts release
 ? Will publish from 0.1.0 to 0.2.0 (y/n) › Yes

Multiple modules

If your repository has a top level folder called modules then deno_changesets will assume it’s where subdirectory modules are defined. When releasing all references to these modules will be updated to the latest version, including imports and import maps.

See: An example release.

Options