Skip to content

Build versioning

Choose a tag to compare

@webbertakken webbertakken released this 01 May 16:11

Functional changes:

  • #80 Adds versioning strategies that make versioning work out of the box (does not apply for custom build scripts).
  • #80 Add strategy None to give the option to opt out. (version will be unchanged)
  • #80 Add strategy Semantic which will be based on tags and the number of commits on top. (0.1.2)
  • #80 Add strategy Tag which will only be based on the tag (tag must start with v#, where # is a digit for this to work)
  • #80 Add strategy Custom to simply pass in a specific version of your own choosing.
  • #80 Add documentation for all strategies in the readme of this repository.
  • #81 Cover versioning logic with 100% coverage
  • #83 Fix versioning for push event

Security updates:

  • #76 Bump acorn from 6.4.0 to 6.4.1
  • #84 Security updates

Other:

  • #84 Updated prettier and unicorn linters to the latest version and refactored code to match latest code styles.
  • #84 Set code coverage for patches to no longer block PRs, unless they affect the project too much.

More about versioning:

The custom option would be useful for pipelines that already generate their versions based on a different script. The implementation for that would look like this (supplying version in addition to versioning:

  versioning: Custom
  version: "0.4.12"

The default strategy will be set to Semantic, because it allows for easy out of the box versioning, which helps the newer developers under us (but also pro's) succeed faster. 🎉

To enable automatic versioning, all you need to do is update to the latest version of builder. This means that versioning is effectively an opt-out feature, rather than opt-in. 😉

To opt-out, simply set versioning strategy to none, like so;

  versioning: None

Cheers!