Description

Pins the remaining tag-based GitHub Actions in the v3 branch to full-length commit SHAs so the workflows satisfy the repository action policy and help backporting eaiser.

The pinned hashes are verified by:

$ git ls-remote https://github.com/actions/checkout.git refs/tags/v4.2.2
$ git ls-remote https://github.com/actions/setup-node.git refs/tags/v4.4.0
$ git ls-remote https://github.com/actions/cache.git refs/tags/v4.2.4
$ git ls-remote https://github.com/actions/github-script.git refs/tags/v7.0.1
11bd71901bbe5b1630ceea73d27597364c9af683        refs/tags/v4.2.2
49933ea5288caeca8642d1e84afbd3f7d6820020        refs/tags/v4.4.0
0400d5f644dc74513175e3cd8d07132dd4860809        refs/tags/v4.2.4
60a0d83039c74a4aee543508d2ffcb1c3799cdea        refs/tags/v7.0.1

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.