nyron bump

Bump a configured project version.

Usage

npx @nyron/cli bump --type <type> [--project <project>]

Required Options

-t, --type <type>

Required. The type of version bump to perform.

Values:

• major - For breaking changes (e.g., 1.0.0 → 2.0.0)
• minor - For new features (e.g., 1.0.0 → 1.1.0)
• patch - For bug fixes (e.g., 1.0.0 → 1.0.1)

npx @nyron/cli bump --type minor

-p, --project <project>

Optional project id/key from your nyron.config.ts.

If your config contains exactly one project, you can omit this flag:

npx @nyron/cli bump --type minor

For multi-project repositories:

npx @nyron/cli bump --type patch --project api

What It Does

When you run nyron bump, it performs the following steps:

1. Chooses the target project from nyron.config.ts
2. Increments the version in .nyron/meta.json for the selected project
3. Records the version transition in .nyron/versions.json
4. Updates package.json in the project directory to match the new version

Nyron uses the project key from nyron.config.ts, not the tag prefix, when selecting which project to bump.

Examples

Bump the only configured project

npx @nyron/cli bump --type minor

Bump a specific project in a monorepo

npx @nyron/cli bump --type patch --project api

Bump a major version

npx @nyron/cli bump --type major --project cli

After Bumping

After running bump, you should usually:

1. Review the version change
2. Commit the updated package.json and .nyron/ files:

   git add .
   git commit -m "chore: bump version to x.y.z"

3. Mark a release boundary with nyron push-tag
4. Preview or publish release notes with nyron release

See the full workflow guide for details.