chore(deps): update github-actions

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	minor	v6.0.3 → v6.1.0
dtolnay/rust-toolchain (changelog)	action	digest	4be7066 → 4cda84d
github/codeql-action	action	patch	v4.37.0 → v4.37.4
ossf/scorecard-action	action	patch	v2.4.3 → v2.4.4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

actions/checkout (actions/checkout)

v6.1.0

Compare Source

github/codeql-action (github/codeql-action)

v4.37.4

Compare Source

v4.37.3

Compare Source

No user facing changes.

v4.37.2

Compare Source

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #​4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #​4007

v4.37.1

Compare Source

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #​3956
• Update default CodeQL bundle version to 2.26.1. #​4019

ossf/scorecard-action (ossf/scorecard-action)

v2.4.4

Compare Source

What's Changed

This update bumps the Scorecard version to the v5.5.0 release. For a complete list of changes, please refer to the Scorecard v5.4.0 release notes and the Scorecard v5.5.0 release notes.

• log POST failures instead of failing entire action by @​spencerschrock in #​1625

Full Changelog: ossf/scorecard-action@v2.4.3...v2.4.4

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Omen Analysis

Diff Risk

Risk Score	27%
Risk Level	LOW
Files Modified	3
Lines Added	+14
Lines Deleted	-14
Commits	2

Risk Factors

Factor	Score
file_churn	0.1
entropy	0.0696
num_files	0.016
commits	0.0140
ownership_diffusion	0.0083
lines_added	0.0056
lines_deleted	0.0056
file_complexity	0

Recommendations

• Touches historically volatile files - changes here often introduce bugs

Repository Health

Health Score	79.07701402745926 / 100
Grade	C
Files Analyzed	112
Critical Issues	1

Score Components

Component	Score	Weight
complexity	96	1
duplication	42.6	0.8
cohesion	94.5	0.6
tdg	85.5	0.6
coupling	54.5	0.4
satd	91.1	0.4
smells	100	0.2

Tips for AI agents

Use these commands to investigate and improve low-scoring areas.

Run full analysis:

omen -f json score    # health score with component breakdown
omen -f json diff     # PR risk analysis
omen hotspot          # high-churn + high-complexity files

Coupling (score: 54.51428571428571) -- needs attention

omen graph && omen smells

Break cyclic dependencies by introducing interfaces or extracting shared types. Reduce fan-out from hub modules by splitting responsibilities.

---

Duplication (score: 42.58687258687259) -- needs attention

omen clones

Look for Type-1 (exact) and Type-2 (renamed) clones. Extract shared logic into reusable functions or modules. Prioritize clones in high-churn files.

---

General workflow for improving scores:

1. Run the relevant analyzer command to identify specific files
2. Focus on the highest-weight components first (complexity 25%, duplication 20%, cohesion 15%, TDG 15%)
3. Make targeted improvements -- small refactors that reduce complexity or eliminate duplication
4. Re-run omen score to verify improvement

[open-cla]

Contributor License Agreement

All contributors are covered by a CLA.