Skip to content

chore(deps): update dependency dotnet-sdk to v10

87e6747
Select commit
Loading
Failed to load commit list.
Closed

chore(deps): update dependency dotnet-sdk to v10 #1371

chore(deps): update dependency dotnet-sdk to v10
87e6747
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 12, 2025 in 1s

2 potential rules

Rule: Automatic merge on approval (merge)

  • #approved-reviews-by>=1
  • #commits-behind = 0 [πŸ›‘ GitHub repository ruleset rule]
  • -closed [πŸ“Œ merge requirement]
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-neutral = Unit tests (macos-latest)
    • check-skipped = Unit tests (macos-latest)
    • check-success = Unit tests (macos-latest)
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-neutral = Unit tests (ubuntu-latest)
    • check-skipped = Unit tests (ubuntu-latest)
    • check-success = Unit tests (ubuntu-latest)
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-neutral = Unit tests (windows-latest)
    • check-skipped = Unit tests (windows-latest)
    • check-success = Unit tests (windows-latest)
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-neutral = API tests
    • check-skipped = API tests
    • check-success = API tests
  • #review-threads-unresolved = 0 [πŸ›‘ GitHub repository ruleset rule]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • any of: [πŸ“Œ merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-success = Testably/Conventional-Commits
    • check-neutral = Testably/Conventional-Commits
    • check-skipped = Testably/Conventional-Commits

Rule: Automatic merge for Renovate pull requests (merge)

  • #commits-behind = 0 [πŸ›‘ GitHub repository ruleset rule]
  • -closed [πŸ“Œ merge requirement]
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-neutral = Unit tests (macos-latest)
    • check-skipped = Unit tests (macos-latest)
    • check-success = Unit tests (macos-latest)
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-neutral = Unit tests (ubuntu-latest)
    • check-skipped = Unit tests (ubuntu-latest)
    • check-success = Unit tests (ubuntu-latest)
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-neutral = Unit tests (windows-latest)
    • check-skipped = Unit tests (windows-latest)
    • check-success = Unit tests (windows-latest)
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-neutral = API tests
    • check-skipped = API tests
    • check-success = API tests
  • #review-threads-unresolved = 0 [πŸ›‘ GitHub repository ruleset rule]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • author=renovate[bot]
  • any of: [πŸ“Œ merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ›‘ GitHub repository ruleset rule]
    • check-success = Testably/Conventional-Commits
    • check-neutral = Testably/Conventional-Commits
    • check-skipped = Testably/Conventional-Commits

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com