chore(deps): update github actions to v3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
nick-fields/assert-action	action	major	v2.0.0 → v3.0.0	v4.0.1 (+3)
nick-fields/assert-action	action	major	v2 → v3	v4.0.1 (+3)

---

Release Notes

nick-fields/assert-action (nick-fields/assert-action)

v3.0.0: Upgrade to node24

Compare Source

What's Changed

• feat!: Upgrade to Node.js 24 by @​dylanmtaylor in #​47

New Contributors

• @​dylanmtaylor made their first contribution in #​47

Full Changelog: nick-fields/assert-action@v2...v3.0.0

v3

Compare Source

---

Configuration

📅 Schedule: (in timezone Europe/Paris)

• Branch creation
  • "after 7am every weekday,before 8pm every weekday"
• 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 these updates again.

---

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

---

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

[sonar-review-alpha]

Summary

This PR updates the nick-fields/assert-action action from v2.0.0 to v3.0.0 across the integration test workflow. The major version bump is driven by an upgrade to Node.js 24. All five action references in .github/workflows/it-test.yml are updated consistently with the new version tag and commit hash.

What reviewers should know

What to review:

• Verify the commit hash 22dd2a66ef733fe92022d3704183ac007463eecb matches the published v3.0.0 tag on the upstream repository
• Check that all five workflow step references are updated (lines 33, 52, 71, 90, 109)
• Ensure the test workflow still executes successfully after this change — the assertions themselves haven't changed, only the action that runs them

Non-obvious points:

• This is a Node.js runtime environment change only; no API or input/output changes are involved
• The workflow uses a pinned commit hash in addition to the version tag, which is good practice for reproducibility

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonarqubecloud]

SonarQube reviewer guide

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined

Post-upgrade command 'pre-commit autoupdate --freeze || true' has not been added to the allowed list in allowedCommands

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonar-review-alpha]

LGTM! ✅

The update is incomplete. The file contains 6 references to nick-fields/assert-action, but only 5 were updated to the v3 SHA. The first job, it-tests-use-input-default-values (line 16), still pins the old v2 SHA (aa0067e01f0f6545c31755d6ca128c5a3a14f6bf # v2). After this PR merges, that job will run on a different Node.js runtime (Node 18/20 via v2) than all other test jobs (Node 24 via v3), creating an inconsistent test environment.

Line 16 was not touched by this PR so it falls outside the diff hunks — it needs to be updated to:

- uses: nick-fields/assert-action@22dd2a66ef733fe92022d3704183ac007463eecb # v3.0.0

🗣️ Give feedback

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud