new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Deno · Reference · all subjects

cli commands/bump-version

20 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

bump-version example: dry-run check

deno bump-version --base=main --dry-run

bump-version experimental status

deno bump-version is experimental and subject to change.

deno bump-version command syntax

The deno bump-version command updates the version field in the project's configuration file, reading and writing the version field in deno.json(c) if present, otherwise falling back to package.json. The command syntax is: deno bump-version [increment]

bump-version increment types and examples

The increment argument selects how the version is bumped with the following options: patch (1.4.6 → 1.4.7), minor (1.4.6 → 1.5.0), major (1.4.6 → 2.0.0), prepatch (1.4.6 → 1.4.7-0), preminor (1.4.6 → 1.5.0-0), premajor (1.4.6 → 2.0.0-0), prerelease (1.4.7-0 → 1.4.7-1).

bump-version default behavior when increment omitted

If increment is omitted, the current version is printed and the configuration file is left unchanged.

bump-version default version when no version field exists

If the configuration file has no version field and an increment is given, the version defaults to 0.1.0.

bump-version error when config file missing

The command exits with an error if neither deno.json nor package.json is found in the current directory.

bump-version workspace mode behavior

When run at the root of a workspace, deno bump-version operates on every member package in a single pass. The same increment is applied to each member's version field. jsr: version constraints in the workspace root config and in any import map are rewritten in place so cross-package references keep matching the bumped versions. Members without a version field are left alone.

bump-version Conventional Commits mode

Inside a workspace, running deno bump-version with no increment argument switches to deriving per-package bumps from Conventional Commits between a base ref and the current branch. Each member's bump is computed independently from the commits that touched files inside it, honoring scoped commits and wildcard * scopes, and the bumped versions are written back to the member configs and any import-map constraints.

bump-version Conventional Commits derivation rules

Conventional Commits derivation rules: fix: and other patch-level types yield patch bump; feat: yields minor bump; a commit marked BREAKING CHANGE: in the body or with ! after the type (e.g. feat!:) yields major bump; for packages still on 0.x.y, semver rules are applied conservatively (breaking change yields minor bump rather than major, and feat: yields patch); prereleases (-0, -1, …) get prerelease increment; any manual edits to a package's version since the base ref are treated as authoritative and skipped.

bump-version --base flag

The --base flag specifies the ref to compare against when deriving bumps from Conventional Commits. Usually a release branch or tag (e.g., --base=main or --base=v1.4.7). This flag is used with deno bump-version --base=<ref>.

bump-version --start flag

The --start flag specifies the ref where the changeset begins when deriving bumps from Conventional Commits. It defaults to the merge base between --base and HEAD. This flag is used with deno bump-version --start=<ref>.

bump-version --dry-run flag

The --dry-run flag prints the planned changes without writing anything to disk. It shows which packages would bump, the old and new version pairs, and the rewritten jsr: constraints. This flag is useful for CI checks and for previewing a release locally before committing.

bump-version example: patch release

deno bump-version patch

bump-version example: minor release

deno bump-version minor

bump-version example: prerelease iteration

deno bump-version prerelease

bump-version example: print version without modifying

deno bump-version

bump-version example: workspace with Conventional Commits

deno bump-version --base=main

bump-version example: compare two explicit refs

deno bump-version --base=v1.4.7 --start=release/1.5

deno bump-version command

deno bump-version is used to bump the project version in deno.json or package.json.

Give your agent this brain