SForms follows the semantic versioning recommendations for new releases, and a SHA based ID for new pre-releases. The workflow is described below.
New releases are done only on the master branch. The recommended workflow to publish a new release is as follows:
- Format your files with
npm run prettier:format
. - Commit all your files.
- Use the
npm run release:<patch | minor | major>
to publish a new release. The script will automatically bump the version, create a new git tag, publish the library to npm and push your commit. Refer to semantic versioning to determine which script to use.
NOTE: You must be logged on npmjs.com and added to the @kbss-cvut/s-forms organization to be able to publish manually.
Pre-releases are automatically managed and published with Github Actions. Check ./github/npm-publish-*.yml
or the workflow directory for more detail.
Beta releases are automatically published by github workflow when a pull request is merged on the master branch.
Alpha releases are automatically published by github workflow on every push that is not on the master branch.