Skip to content

Releases: RollingVersions/RollingVersions

@rollingversions/server@5.1.1

14 Jan 11:47
c471e70
Compare
Choose a tag to compare

Bug Fixes

  • Loading past releases resulted in a 500 error if any packages had no releases (#195)

rollingversions@3.2.0

22 Dec 15:10
7453019
Compare
Choose a tag to compare

New Features

  • Add support for "Release Descriptions" (#192)

@rollingversions/types@2.1.0

22 Dec 15:10
7453019
Compare
Choose a tag to compare

New Features

  • Add types for new API endpoints (#192)

@rollingversions/server@5.1.0

22 Dec 15:10
7453019
Compare
Choose a tag to compare

You can find a video that covers all the new features in this release on YouTube

New Features

  • Support adding descriptions to releases (#192)

    This lets you provide additional context above the list of structured changes.

  • Show list of pull requests included in the next release on the repository page (#192)

    This makes it easier to see any pull requests that might be missing release notes

  • Link to pull requests on repository page (#192)

    This makes it easier to edit release notes.

  • Show past releases on the repository page (#192)

    We show the most recent release for each package by default. You can then choose a package to filter by and see all releases for that package. Since these are pulled from GitHub, they include releases even before you started using Rolling Versions (provided you created GitHub releases for them)

rollingversions@3.1.0

29 Oct 16:08
b2b3f69
Compare
Choose a tag to compare

New Features

  • Add support for optional sections in custom tag formats (#189)

    You can now mark a section of the custom tag format as optional. It will then only be included if there is a non-zero version in that section. e.g. the following:

    tag_format = "v{{MAJOR}}.{{MINOR}}{{?.{{PATCH}}}}"

    Produces a tag of v1.2.3 for version 1.2.3, but produces a simplified tag of v1.2 for 1.2.0.

  • Support custom change types and custom versioning schemas (#189)

    You can see an example using all these features in test-circleci-hotfix-releases

  • Support overriding the versioning mode for different branches separately (#189)

    For example, to have a different versioning mode between hotfix branches and the main branch, you could do:

    [[versioning_mode]]
      branch = "main"
      mode = "ALWAYS_INCREASING"
    
    [[versioning_mode]]
      branch = "hotfix/*"
      mode = "BY_BRANCH"
  • Report validation errors in package manifest config more clearly (#189)

  • Display custom tag formats in preview logs when specified in config (#189)

  • Pass $CURRENT_VERSION, $CURRENT_TAG and $NEW_TAG to custom scripts (#189)

@rollingversions/version-number@3.0.0

29 Oct 16:08
b2b3f69
Compare
Choose a tag to compare

Breaking Changes

  • Update @rollingversions/types to provide more flexible versioning mode config (#189)

@rollingversions/types@2.0.0

29 Oct 16:08
b2b3f69
Compare
Choose a tag to compare

Breaking Changes

  • Allow versoiningMode to be customised per branch (#189)

@rollingversions/tag-format@3.0.0

29 Oct 16:08
b2b3f69
Compare
Choose a tag to compare

Breaking Changes

  • Update @rollingversions/types to provide more flexible versioning mode config (#189)

New Features

  • Support optional sections in custom tag formats (#189)

@rollingversions/sort-by-dependencies@2.0.0

29 Oct 16:08
b2b3f69
Compare
Choose a tag to compare

Breaking Changes

  • Update @rollingversions/types to provide more flexible versioning mode config (#189)

@rollingversions/server@5.0.0

29 Oct 17:49
f5ff7b7
Compare
Choose a tag to compare

Breaking Changes

  • Remove support for tracking cherry picked commits (#191)

    The performance was way too slow on production. We still track the info in our database, so it may be possible to re-add something along these lines in a future release.

    Support for this feature was only added in v4.0.0 (released approximately 2 hours ago) so hopefully nobody is currently relying on this feature.