chore(deps): update github actions

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
jupyterlab/maintainer-tools	action	digest	affc83b -> d72f5cb
qltysh/qlty-action	action	digest	a192421 -> 92420f3

---

Configuration

📅 Schedule: 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 is behind base branch, 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.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated pinned commit hashes for GitHub Actions across multiple workflows. The jupyterlab/maintainer-tools base-setup and related action references were changed from commit affc83be6020d529b9368cd4d63e467877606600 to d72f5cb72b472c1e59036840891e918c9bda4dae in Build, Check Links, check-release, ci(.yml/.yaml), prep-release, publish-release, and update-integration-tests workflows. In .github/workflows/ci.yml the qlty install SHA was updated from a19242102d17e497f437d7466aa01b528537e899 to 92420f3093ba65970fed22ce5f162ecb8a5c1700. No steps, inputs, control flow, or public API signatures were otherwise modified.

Sequence Diagram(s)

No control-flow or feature changes; sequence diagram not applicable.

Possibly related PRs

• chore(deps): pin jupyterlab/maintainer-tools action to affc83b #29 — touches the same jupyterlab/maintainer-tools base-setup action usage that this PR updates.
• chore(deps): pin dependencies #20 — previously updated the jupyterlab/maintainer-tools pin now replaced by this PR.
• chore(deps): pin dependencies vscode-deepnote#85 — updates the qlty action digest in .github/workflows/ci.yml (overlaps with this PR).

Suggested reviewers

• saltenasl
• Artmann
• andyjakubowski
• jamesbhobbs

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "chore(deps): update github actions" accurately reflects the changeset's primary purpose: updating GitHub Actions references across multiple workflow files. The title is clear and specific enough that a developer scanning history would immediately understand this is a dependency update for GitHub Actions. While the title doesn't specify which actions were updated (jupyterlab/maintainer-tools and qlty-action), it covers the main change without being misleading or overly vague.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.20%. Comparing base (aa44b74) to head (d254669).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #33   +/-   ##
=======================================
  Coverage   50.20%   50.20%           
=======================================
  Files          13       13           
  Lines         249      249           
  Branches       26       26           
=======================================
  Hits          125      125           
  Misses        119      119           
  Partials        5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[andyjakubowski]

We’ll request Renovate to retry after we merge #35 into main