Manage Version

The blocklet version command simplifies the process of updating your blocklet's version number, a critical step before packaging and distributing your work. It modifies the version field in your blocklet.yml file according to semantic versioning (semver) rules.

Running this command also updates the specVersion in your blocklet.yml to the latest version supported by your CLI, ensuring compatibility.

Usage#

Arguments#

Argument	Description
[newVersion]	Optional. Specifies the version increment. It can be a specific version string (e.g., 2.0.0) or a semver keyword: patch, minor, major, prepatch, preminor, premajor, prerelease. If omitted, it defaults to patch.

Options#

Option	Description
--git-commit	Automatically adds blocklet.yml to git and creates a commit with a message like "blocklet version x.y.z".
--force	Allows the command to proceed even if it results in downgrading the specVersion. This is generally not recommended unless you are certain about the downgrade.

Examples#

Bumping a Patch Version#

This is the most common use case. If your current version is 1.2.2, this command will update it to 1.2.3.

Console Output:

Bumping a Minor Version#

To release new features in a backward-compatible way, use the minor keyword.

Setting a Specific Version#

You can also set the version to a specific number directly.

Bumping the Version and Committing to Git#

For a streamlined workflow, you can bump the version and commit the change in a single command.

This command will update blocklet.yml and then execute the equivalent of:

After updating your blocklet's version, the next logical step is to package it. Proceed to the Bundle Blocklet guide to learn how to create a deployable asset from your project.