chore(deps): update github-actions versions

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	minor	6.0.3 → 6.1.0
amannn/action-semantic-pull-request	action	minor	v6 → v6.1.1

Warnings (1)

Please correct - or verify that you can safely ignore - these warnings before you merge this PR.

• actions/checkout: Could not determine new digest for update (github-tags package actions/checkout)

---

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

actions/checkout (actions/checkout)

v6.1.0

Compare Source

amannn/action-semantic-pull-request (amannn/action-semantic-pull-request)

v6.1.1

Compare Source

Bug Fixes

• Parse headerPatternCorrespondence properly (#​295) (800da4c)

v6.1.0

Compare Source

Features

• Support providing regexps for types (#​292) (a30288b)

Bug Fixes

• Remove trailing whitespace from "unknown release type" error message (#​291) (afa4edb)

v6.0.1

Compare Source

Bug Fixes

• Actually execute action (#​289) (58e4ab4)

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • "on the 15th day of the month before 12pm"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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.

[greptile-apps]

Greptile Summary

This PR updates the pinned actions/checkout revision across CI, documentation, lint, and release workflows. It also relabels the semantic pull-request action as v6.1.1 without updating the executable SHA.

Confidence Score: 4/5

The semantic pull-request action update should be corrected before merging because the workflow still executes the old pinned revision.

The checkout upgrades consistently change their immutable references, but the semantic action change modifies only a comment and therefore does not apply the advertised dependency update.

Files Needing Attention: .github/workflows/lint-pr-title.yml

Important Files Changed

Filename	Overview
.github/workflows/ci.yml	Updates the immutable checkout action reference from 6.0.3 to 6.1.0.
.github/workflows/docs.yml	Updates the documentation workflow's checkout action reference to 6.1.0.
.github/workflows/lint-pr-title.yml	Changes only the semantic action's version comment, leaving the executed SHA unchanged.
.github/workflows/lint.yml	Updates the lint workflow's checkout action reference to 6.1.0.
.github/workflows/release-please.yml	Updates both checkout references used by release automation to 6.1.0.
.github/workflows/release.yml	Updates the release workflow's checkout action reference to 6.1.0.

Prompt To Fix All With AI

### Issue 1
.github/workflows/lint-pr-title.yml:18
**Semantic action remains on old revision**

When pull-request title validation runs, GitHub Actions resolves the action from the unchanged immutable SHA rather than the updated version comment, causing the workflow to continue using the previous action revision without the v6.1.1 fixes and features.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "chore(deps): update github-actions versi..." | Re-trigger Greptile}

[greptile-apps]

Semantic action remains on old revision

When pull-request title validation runs, GitHub Actions resolves the action from the unchanged immutable SHA rather than the updated version comment, causing the workflow to continue using the previous action revision without the v6.1.1 fixes and features.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/lint-pr-title.yml
Line: 18

Comment:
**Semantic action remains on old revision**

When pull-request title validation runs, GitHub Actions resolves the action from the unchanged immutable SHA rather than the updated version comment, causing the workflow to continue using the previous action revision without the v6.1.1 fixes and features.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.