Updating a Plugin

For information on semantic versioning, see the Semantic Versioning documentation.

After updating a plugin, bumping the package version is important for ensuring the new changes can be pushed to npm downstream for all consumers of installable packages. For external packages, it helps track changes and maintain compatibility.

Bumping Versions and Publishing External Plugins

For external plugins, manually updating the version number in the package.json field should suffice. Follow the semantic versioning scheme as linked above to ensure clarity in the change.

Code is automatically published to the GitHub Pages instance present here

Bumping Versions and Publishing Installable Plugins

If you've made a change in the repository that requires a new version to be published, you can run the following command to create a new changeset:

yarn changeset

It will prompt you to select the type of change (patch, minor, major) and the packages that are affected by the change. After you've made your selections, it will create a new changeset file.

After you've merged your changes to the main branch, a PR will be automatically created to publish the new version to npm.