Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AXON-19] feat: nightly versioning & release scripts #9

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

sdzh-atlassian
Copy link
Member

What is this?

A set of scripts to define the versioning behavior for nightly releases, in line with the vscode docs

In this implementation:

  • Versions with EVEN minor number (e.g. v3.0.14, v3.2.1) - are treated as stable
  • Versions with ODD minor number (e.g. v1.1.1, v3.1.0) - are treated as pre-release (or nightly)
  • Nightly versions increment patch independently - except when there's a next stable release, then the major/minor is bumped accordingly, and the patch is reset to 0
  • Nightly versions are suffixed with -nightly to indicate pre-release as per semver

How was this tested

  • Bunch of runs for the version scripts to simulate the different stable version updates
  • Played around with these build scripts in a separate repo to satisfactory results
  • Ran release pipeline once here - but more testing will follow once the CI code is merged to `main
    image

@sdzh-atlassian
Copy link
Member Author

As an afterthought - added a check to validate the version number and fail early - in case someone tags incorrectly by mistake
image

@sdzh-atlassian sdzh-atlassian force-pushed the AXON-19-nightly-release-scripts branch from ca39211 to 6c0e081 Compare December 4, 2024 18:40
@sdzh-atlassian sdzh-atlassian merged commit c43983b into main Dec 4, 2024
6 checks passed
@sdzh-atlassian sdzh-atlassian deleted the AXON-19-nightly-release-scripts branch December 4, 2024 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants