-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Improve, document and group versioning code in Build.scala
#21837
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
Improve, document and group versioning code in Build.scala
#21837
Conversation
Side note: with change to Edit: |
…orkaround wix limitations
…s triggered by tag
d6367fd
to
af7ff5b
Compare
# NECESSARY FLAG TO CORRECTLY CONFIGURE THE VERSION FOR SCALA | ||
RELEASEBUILD: yes | ||
# Release only happends when triggering CI by pushing tag | ||
RELEASEBUILD: ${{ startsWith(github.event.ref, 'refs/tags/') && 'yes' || 'no' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be fine since the payload in the reusable workflow is inherited from the caller (See https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_call)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested it in a custom repo, it worked as expected
…21837) * Introduce `developedVersion` describing the target for the current release cycle * Adapt `baseVersion` to the effectively revert #21011 changes * Adapt .msi packager to use `developedVersion` as a workaround to MSI ProductInfo limitations (version without RC suffix required) * Group and document versioning related code [Cherry-picked 11c957c][modified]
…21837) * Introduce `developedVersion` describing the target for the current release cycle * Adapt `baseVersion` to the effectively revert #21011 changes * Adapt .msi packager to use `developedVersion` as a workaround to MSI ProductInfo limitations (version without RC suffix required) * Group and document versioning related code [Cherry-picked 11c957c][modified]
…21837) * Introduce `developedVersion` describing the target for the current release cycle * Adapt `baseVersion` to the effectively revert #21011 changes * Adapt .msi packager to use `developedVersion` as a workaround to MSI ProductInfo limitations (version without RC suffix required) * Group and document versioning related code [Cherry-picked 11c957c][modified]
…21837) * Introduce `developedVersion` describing the target for the current release cycle * Adapt `baseVersion` to the effectively revert #21011 changes * Adapt .msi packager to use `developedVersion` as a workaround to MSI ProductInfo limitations (version without RC suffix required) * Group and document versioning related code [Cherry-picked 11c957c][modified]
…cala#21837) * Introduce `developedVersion` describing the target for the current release cycle * Adapt `baseVersion` to the effectively revert scala#21011 changes * Adapt .msi packager to use `developedVersion` as a workaround to MSI ProductInfo limitations (version without RC suffix required) * Group and document versioning related code
…cala#21837) * Introduce `developedVersion` describing the target for the current release cycle * Adapt `baseVersion` to the effectively revert scala#21011 changes * Adapt .msi packager to use `developedVersion` as a workaround to MSI ProductInfo limitations (version without RC suffix required) * Group and document versioning related code
@WojciechMazur Do we need to backport this one to LTS? |
It might be useful to have these to align the release procedures between two lines, so we can try to backport this. Some of this changes can already be present in the LTS branch. There's no .msi in the LTS so changes to related CI job and |
…cala#21837) * Introduce `developedVersion` describing the target for the current release cycle * Adapt `baseVersion` to the effectively revert scala#21011 changes * Adapt .msi packager to use `developedVersion` as a workaround to MSI ProductInfo limitations (version without RC suffix required) * Group and document versioning related code
* [build] Improve, document and group versioning code in `Build.scala` (scala#21837) * Introduce `developedVersion` describing the target for the current release cycle * Adapt `baseVersion` to the effectively revert scala#21011 changes * Adapt .msi packager to use `developedVersion` as a workaround to MSI ProductInfo limitations (version without RC suffix required) * Group and document versioning related code * Improve mima test for previous version - test against first version in the series * Document referenceVersion * Update reference, MiMa previous version and sync TASTy version (scala#22187) * We now document better how and when tasty version should be set * Add additional runtime test to ensure we don't emit invalid TASTy version during Release / NIGHTLY releases and the expected version set in build matches version defined in TastyFormat * Adapt `checkReleasedTastyVersion` to LTS series - nightlies of LTS are released using stable TASTy version * Adjust expected tasty version comments to LTS versioning * Adjust MiMaFilter for backported dotty.tools.tasty.TastyVersion class
developedVersion
describing the target for the current release cyclebaseVersion
to the effectively revert Set baseVersion to 3.6.0 instead of 3.6.0-RC1 #21011 changesdevelopedVersion
as a workaround to MSI ProductInfo limitations (version without RC suffix required)Fixes #21821
Resolves #21812
[test_msi]