Versioning
Codeblox uses semantic versioning.
You can publish as many versions of your block as you'd like, but there are some rules that are enforced on the server-side.
Semantic versioning looks like 1.5.0 where 1 is the major version, 5 is the minor version and 0 is the patch version. Semver convention is to increment the major version whenever a backwards-incompatible change is made. On codeblox, this means one of two things:
- The input or output type is changed
- For example, changing input type from text to number
- Options are modified or removed
These are both considered breaking changes because they could break any sequences or presets associated with your current block version. Because of that, you will need to increment the major version if you do either of these. For example if your current version is 1.5.0 and you change the input type, you'll need to change the version to 2.0.0.
Sequence Block Version
When you create a sequence, codeblox will use the highest major version of each block in the sequence at creation time. Coupled with the above version validation, this ensures that your sequences won't break when a new version of a block is published, but can still receive minor and patch updates.