chore(deps): update all ci non-major dependencies

[turo-dependency-manager-app]

This PR contains the following updates:

Package	Type	Update	Change
alessandrojcm/commitlint-pre-commit-hook	repository	minor	v9.18.0 -> v9.20.0
rhysd/actionlint	repository	patch	v1.7.1 -> v1.7.4

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

---

Release Notes

alessandrojcm/commitlint-pre-commit-hook (alessandrojcm/commitlint-pre-commit-hook)

v9.20.0

Compare Source

Features

• bump the commitlint group with 2 updates (4a3054c)

v9.19.0

Compare Source

Features

• bump the commitlint group with 2 updates (ff83bce)

rhysd/actionlint (rhysd/actionlint)

v1.7.4

Compare Source

• Disallow the usage of popular actions that run on node16 runner. The node16 runner will reach the end of life on November 12.
  • In case of the error, please update your actions to the latest version so that they run on the latest node20 runner.
  • If you're using self-hosted runner and you cannot upgrade your runner to node20 soon, please consider to ignore the error by the paths configuration described below.
  • If you're using actions/upload-artifact@v3 and actions/download-artifact@v3 on GHES, please replace them with actions/upload-artifact@v3-node20 and actions/download-artifact@v3-node20. (#​468)
• Provide the configuration for ignoring errors by regular expressions in actionlint.yml (or actionlint.yaml). Please see the document for more details. (#​217, #​342)
  • The paths is a mapping from the file path glob pattern to the corresponding configuration. The ignore configuration is a list of regular expressions to match error messages (similar to the -ignore command line option).

    paths:

This pattern matches any YAML file under the '.github/workflows/' directory.

  .github/workflows/**/*.yaml:
    ignore:

Ignore the specific error from shellcheck

      - 'shellcheck reported issue in this script: SC2086:.+'

This pattern only matches '.github/workflows/release.yaml' file.

  .github/workflows/release.yaml:
    ignore:

Ignore errors from the old runner check. This may be useful for (outdated) self-hosted runner environment.

      - 'the runner of ".+" action is too old to run on GitHub Actions'
```

• This configuration was not implemented initially because I wanted to keep the configuration as minimal as possible. However, due to several requests for it, the configuration has now been added.
• Untrusted inputs check is safely skipped inside specific function calls. (#​459, thanks @​IlyaGulya)
  • For example, the following step contains the untrusted input github.head_ref, but it is safe because it's passed to the contains() argument.

    - run: echo "is_release_branch=${{ contains(github.head_ref, 'release') }}" >> "$GITHUB_OUTPUT"

  • For more details, please read the rule document.
• Recognize gcr.io and gcr.dev as the correct container registry hosts. (#​463, thanks @​takaidohigasi)
  • Note that it is recommended explicitly specifying the scheme like docker://gcr.io/....
• Remove macos-x.0 runner labels which are no longer available. (#​452)
• Disable shellcheck SC2043 rule because it can cause false positives on checking run:. (#​355)
  • The rule document was updated as well. (#​466, thanks @​risu729)
• Fix the error message was not deterministic when detecting cycles in needs dependencies.
• Fix the check for format() function was not applied when the function name contains upper case like Format(). Note that function names in ${{ }} placeholders are case-insensitive.
• Update the popular actions data set to the latest.
  • This includes the new ref and commit outputs of actions/checkout.
• Add actions/cache/save and actions/cache/restore to the popular actions data set.
• Links in the README.md now point to the document of the latest version tag instead of HEAD of main branch.
• Add Linter.LintStdin method dedicated to linting STDIN instead of handling STDIN in Command.
• (Dev) Add new check-checks script to maintain the 'Checks' document. It automatically updates the outputs and playground links for example inputs in the document. It also checks the document is up-to-date on CI. Please read the document for more details.

Documentation

[Changes][v1.7.4]

v1.7.3

Compare Source

• Remove macos-11 runner labels because macOS 11 runner was dropped on 6/28/2024. (#​451, thanks @​muzimuzhi)
• Support macos-15, macos-15-large, and macos-15-xlarge runner labels. The macOS 15 runner is not globally available yet, but they are available in beta. (#​453, thanks @​muzimuzhi)
• Release artifact includes checksums for the released binaries. The file name is actionlint_{version}_checksums.txt. (#​449)
  • For example, the checksums for v1.7.3 can be found here.
• Fix download-path output is missing in actions/download-artifact@v3 action. (#​442)
  • Note that the latest version actions/download-artifact@v4 was not affected by this issue.
• Support Go 1.23.

Documentation

[Changes][v1.7.3]

v1.7.2

Compare Source

• Fix child processes to run in parallel.
• Update the popular actions data set to the latest. (#​442, #​445, #​446, #​447, thanks @​maikelvdh)
• Add support for checking branch filters on merge_group event. (#​448, thanks @​muzimuzhi)
• The playground now supports both light and dark modes and automatically applies the system's theme.
• Fix releasing a failure on making a new winget package. (#​438, thanks @​vedantmgoyal9)

[Changes][v1.7.2]

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 has been generated by Renovate Bot.

[github-actions]

Release notes preview

No new release will be created.

If you are expecting a release, you will need to either fix a bug or add a feature.
Chores, CI, docs, refactoring, style and other changes will not trigger a release.