Versions

A published version must not change: data that names its @context relies on it. check compares the files with the published ones and fails when a published file would change.

Changing a model later

Before you change anything, start the next version with bump. It keeps the published version online (its @context, vocabulary and schemas go into models/road/releases/), then raises the subject's version in subject.yaml and the version in its schema URLs. It refuses when the files differ from the published ones. Commit the result.

npx github:geolonia/datamodels-toolkit#v0.3.3 bump road minor

Then make the change. The site has both versions; see URLs and versions for which level (patch, minor, major) fits a change.

Only keeping a version

The first thing bump does, keeping the version, is also a command of its own: release. It saves the current version into models/road/releases/ and does not raise the version. Run it once a version is published, before you change its sources, and commit the result. check notes a published version that is not saved yet.

npx github:geolonia/datamodels-toolkit#v0.3.3 release road

Moving to a newer toolkit

To move the node to a newer toolkit, run upgrade and commit: it changes the version in the workflow and the README to the latest release (or the one given with --to). Dependabot also proposes new releases.

npx github:geolonia/datamodels-toolkit#v0.3.3 upgrade