This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [actions/setup-dotnet](https://github.com/actions/setup-dotnet) | action | major | `v5` → `v6` |
---
### Release Notes
<details>
<summary>actions/setup-dotnet (actions/setup-dotnet)</summary>
### [`v6.0.0`](https://github.com/actions/setup-dotnet/releases/tag/v6.0.0)
[Compare Source](https://github.com/actions/setup-dotnet/compare/v6.0.0...v6.0.0)
##### What's Changed
- Migrate to ESM and upgrade dependencies by [@​priyagupta108](https://github.com/priyagupta108) in [#​752](https://github.com/actions/setup-dotnet/pull/752)
- Bump actions/checkout from 6.0.3 to 7.0.0 by [@​dependabot](https://github.com/dependabot)\[bot] in [#​751](https://github.com/actions/setup-dotnet/pull/751)
- chore(deps): bump [@​actions/cache](https://github.com/actions/cache) to 6.2.0 by [@​philip-gai](https://github.com/philip-gai) in [#​756](https://github.com/actions/setup-dotnet/pull/756)
##### New Contributors
- [@​philip-gai](https://github.com/philip-gai) made their first contribution in [#​756](https://github.com/actions/setup-dotnet/pull/756)
**Full Changelog**: <https://github.com/actions/setup-dotnet/compare/v5...v6.0.0>
### [`v6`](https://github.com/actions/setup-dotnet/compare/v5.4.0...v6.0.0)
[Compare Source](https://github.com/actions/setup-dotnet/compare/v5.4.0...v6.0.0)
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNjUuNCIsInVwZGF0ZWRJblZlciI6IjQ0LjQuNSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
Risky changes:actions/setup-dotnet v6 is a major CI action upgrade that migrates to ESM and updates transitive checkout/cache tooling in the combined PR/push workflow.
Are we affected?Likely, with positive compatibility evidence. Exact-head PR and push checks are green, but every future Meeting Assistant build/test run depends on this control-plane path.
Risk: Runner, cache, checkout, or credential behavior can regress later build and delivery jobs even though this head passed once.
Recommendation: CI/CD control-plane changes are high risk by automation policy. Use an attended explicit manual merge outside automations, monitor the first main run, and keep v5 ready for rollback.
### Weekly automation risk assessment (2026-07-23)
- **Risky changes:** `actions/setup-dotnet` v6 is a major CI action upgrade that migrates to ESM and updates transitive checkout/cache tooling in the combined PR/push workflow.
- **Are we affected?** **Likely, with positive compatibility evidence.** Exact-head PR and push checks are green, but every future Meeting Assistant build/test run depends on this control-plane path.
- **Risk:** Runner, cache, checkout, or credential behavior can regress later build and delivery jobs even though this head passed once.
- **Recommendation:** CI/CD control-plane changes are high risk by automation policy. Use an **attended explicit manual merge outside automations**, monitor the first main run, and keep v5 ready for rollback.
Weekly status: classification remains high risk under the CI/CD control-plane policy. Compatibility evidence is strong—both exact-head runs succeeded, v5 and v6 retain the same Node 24 action interface, and setup-dotnet caching is not enabled—but main has advanced since those checks. Renovate rebase/retry requested. Require fresh successful validation, then use an attended explicit manual merge outside automation and monitor the first main push run. Rollback is the one-line workflow reference back to v5; no application or data migration is involved.
Weekly status: classification remains **high risk under the CI/CD control-plane policy**. Compatibility evidence is strong—both exact-head runs succeeded, v5 and v6 retain the same Node 24 action interface, and setup-dotnet caching is not enabled—but `main` has advanced since those checks. Renovate rebase/retry requested. Require fresh successful validation, then use an attended explicit manual merge outside automation and monitor the first `main` push run. Rollback is the one-line workflow reference back to v5; no application or data migration is involved.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
v5→v6Release Notes
actions/setup-dotnet (actions/setup-dotnet)
v6.0.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/actions/setup-dotnet/compare/v5...v6.0.0
v6Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
Weekly automation risk assessment (2026-07-23)
actions/setup-dotnetv6 is a major CI action upgrade that migrates to ESM and updates transitive checkout/cache tooling in the combined PR/push workflow.Weekly status: classification remains high risk under the CI/CD control-plane policy. Compatibility evidence is strong—both exact-head runs succeeded, v5 and v6 retain the same Node 24 action interface, and setup-dotnet caching is not enabled—but
mainhas advanced since those checks. Renovate rebase/retry requested. Require fresh successful validation, then use an attended explicit manual merge outside automation and monitor the firstmainpush run. Rollback is the one-line workflow reference back to v5; no application or data migration is involved.e2ad41f951to819547219aView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.