Skip to content

Bump the major-minor-dependencies group across 3 directories with 2 updates #530

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Apr 8, 2025
Merged

Bump the major-minor-dependencies group across 3 directories with 2 updates #530

merged 1 commit into from
Apr 8, 2025

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 7, 2025

Bumps the major-minor-dependencies group with 2 updates in the /backend/ILSpyX.Backend directory: GitVersion.MsBuild and gitversion.tool.
Bumps the major-minor-dependencies group with 2 updates in the /backend/ILSpyX.Backend.LSP directory: GitVersion.MsBuild and gitversion.tool.
Bumps the major-minor-dependencies group with 2 updates in the /backend/ILSpyX.Backend.Tests directory: GitVersion.MsBuild and gitversion.tool.

Updates GitVersion.MsBuild from 6.1.0 to 6.2.0

Release notes

Sourced from GitVersion.MsBuild's releases.

6.2.0

As part of this release we had 159 commits which resulted in 27 issues being closed.

Breaking change

  • !4383 branch regex is matched against {EscapedBranchName} not {BranchName} by HHobeck

Bugs

Dependencies

Documentation

Features

Improvements

Contributors

... (truncated)

Changelog

Sourced from GitVersion.MsBuild's changelog.

v6.2.0

  • The configuration property label-number-pattern was removed. The functionality can be still used by changing the label and the branch name regular expression for pull-request branches.

v6.0.0

Platforms

  • Drop support for .NET Framework 4.8, .NET Core 3.1 and .NET 5.0. Changed the project targets to .NET 6.0 or later.

Caching

  • Refactor caching system in GitVersion to use json files instead of yaml files. This change is not backwards compatible with the old caching system.

Configuration changes:

  • The configuration properties continuous-delivery-fallback-tag, tag-number-pattern, and tag were renamed to continuous-delivery-fallback-label, label-number-pattern, and label respectively. tag-pre-release-weight and tag-prefix remained as they were as they are referring to a Git tag.

  • When using a commit message that matches both *-version-bump-message and no-bump-message, there is no increment for that commit. In other words, no-bump-message now takes precedence over *-version-bump-message.

  • The fallback version strategy now returns 0.0.0 and is flagged with ShouldIncrement equal to true. This yields the version 0.1.0 on the develop branch (IncrementStrategy.Minor by default) and 0.0.1 on the main branch (IncremetnStrategy.Patch by default).

  • The current branch (child) inherits its configuration from the source (parent) branch if the increment strategy is set to Inherit. This makes branch configuration recursive, simpler, more intuitive, more flexible, and more robust.

  • Instead of having a single effective configuration, we now have one effective configuration per branch where the increment strategy is not set to inherit.

  • The new implementation of the branch configuration inheritance affects per default only the pull-requests, hotfix and feature branches. In this case the next version will be generated like the child branch is not existing and the commits have been made on the source branch.

    • The following example illustrates this behavior. On the feature branch the semantic version 1.1.0-just-a-test.1+2 will now be generated instead of version 1.0.0-just-a-test.1+3 previously:

      * 1f1cfb4 52 minutes ago  (HEAD -> feature/just-a-test)
* 1f9654d 54 minutes ago  (release/1.1.0)
* be72411 56 minutes ago  (develop)
* 14800ff 58 minutes ago  (tag: 1.0.0, main)

  • A new unknown branch magic string has been introduced to give the user the possibility to specify the branch configuration for a branch which is not known. A branch is not known if only the regular expression of the branch configuration with the name unknown is matching. Please notice that this branch configuration behaves like any other branch configurations.

  • Additional fallback branch configuration properties have been introduced at the root to define base properties which will be inherit to the branch configurations. That means if no other branch configuration in the inheritance line defines the given property the fallback property applies. Notice that the inheritance tree can be controlled using the increment strategy property in the branch configuration section.

    • The following example illustrates this behavior. The hotfix branch configuration overrides the main branch configuration and the result overrides the fallback branch configuration.

      * 1f1cfb4 52 minutes ago  (HEAD -> hotfix/just-a-test)
* 14800ff 58 minutes ago  (tag: 1.0.0, main)

  • When overriding the configuration with e.g. GitVersion.yaml the software distinguishes between properties who are not existent and properties who are null. This is especially important if the user wants to define branch related configuration which are marked with increment strategy Inherit.

  • Following root configuration properties have been removed:

    • continuous-delivery-fallback-tag

... (truncated)

Commits
  • c2bc09f update schemas
  • 8ba10bd +semver minor
  • 3b32eec Merge pull request #4476 from GitTools/dependabot/nuget/new-cli/multi-0aa6d1b253
  • a16753f (deps): Bump Microsoft.CSharp and Scriban in /new-cli
  • 336bd63 Refactor semantic version handling with dedicated tuple type
  • 67b3bfe Renamed build agent methods for consistency
  • fe6ef74 Merge pull request #4469 from GitTools/dependabot/nuget/new-cli/microsoft-07c...
  • 70eff5c (deps): Bump System.CommandLine
  • 939e240 Merge pull request #4470 from GitTools/dependabot/nuget/new-cli/serilog-99926...
  • 122bdd1 (deps): Bump the serilog group across 1 directory with 2 updates
  • Additional commits viewable in compare view

Updates gitversion.tool from 6.1.0 to 6.2.0

Release notes

Sourced from gitversion.tool's releases.

6.2.0

As part of this release we had 159 commits which resulted in 27 issues being closed.

Breaking change

  • !4383 branch regex is matched against {EscapedBranchName} not {BranchName} by HHobeck

Bugs

Dependencies

Documentation

Features

Improvements

Contributors

... (truncated)

Changelog

Sourced from gitversion.tool's changelog.

v6.2.0

  • The configuration property label-number-pattern was removed. The functionality can be still used by changing the label and the branch name regular expression for pull-request branches.

v6.0.0

Platforms

  • Drop support for .NET Framework 4.8, .NET Core 3.1 and .NET 5.0. Changed the project targets to .NET 6.0 or later.

Caching

  • Refactor caching system in GitVersion to use json files instead of yaml files. This change is not backwards compatible with the old caching system.

Configuration changes:

  • The configuration properties continuous-delivery-fallback-tag, tag-number-pattern, and tag were renamed to continuous-delivery-fallback-label, label-number-pattern, and label respectively. tag-pre-release-weight and tag-prefix remained as they were as they are referring to a Git tag.

  • When using a commit message that matches both *-version-bump-message and no-bump-message, there is no increment for that commit. In other words, no-bump-message now takes precedence over *-version-bump-message.

  • The fallback version strategy now returns 0.0.0 and is flagged with ShouldIncrement equal to true. This yields the version 0.1.0 on the develop branch (IncrementStrategy.Minor by default) and 0.0.1 on the main branch (IncremetnStrategy.Patch by default).

  • The current branch (child) inherits its configuration from the source (parent) branch if the increment strategy is set to Inherit. This makes branch configuration recursive, simpler, more intuitive, more flexible, and more robust.

  • Instead of having a single effective configuration, we now have one effective configuration per branch where the increment strategy is not set to inherit.

  • The new implementation of the branch configuration inheritance affects per default only the pull-requests, hotfix and feature branches. In this case the next version will be generated like the child branch is not existing and the commits have been made on the source branch.

    • The following example illustrates this behavior. On the feature branch the semantic version 1.1.0-just-a-test.1+2 will now be generated instead of version 1.0.0-just-a-test.1+3 previously:

      * 1f1cfb4 52 minutes ago  (HEAD -> feature/just-a-test)
* 1f9654d 54 minutes ago  (release/1.1.0)
* be72411 56 minutes ago  (develop)
* 14800ff 58 minutes ago  (tag: 1.0.0, main)

  • A new unknown branch magic string has been introduced to give the user the possibility to specify the branch configuration for a branch which is not known. A branch is not known if only the regular expression of the branch configuration with the name unknown is matching. Please notice that this branch configuration behaves like any other branch configurations.

  • Additional fallback branch configuration properties have been introduced at the root to define base properties which will be inherit to the branch configurations. That means if no other branch configuration in the inheritance line defines the given property the fallback property applies. Notice that the inheritance tree can be controlled using the increment strategy property in the branch configuration section.

    • The following example illustrates this behavior. The hotfix branch configuration overrides the main branch configuration and the result overrides the fallback branch configuration.

      * 1f1cfb4 52 minutes ago  (HEAD -> hotfix/just-a-test)
* 14800ff 58 minutes ago  (tag: 1.0.0, main)

  • When overriding the configuration with e.g. GitVersion.yaml the software distinguishes between properties who are not existent and properties who are null. This is especially important if the user wants to define branch related configuration which are marked with increment strategy Inherit.

  • Following root configuration properties have been removed:

    • continuous-delivery-fallback-tag

... (truncated)

Commits
  • c2bc09f update schemas
  • 8ba10bd +semver minor
  • 3b32eec Merge pull request #4476 from GitTools/dependabot/nuget/new-cli/multi-0aa6d1b253
  • a16753f (deps): Bump Microsoft.CSharp and Scriban in /new-cli
  • 336bd63 Refactor semantic version handling with dedicated tuple type
  • 67b3bfe Renamed build agent methods for consistency
  • fe6ef74 Merge pull request #4469 from GitTools/dependabot/nuget/new-cli/microsoft-07c...
  • 70eff5c (deps): Bump System.CommandLine
  • 939e240 Merge pull request #4470 from GitTools/dependabot/nuget/new-cli/serilog-99926...
  • 122bdd1 (deps): Bump the serilog group across 1 directory with 2 updates
  • Additional commits viewable in compare view

Updates GitVersion.MsBuild from 6.1.0 to 6.2.0

Release notes

Sourced from GitVersion.MsBuild's releases.

6.2.0

As part of this release we had 159 commits which resulted in 27 issues being closed.

Breaking change

  • !4383 branch regex is matched against {EscapedBranchName} not {BranchName} by HHobeck

Bugs

Dependencies

Documentation

Features

Improvements

Contributors

... (truncated)

Changelog

Sourced from GitVersion.MsBuild's changelog.

v6.2.0

  • The configuration property label-number-pattern was removed. The functionality can be still used by changing the label and the branch name regular expression for pull-request branches.

v6.0.0

Platforms

  • Drop support for .NET Framework 4.8, .NET Core 3.1 and .NET 5.0. Changed the project targets to .NET 6.0 or later.

Caching

  • Refactor caching system in GitVersion to use json files instead of yaml files. This change is not backwards compatible with the old caching system.

Configuration changes:

  • The configuration properties continuous-delivery-fallback-tag, tag-number-pattern, and tag were renamed to continuous-delivery-fallback-label, label-number-pattern, and label respectively. tag-pre-release-weight and tag-prefix remained as they were as they are referring to a Git tag.

  • When using a commit message that matches both *-version-bump-message and no-bump-message, there is no increment for that commit. In other words, no-bump-message now takes precedence over *-version-bump-message.

  • The fallback version strategy now returns 0.0.0 and is flagged with ShouldIncrement equal to true. This yields the version 0.1.0 on the develop branch (IncrementStrategy.Minor by default) and 0.0.1 on the main branch (IncremetnStrategy.Patch by default).

  • The current branch (child) inherits its configuration from the source (parent) branch if the increment strategy is set to Inherit. This makes branch configuration recursive, simpler, more intuitive, more flexible, and more robust.

  • Instead of having a single effective configuration, we now have one effective configuration per branch where the increment strategy is not set to inherit.

  • The new implementation of the branch configuration inheritance affects per default only the pull-requests, hotfix and feature branches. In this case the next version will be generated like the child branch is not existing and the commits have been made on the source branch.

    • The following example illustrates this behavior. On the feature branch the semantic version 1.1.0-just-a-test.1+2 will now be generated instead of version 1.0.0-just-a-test.1+3 previously:

      * 1f1cfb4 52 minutes ago  (HEAD -> feature/just-a-test)
* 1f9654d 54 minutes ago  (release/1.1.0)
* be72411 56 minutes ago  (develop)
* 14800ff 58 minutes ago  (tag: 1.0.0, main)

  • A new unknown branch magic string has been introduced to give the user the possibility to specify the branch configuration for a branch which is not known. A branch is not known if only the regular expression of the branch configuration with the name unknown is matching. Please notice that this branch configuration behaves like any other branch configurations.

  • Additional fallback branch configuration properties have been introduced at the root to define base properties which will be inherit to the branch configurations. That means if no other branch configuration in the inheritance line defines the given property the fallback property applies. Notice that the inheritance tree can be controlled using the increment strategy property in the branch configuration section.

    • The following example illustrates this behavior. The hotfix branch configuration overrides the main branch configuration and the result overrides the fallback branch configuration.

      * 1f1cfb4 52 minutes ago  (HEAD -> hotfix/just-a-test)
* 14800ff 58 minutes ago  (tag: 1.0.0, main)

  • When overriding the configuration with e.g. GitVersion.yaml the software distinguishes between properties who are not existent and properties who are null. This is especially important if the user wants to define branch related configuration which are marked with increment strategy Inherit.

  • Following root configuration properties have been removed:

    • continuous-delivery-fallback-tag

... (truncated)

Commits
  • c2bc09f update schemas
  • 8ba10bd +semver minor
  • 3b32eec Merge pull request #4476 from GitTools/dependabot/nuget/new-cli/multi-0aa6d1b253
  • a16753f (deps): Bump Microsoft.CSharp and Scriban in /new-cli
  • 336bd63 Refactor semantic version handling with dedicated tuple type
  • 67b3bfe Renamed build agent methods for consistency
  • fe6ef74 Merge pull request #4469 from GitTools/dependabot/nuget/new-cli/microsoft-07c...
  • 70eff5c (deps): Bump System.CommandLine
  • 939e240 Merge pull request #4470 from GitTools/dependabot/nuget/new-cli/serilog-99926...
  • 122bdd1 (deps): Bump the serilog group across 1 directory with 2 updates
  • Additional commits viewable in compare view

Updates gitversion.tool from 6.1.0 to 6.2.0

Release notes

Sourced from gitversion.tool's releases.

6.2.0

As part of this release we had 159 commits which resulted in 27 issues being closed.

Breaking change

  • !4383 branch regex is matched against {EscapedBranchName} not {BranchName} by HHobeck

Bugs

Dependencies

Documentation

Features

Improvements

Contributors

... (truncated)

Changelog

Sourced from gitversion.tool's changelog.

v6.2.0

  • The configuration property label-number-pattern was removed. The functionality can be still used by changing the label and the branch name regular expression for pull-request branches.

v6.0.0

Platforms

  • Drop support for .NET Framework 4.8, .NET Core 3.1 and .NET 5.0. Changed the project targets to .NET 6.0 or later.

Caching

  • Refactor caching system in GitVersion to use json files instead of yaml files. This change is not backwards compatible with the old caching system.

Configuration changes:

  • The configuration properties continuous-delivery-fallback-tag, tag-number-pattern, and tag were renamed to continuous-delivery-fallback-label, label-number-pattern, and label respectively. tag-pre-release-weight and tag-prefix remained as they were as they are referring to a Git tag.

  • When using a commit message that matches both *-version-bump-message and no-bump-message, there is no increment for that commit. In other words, no-bump-message now takes precedence over *-version-bump-message.

  • The fallback version strategy now returns 0.0.0 and is flagged with ShouldIncrement equal to true. This yields the version 0.1.0 on the develop branch (IncrementStrategy.Minor by default) and 0.0.1 on the main branch (IncremetnStrategy.Patch by default).

  • The current branch (child) inherits its configuration from the source (parent) branch if the increment strategy is set to Inherit. This makes branch configuration recursive, simpler, more intuitive, more flexible, and more robust.

  • Instead of having a single effective configuration, we now have one effective configuration per branch where the increment strategy is not set to inherit.

  • The new implementation of the branch configuration inheritance affects per default only the pull-requests, hotfix and feature branches. In this case the next version will be generated like the child branch is not existing and the commits have been made on the source branch.

    • The following example illustrates this behavior. On the feature branch the semantic version 1.1.0-just-a-test.1+2 will now be generated instead of version 1.0.0-just-a-test.1+3 previously:

      * 1f1cfb4 52 minutes ago  (HEAD -> feature/just-a-test)
* 1f9654d 54 minutes ago  (release/1.1.0)
* be72411 56 minutes ago  (develop)
* 14800ff 58 minutes ago  (tag: 1.0.0, main)

  • A new unknown branch magic string has been introduced to give the user the possibility to specify the branch configuration for a branch which is not known. A branch is not known if only the regular expression of the branch configuration with the name unknown is matching. Please notice that this branch configuration behaves like any other branch configurations.

  • Additional fallback branch configuration properties have been introduced at the root to define base properties which will be inherit to the branch configurations. That means if no other branch configuration in the inheritance line defines the given property the fallback property applies. Notice that the inheritance tree can be controlled using the increment strategy property in the branch configuration section.

    • The following example illustrates this behavior. The hotfix branch configuration overrides the main branch configuration and the result overrides the fallback branch configuration.

      * 1f1cfb4 52 minutes ago  (HEAD -> hotfix/just-a-test)
* 14800ff 58 minutes ago  (tag: 1.0.0, main)

  • When overriding the configuration with e.g. GitVersion.yaml the software distinguishes between properties who are not existent and properties who are null. This is especially important if the user wants to define branch related configuration which are marked with increment strategy Inherit.

  • Following root configuration properties have been removed:

    • continuous-delivery-fallback-tag

... (truncated)

Commits
  • c2bc09f update schemas
  • 8ba10bd +semver minor
  • 3b32eec Merge pull request #4476 from GitTools/dependabot/nuget/new-cli/multi-0aa6d1b253
  • a16753f (deps): Bump Microsoft.CSharp and Scriban in /new-cli
  • 336bd63 Refactor semantic version handling with dedicated tuple type
  • 67b3bfe Renamed build agent methods for consistency
  • fe6ef74 Merge pull request #4469 from GitTools/dependabot/nuget/new-cli/microsoft-07c...
  • 70eff5c (deps): Bump System.CommandLine
  • 939e240 Merge pull request #4470 from GitTools/dependabot/nuget/new-cli/serilog-99926...
  • 122bdd1 (deps): Bump the serilog group across 1 directory with 2 updates
  • Additional commits viewable in compare view

Updates GitVersion.MsBuild from 6.1.0 to 6.2.0

Release notes

Sourced from GitVersion.MsBuild's releases.

6.2.0

As part of this release we had 159 commits which resulted in 27 issues being closed.

Breaking change

  • !4383 branch regex is matched against {EscapedBranchName} not {BranchName} by HHobeck

Bugs

Dependencies

@dependabot
Bump the major-minor-dependencies group across 3 directories with 2 u…
59e03b8 
…pdates

Bumps the major-minor-dependencies group with 2 updates in the /backend/ILSpyX.Backend directory: [GitVersion.MsBuild](https://github.com/GitTools/GitVersion) and [gitversion.tool](https://github.com/GitTools/GitVersion).
Bumps the major-minor-dependencies group with 2 updates in the /backend/ILSpyX.Backend.LSP directory: [GitVersion.MsBuild](https://github.com/GitTools/GitVersion) and [gitversion.tool](https://github.com/GitTools/GitVersion).
Bumps the major-minor-dependencies group with 2 updates in the /backend/ILSpyX.Backend.Tests directory: [GitVersion.MsBuild](https://github.com/GitTools/GitVersion) and [gitversion.tool](https://github.com/GitTools/GitVersion).


Updates `GitVersion.MsBuild` from 6.1.0 to 6.2.0
- [Release notes](https://github.com/GitTools/GitVersion/releases)
- [Changelog](https://github.com/GitTools/GitVersion/blob/main/BREAKING_CHANGES.md)
- [Commits](GitTools/GitVersion@6.1.0...6.2.0)

Updates `gitversion.tool` from 6.1.0 to 6.2.0
- [Release notes](https://github.com/GitTools/GitVersion/releases)
- [Changelog](https://github.com/GitTools/GitVersion/blob/main/BREAKING_CHANGES.md)
- [Commits](GitTools/GitVersion@6.1.0...6.2.0)

Updates `GitVersion.MsBuild` from 6.1.0 to 6.2.0
- [Release notes](https://github.com/GitTools/GitVersion/releases)
- [Changelog](https://github.com/GitTools/GitVersion/blob/main/BREAKING_CHANGES.md)
- [Commits](GitTools/GitVersion@6.1.0...6.2.0)

Updates `gitversion.tool` from 6.1.0 to 6.2.0
- [Release notes](https://github.com/GitTools/GitVersion/releases)
- [Changelog](https://github.com/GitTools/GitVersion/blob/main/BREAKING_CHANGES.md)
- [Commits](GitTools/GitVersion@6.1.0...6.2.0)

Updates `GitVersion.MsBuild` from 6.1.0 to 6.2.0
- [Release notes](https://github.com/GitTools/GitVersion/releases)
- [Changelog](https://github.com/GitTools/GitVersion/blob/main/BREAKING_CHANGES.md)
- [Commits](GitTools/GitVersion@6.1.0...6.2.0)

Updates `gitversion.tool` from 6.1.0 to 6.2.0
- [Release notes](https://github.com/GitTools/GitVersion/releases)
- [Changelog](https://github.com/GitTools/GitVersion/blob/main/BREAKING_CHANGES.md)
- [Commits](GitTools/GitVersion@6.1.0...6.2.0)

---
updated-dependencies:
- dependency-name: GitVersion.MsBuild
  dependency-version: 6.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: major-minor-dependencies
- dependency-name: gitversion.tool
  dependency-version: 6.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: major-minor-dependencies
- dependency-name: GitVersion.MsBuild
  dependency-version: 6.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: major-minor-dependencies
- dependency-name: gitversion.tool
  dependency-version: 6.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: major-minor-dependencies
- dependency-name: GitVersion.MsBuild
  dependency-version: 6.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: major-minor-dependencies
- dependency-name: gitversion.tool
  dependency-version: 6.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: major-minor-dependencies
...

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 Apr 7, 2025
@Rpinski Rpinski merged commit a6f6030 into master Apr 8, 2025
1 check passed
@dependabot dependabot bot deleted the dependabot/nuget/backend/ILSpyX.Backend/major-minor-dependencies-a4ea52f1e1 branch April 8, 2025 12:30
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Rpinski