Skip to content

2.0.0

Choose a tag to compare

View all tags
@julien-carsique-sonarsource julien-carsique-sonarsource released this 27 Aug 10:29
Immutable release. Only release title and notes can be modified.
2.0.0
d41706a

Caution

Breaking change. get-build-number, config-maven, config-pip, and config-uv now require:

    permissions:
      contents: write

What's Changed

Bug Fixes

  • (#336, PREQ-7781) Fixed a race condition where concurrent workflow runs (e.g. several GitHub Stacked PRs opened at once) could be assigned the same build number. Claiming now uses atomic Git references (refs/build-number/<N>) instead of a non-atomic repository-property.
    The manual BUILD_NUMBER output/env passthrough between jobs some workflows used as a cross-job reuse workaround is no longer necessary.
    See the Git References section of the README for the full reference table, and Inspecting current refs for how to check the current build number or a workflow run's claimed number directly via git ls-remote.
    See also the xtranet/Platform/BUILD_NUMBER - GitHub page.

Internal & Chores

Migration

Update every caller's permissions: block: contents: read → contents: write. This includes get-build-number, config-maven,
config-pip, and config-uv.

Remove any manual BUILD_NUMBER output/env passthrough between jobs, as the new atomic Git reference mechanism handles this automatically.

Remove any parent workflow's get-build-number step if it was only used to pass a synchronized build number to child workflows.

Full Changelog: 1.8.9...2.0.0

Assets 3
Loading