Skip to content

Bump GitVersion.MsBuild from 6.4.0 to 6.7.0#621

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/nuget/src/GitVersion.MsBuild-6.7.0
Open

Bump GitVersion.MsBuild from 6.4.0 to 6.7.0#621
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/nuget/src/GitVersion.MsBuild-6.7.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jun 1, 2026

Updated GitVersion.MsBuild from 6.4.0 to 6.7.0.

Release notes

Sourced from GitVersion.MsBuild's releases.

6.7.0

As part of this release we had 46 commits which resulted in 3 issues being closed.

Features

Improvements

Contributors

2 contributors made this release possible.

arturcic copilot-swe-agent

SHA256 Hashes of the release artifacts

  • 180fd7cf40fdfacf2c251176a4b613a444db2b40af477fd07a7c6d4d6b355dc6 - gitversion-linux-arm64-6.7.0.tar.gz
  • 254d1de40ac82af4c17771f996cb6656e6f3ba0f9cd2f6e94e07d983ac79595a - gitversion-linux-musl-arm64-6.7.0.tar.gz
  • d59557ebd5fcd036387cf1c7e6fb82df7fe71b5409ec1a69fd4a0ba614ccbcb7 - gitversion-linux-musl-x64-6.7.0.tar.gz
  • e2012abfb3392a6f0ccf5f82738173c291b15bfdb2d5e9197777ec3f41b88f76 - gitversion-linux-x64-6.7.0.tar.gz
  • 429108e0d51f98815b6fbf4ebba84cf53812a4c71eee67180456e8771e9f4320 - gitversion-osx-arm64-6.7.0.tar.gz
  • 02f6b9ac0d70a18d8bc2c0e3eaf183377a2417ecadd5df452ab3150b4404182c - gitversion-osx-x64-6.7.0.tar.gz
  • 873cdc294068cbbda43717e6384b849599d2d0db0db6f7c2592074c8f9386116 - gitversion-win-arm64-6.7.0.zip
  • 55b43a1c1e1d174675ca1500410e64a0ad9904425f2329fe6b35b5368a31f629 - gitversion-win-x64-6.7.0.zip

6.6.2

As part of this release we had 30 commits which resulted in 2 issues being closed.

Improvements

Contributors

2 contributors made this release possible.

denisbredikhin arturcic

SHA256 Hashes of the release artifacts

  • 4d0637a80cdf5b615b0b5426f4c8a670db3f44d696bb68c2935b3ab801698090 - gitversion-linux-arm64-6.6.2.tar.gz
  • 11e0bd3daa1b40f63dc5f61192a41a9d59f76a2513ddefa28ec47ac65c34ee00 - gitversion-linux-musl-arm64-6.6.2.tar.gz
  • fa526a55aa10a80e53ab6e85896144e23350c7366d6307b0f353d9d2d8353e73 - gitversion-linux-musl-x64-6.6.2.tar.gz
  • 1c436efca8063f936ef9144b71350e813ae1a0d6dcd8256ef85c5254ce00714c - gitversion-linux-x64-6.6.2.tar.gz
  • 3c7c331999ff6a69ca4942f4dbc84a87998b5f278df509551be0160415f9e67e - gitversion-osx-arm64-6.6.2.tar.gz
  • fb4d8c16e64360e9fb7df1c507d30c5a959fc0c41e0db2bc2dbcc55808b6d24b - gitversion-osx-x64-6.6.2.tar.gz
  • d0dfba1cdec96efcf5742173aa249fcd8cd866bd0cc519539976c0eaf49556f6 - gitversion-win-arm64-6.6.2.zip
  • 8013cc3422d26ef014c903554be8be6a1b835514e8064f0ec6a63ca52c7f3729 - gitversion-win-x64-6.6.2.zip

6.6.1

As part of this release we had 67 commits which resulted in 2 issues being closed.

Improvements

Contributors

1 contributors made this release possible.

arturcic

SHA256 Hashes of the release artifacts

  • abd80a77ebb3f4750255378f222076bef6884be46b07ee5bb35d84a5c2d5b6fb - gitversion-linux-arm64-6.6.1.tar.gz
  • 37cf7184e9f94de20d1dfd80f5d94a20c74327cab241ba90116531559630a9df - gitversion-linux-musl-arm64-6.6.1.tar.gz
  • bdd393d9ab7a37811bc04a9b92687e99de6b5c0162be416aa6db0dbb9dae51ec - gitversion-linux-musl-x64-6.6.1.tar.gz
  • 613b1247794aaf541b3060d5d5d6ef53e6b7a5779b0bf446f7549ebf935a1d38 - gitversion-linux-x64-6.6.1.tar.gz
  • 2c19105a672c0da445c6998429cd6034b864b707bcd830bb5d4e9862572cc3e2 - gitversion-osx-arm64-6.6.1.tar.gz
  • ee07876b25cd5c53a4500ac94373dd07e207db64fca67201daaa4a78397aba20 - gitversion-osx-x64-6.6.1.tar.gz
  • d333202ff9c95131644a1d093c8e75fd4e29277168d3bdd72342d95c11b9ef08 - gitversion-win-arm64-6.6.1.zip
  • 9a4deffb3c8ad25276577d3a6b8a69d80c3b6a0cb8f0b9c3a933fac7a2c46bbc - gitversion-win-x64-6.6.1.zip

6.6.0

Documentation

Features

Improvements

  • #​4418 [ISSUE]: GitVersion sometimes takes several hours, seemingly hanging for several minutes between steps by ChristoWolf resolved in !4809 by sanelson
  • !4789 Support integer formatting with specifiers D and B by BCSharp raised in #​4788 by BCSharp
  • !4812 refactor(serializer): utilize source-generated JSON context for seria… by arturcic
  • !4817 refactor(gitversion-variables): Standardize output variable order by arturcic

As part of this release we had 131 commits which resulted in 37 issues being closed.

Bugs

Dependencies

6.5.1

As part of this release we had 64 commits which resulted in 6 issues being closed.

Bugs

Features

  • !4750 Bring back support for msbuild and Visual Studio by arturcic

Improvements

  • !4748 Refactor RegexPatterns to use properties instead of methods for Regex by arturcic

Contributors

3 contributors made this release possible.

peschmae davidjenni arturcic

SHA256 Hashes of the release artifacts

  • 00db6e97688e0f9edec5015b10914580405759e4198aabbc7261ccd75161e080 - gitversion-linux-arm64-6.5.1.tar.gz
  • 8d435c06d105350b3368651c467144db462bd73fd23962c5e7ae512638665333 - gitversion-linux-musl-arm64-6.5.1.tar.gz
  • ee0efdbeba8f7f2c4a4d7c78d3cf45429433e3c3219464db4ad7e0c424f735ed - gitversion-linux-musl-x64-6.5.1.tar.gz
  • 2c3f19d9186499efc1e97dbedd250f26ab87ba8c0a58e2c20dc29e9db4aa37cc - gitversion-linux-x64-6.5.1.tar.gz
  • 463c08c23cbdbfe218e132691b0b8a5794cb2696c8dca52ba89f527e73be46f8 - gitversion-osx-arm64-6.5.1.tar.gz
  • 566c3df4abde70bf594059c39803b3650e02251cf8f4d3ce476549ad3cfb9a56 - gitversion-osx-x64-6.5.1.tar.gz
  • beea0ca8e69a5de35f7a1901228368e11f2b4f32ddb7fb32aa27467289bd6f23 - gitversion-win-arm64-6.5.1.zip
  • 5c8f1f8e5ea6512deffe36d00bd7b57c0b64cba547779f78a892c0e73bc48b67 - gitversion-win-x64-6.5.1.zip

6.5.0

As part of this release we had 113 commits which resulted in 10 issues being closed.

Features

Improvements

Contributors

6 contributors made this release possible.

aidanblacklumeris Copilot simonachmueller pvanbuijtene arturcic copilot-swe-agent

SHA256 Hashes of the release artifacts

  • 05994d42146f5dc01348576240fdff0dea75f3cdf13ebd5d3f6764fc1d7e6140 - gitversion-linux-arm64-6.5.0.tar.gz
  • 63fd7d6832c6311fdf3017fc7dc277170ee9dae2790d825d8d7673d6fc1db265 - gitversion-linux-musl-arm64-6.5.0.tar.gz
  • 121c8a1de4133a0c628b3cfc2100b46813fa951ce477be3378247642a06169dd - gitversion-linux-musl-x64-6.5.0.tar.gz
  • 3399cc297ec83ef433763d0bae91b2f998117837397f5a63adca992b00dde2b6 - gitversion-linux-x64-6.5.0.tar.gz
  • 9be6d6f617eeba12ad7786f7187d1ffb21fb14d3db082e645fda5122b2573bc7 - gitversion-osx-arm64-6.5.0.tar.gz
  • e4f83a4a0162dbbf13997fdc6c43fbb155562cb14978a695c1d1218b8f8368c1 - gitversion-osx-x64-6.5.0.tar.gz
  • 86c467cfe9af5cf5e0bef85bd867469aa0c4948a088b6e0e35f930acc650fdeb - gitversion-win-arm64-6.5.0.zip
  • c423d828455777c065e413c585232dbdb6e44e9ec0eae530a55d32d075762e37 - gitversion-win-x64-6.5.0.zip

Commits viewable in compare view.

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
Bump GitVersion.MsBuild from 6.4.0 to 6.7.0
0ec8279 
---
updated-dependencies:
- dependency-name: GitVersion.MsBuild
  dependency-version: 6.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Jun 1, 2026
@clawsweeper
Copy link
Copy Markdown

clawsweeper Bot commented Jun 1, 2026 •
edited
Loading

Codex review: needs changes before merge. Reviewed June 1, 2026, 4:41 PM ET / 20:41 UTC.

Summary
The PR changes src/Directory.Build.props to bump GitVersion.MsBuild from 6.4.0 to 6.7.0.

Reproducibility: yes. Source inspection shows the PR updates only src/Directory.Build.props while .github/workflows/ci.yml and .config/dotnet-tools.json remain pinned to GitVersion 6.4.

Review metrics: 1 noteworthy metric.

  • GitVersion pins: 1 updated, 2 related pins unchanged. MSBuild, CI, and the local version helper all participate in release version calculation.

Merge readiness
Overall: 🦪 silver shellfish
Proof: 🌊 off-meta tidepool
Patch quality: 🦪 silver shellfish
Result: blocked by patch quality or review findings.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

  • Align the CI GitVersion action and .config/dotnet-tools.json pins with the MSBuild package version.
  • [P2] Run ./build.ps1 and both required dotnet test commands after the coordinated bump.

Risk before merge

  • [P1] Merging as-is leaves three GitVersion entry points on different minor versions: MSBuild on 6.7.0, CI action setup on 6.4.x, and the local dotnet tool on 6.4.0. A release could compute artifact/workflow outputs with one GitVersion engine while assemblies are stamped by another.

Maintainer options:

  1. Align all GitVersion pins (recommended)
    Update the MSBuild package, local dotnet tool manifest, and CI GitVersion setup to the same 6.7 line before merge.
  2. Hold the bump
    Close or pause this dependency update until the GitVersion tool, action, and MSBuild package can move together.
Copy recommended automerge instruction 
@clawsweeper automerge

Special instructions:
Update the PR so GitVersion.MsBuild, GitVersion.Tool in .config/dotnet-tools.json, and the CI gittools setup versionSpec all target the same 6.7 line; do not edit CHANGELOG.md; run the repository-required build and tests.

Next step before merge

  • [P2] Queue a narrow repair: the PR can be fixed mechanically by aligning the GitVersion tool and CI action pins with the MSBuild package bump.

Security
Cleared: No concrete security or supply-chain regression was found beyond the normal review needed for a build-time NuGet dependency update.

Review findings

  • [P2] Keep GitVersion tooling pins in sync — src/Directory.Build.props:16
Review details

Best possible solution:

Update GitVersion.MsBuild, GitVersion.Tool, and the CI GitVersion action versionSpec together to the same GitVersion line, then run the repository-required build and test validation.

Do we have a high-confidence way to reproduce the issue?

Yes. Source inspection shows the PR updates only src/Directory.Build.props while .github/workflows/ci.yml and .config/dotnet-tools.json remain pinned to GitVersion 6.4.

Is this the best way to solve the issue?

No. The maintainable fix is to align every GitVersion entry point in the same dependency update, or keep all pins at 6.4 until they can move together.

Full review comments:

  • [P2] Keep GitVersion tooling pins in sync — src/Directory.Build.props:16
    This bumps only GitVersion.MsBuild, but the release workflow still installs GitVersion 6.4.x and the local tool manifest still pins GitVersion.Tool to 6.4.0. The versioning docs make these surfaces part of the same release-version contract, so merging this can make CI/artifact outputs and assembly metadata come from different GitVersion engines. Please bump the workflow/tool pins with this package, or leave the MSBuild package on 6.4.
    Confidence: 0.9

Overall correctness: patch is incorrect
Overall confidence: 0.9

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 1d58d59673c9.

Label changes

Label changes:

  • add P2: This is a normal dependency maintenance PR with limited blast radius, but it touches release versioning rather than isolated application code.
  • add merge-risk: 🚨 automation: The diff changes one GitVersion engine while CI and local versioning remain pinned to 6.4, which can make release automation compute inconsistent versions.
  • add rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🌊 off-meta tidepool and patch quality is 🦪 silver shellfish.
  • add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This is a Dependabot dependency PR, so contributor real-behavior proof is not required; build and test validation should gate the repaired update.

Label justifications:

  • P2: This is a normal dependency maintenance PR with limited blast radius, but it touches release versioning rather than isolated application code.
  • merge-risk: 🚨 automation: The diff changes one GitVersion engine while CI and local versioning remain pinned to 6.4, which can make release automation compute inconsistent versions.
  • rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🌊 off-meta tidepool and patch quality is 🦪 silver shellfish.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This is a Dependabot dependency PR, so contributor real-behavior proof is not required; build and test validation should gate the repaired update.
Evidence reviewed

Acceptance criteria:

  • [P1] ./build.ps1.
  • [P1] dotnet test ./tests/OpenClaw.Shared.Tests/OpenClaw.Shared.Tests.csproj --no-restore.
  • [P1] dotnet test ./tests/OpenClaw.Tray.Tests/OpenClaw.Tray.Tests.csproj --no-restore.

What I checked:

  • PR diff updates only the MSBuild package: The proposed commit changes only src/Directory.Build.props, replacing GitVersion.MsBuild 6.4.0 with 6.7.0 and leaving the local tool manifest and workflow pins untouched. (src/Directory.Build.props:16, 0ec82793448a)
  • Current main has a multi-surface GitVersion contract: Versioning docs say CI computes GitVersion outputs while product builds use GitVersion-backed MSBuild metadata, and the local script uses GitVersion.Tool for the same versioning flow. (docs/VERSIONING.md:41, 1d58d59673c9)
  • CI still pins GitVersion 6.4.x: The workflow installs GitVersion with versionSpec 6.4.x before computing semVer and majorMinorPatch outputs for release/test jobs. (.github/workflows/ci.yml:100, 1d58d59673c9)
  • Local GitVersion.Tool remains 6.4.0: The repository-local dotnet tool manifest still pins GitVersion.Tool to 6.4.0, so local release helpers would use a different engine than MSBuild after this PR. (.config/dotnet-tools.json:6, 1d58d59673c9)
  • History points to the versioning owner path: git blame ties the GitVersion.MsBuild line to the commit that introduced GitVersion-backed app version metadata and closed the versioning work. (src/Directory.Build.props:16, f8e6ac4d0995)

Likely related people:

  • Scott Hanselman: Introduced the GitVersion.MsBuild reference and GitVersion-backed app version metadata, then followed up on the GitVersion branch/tag contract. (role: feature owner; confidence: high; commits: f8e6ac4d0995, 32e6025d00c6; files: src/Directory.Build.props, GitVersion.yml, docs/VERSIONING.md)
  • Vincent Koc: Most recently touched src/Directory.Build.props for build/release dependency packaging, adjacent to the changed package reference. (role: recent adjacent contributor; confidence: medium; commits: 7485ce2af9da; files: src/Directory.Build.props)
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@clawsweeper clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants