chore: bump gittools/actions from 0.9.13 to 4.7.0 - #223
Conversation
dependabot
Bot
added
dependencies
Bumps [gittools/actions](https://github.com/gittools/actions) from 0.9.13 to 4.7.0. - [Release notes](https://github.com/gittools/actions/releases) - [Commits](GitTools/actions@v0.9.13...v4.7.0) --- updated-dependencies: - dependency-name: gittools/actions dependency-version: 4.7.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
gittools/actions 4.7.x requires GitVersion >=6.2.0 <7.0.0, so the bump alone fails
`Build and Package` at the setup step: `Version spec '5.x' resolved as '5.12.0' does
not satisfy the range`. Two more things move with the major, neither of which fails
loudly:
**The exported variable names changed.** v0.9.13 exported `GITVERSION_<PROPERTY>`
(`core.exportVariable('GITVERSION_' + name.toUpperCase(), ...)`); v4.7.0 exports
`<property>` and `GitVersion_<Property>`. `${GITVERSION_FULLSEMVER}` in a bash step is
just empty under the new action, so the build would have run `-Pversion=` and published
a package with no version rather than failing. The step now reads the new names and
exits non-zero if the version comes out empty, so a future rename is a red build.
**GitVersion 6 renamed the mode values**, and 5.x `ContinuousDeployment` is 6.x
`ContinuousDelivery` (6.x `ContinuousDeployment` is a new trunk-based mode). Measured on
this repo, one commit past v6.7.1 on main:
| config | 5.12.0 | 6.4.0 |
|---|---|---|
| `mode: ContinuousDeployment` | `6.7.2-ci.1` | `6.7.2` |
| `mode: ContinuousDelivery` | - | `6.7.2-1` |
Leaving the old value would have dropped the pre-release tag and produced a plain
`6.7.2` that collides with the eventual release, so the value is ported rather than kept.
Verified with the 5.12.0 and 6.4.0 tools against this repo:
| scenario | 5.12.0 FullSemVer | 6.4.0 FullSemVer |
|---|---|---|
| PR ref `refs/pull/234/merge` | `6.7.2-PullRequest0234.1` | `6.7.2-PullRequest234.1` |
| release tag `v6.7.1` | `6.7.1` | `6.7.1` |
PR builds lose the zero-padding on the PR number, which is the only user-visible change;
they stay unique per commit (`PullRequest234.3`, `.4` over successive commits). FullSemVer
is kept over SemVer for that reason - on a plain branch SemVer repeats across commits
while FullSemVer carries the count. README's worked example is updated to match, and
`./gradlew packageName -Pversion=6.7.2-PullRequest234.4` names the zip as expected.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
fadb345 to
c654e42
Compare
|
Rebased onto
The exported variable names changed, silently. v0.9.13 exported core.exportVariable(`GITVERSION_${name.toUpperCase()}`, value)v4.7.0 exports
Keeping the old value would have dropped the pre-release tag and produced a plain What changes for us
The zero-padding on the PR number is the only user-visible difference; README's worked example is updated. PR versions stay unique per commit ( Checked locally with both tools against this repo, and Note this branch now has a non-dependabot commit on it, so dependabot will leave it alone rather than rebasing it. |
The first CI run of this branch built `Octopus.TeamCity.6.8.0-PullRequest223.3` where 5.x would have built `6.7.2-PullRequest0223.3` - the minor moved, not just the padding. `pull-request` carries `increment: Inherit` in both versions, so the increment comes from the source branch. GitVersion 6 resolves that through `develop`, whose default increment is Minor; 5.12.0 resolved it through `main` (Patch). `develop` here is a branch last touched at "Update Octo.exe to 3.4.0-beta0002" and long superseded by release-please on `main`, so the version was being decided by a dead ref. Reproduced against the real `refs/pull/223/merge`, and deleting the `origin/develop` ref alone takes 6.4.0 back to `6.7.2-PullRequest223.3`. Pinning the increment fixes it at the config rather than depending on which stale branches the remote happens to carry: | GitVersion.yml | 5.12.0 | 6.4.0 | |---|---|---| | as pushed | `6.7.2-PullRequest0223.3` | `6.8.0-PullRequest223.3` | | `pull-request: increment: Patch` | `6.7.2-PullRequest0223.3` | `6.7.2-PullRequest223.3` | 5.12.0 reads the same file unchanged, and `main` and the `v6.7.1` tag stay at `6.7.1` under both tools, so the nightly and release paths are untouched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The first run here built
Reproduced against the real Pinned at the config rather than depending on the remote's branch hygiene:
5.12.0 reads the same file unchanged, so the config isn't tied to the bump landing, and Worth noting separately: |
1 participant
Bumps gittools/actions from 0.9.13 to 4.7.0.
Release notes
Sourced from gittools/actions's releases.
... (truncated)
Commits
7417b10build: update GitVersion version specification to 6.8.xf6091cfMerge pull request #2086 from MarcelGosselin/fix/issue-18247c22071fix: update minimum GitVersion.Tool to 6.2.0 so output is compatibleb6fc43bMerge pull request #2135 from GitTools/dependabot/npm_and_yarn/vite-78f5677d332e13db5(npm): bump vite from 8.1.2 to 8.1.3 in the vite groupf0638b1docs(release-skill): harden GRM preconditions, settle check, and recovery steps13f62f7build(grm): include contributors in release notes214fddaupdate examples version to 4.6.003e8e09build(dependabot): assign PRs to the umbrella milestone (32)4eb45bbMerge pull request #2131 from GitTools/fix/deterministic-process-importDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)