build(deps): bump github.com/rhysd/actionlint from 1.7.4 to 1.7.5 in /.ci/tools

[dependabot]

Bumps github.com/rhysd/actionlint from 1.7.4 to 1.7.5.

Release notes

Sourced from github.com/rhysd/actionlint's releases.

v1.7.5

• Strictly check available contexts in ${{ }} placeholders following the 'Context availability' table in the official document.
  • For example, jobs.<job>.env allows github context but jobs.<job>.services.<service>.env doesn't allow any contexts. Now actionlint can catch the mistake.

    jobs:
      test:
        runs-on: ubuntu-latest
        env:
          # OK. `github` context is available here.
          COMMIT_SHA: ${{ github.sha }}
        services:
          redis:
            image: redis
            env:
              # ERROR: No context is available here.
              COMMIT_SHA: ${{ github.sha }}
        steps:
          - ...

• Check a string literal passed to fromJSON() call. This pattern is popular to create array or object constants because GitHub Actions does not provide the literal syntax for them. See the document for more details. (#464)

  jobs:
    test:
      # ERROR: Key 'mac' does not exist in the object returned by the fromJSON()
      runs-on: ${{ fromJSON('{"win":"windows-latest","linux":"ubuntul-latest"}')['mac'] }}
      steps:
        - run: echo This is a special branch!
          # ERROR: Broken JSON string passed to fromJSON.
          if: contains(fromJSON('["main","release","dev"'), github.ref_name)

• Allow passing command arguments to -shellcheck argument. (#483, thanks @​anuraaga)
  • This is useful when you want to use alternative build of shellcheck like go-shellcheck.

    actionlint -shellcheck="go run github.com/wasilibs/go-shellcheck/cmd/shellcheck@latest"

• Support undocumented repository_visibility, artifact_cache_size_limit, step_summary, output, state properties in github context. (#489, thanks @​rasa for adding repository_visibility property)
• Remove macos-12 runner label from known labels because it was dropped from GitHub-hosted runners on Dec. 3 and is no longer available.
• Add windows-2025 runner label to the known labels. The runner is in public preview. (#491, thanks @​ericcornelissen)
• Add black to the list of colors for branding.color action metadata. (#485, thanks @​eifinger)
• Add table to the list of icons for branding.icon action metadata.
• Fix parsing escaped { in format() function call's first argument.
• Fix the incorrect join() function overload. join(s1: string, s2: string) was wrongly accepted.
• Update popular actions data set to the latest.
  • Add download-artifact/v3-node20 to the data set. (#468)
  • Fix missing the reviewdog/action-hadolint@v1 action input. (#487, thanks @​mi-wada)
• Link to the documents of the stable version in actionlint man page and -help output.
• Refactor LintStdin() API example and some unit tests. (#472, #475, thanks @​alexandear)
• Improve the configuration example in actionlint.yaml document to explain glob patterns for paths. (#481)

Changelog

Sourced from github.com/rhysd/actionlint's changelog.

v1.7.5 - 2024-12-28

• Strictly check available contexts in ${{ }} placeholders following the 'Context availability' table in the official document.
  • For example, jobs.<job>.env allows github context but jobs.<job>.services.<service>.env doesn't allow any contexts. Now actionlint can catch the mistake.

    jobs:
      test:
        runs-on: ubuntu-latest
        env:
          # OK. `github` context is available here.
          COMMIT_SHA: ${{ github.sha }}
        services:
          redis:
            image: redis
            env:
              # ERROR: No context is available here.
              COMMIT_SHA: ${{ github.sha }}
        steps:
          - ...

• Check a string literal passed to fromJSON() call. This pattern is popular to create array or object constants because GitHub Actions does not provide the literal syntax for them. See the document for more details. (#464)

  jobs:
    test:
      # ERROR: Key 'mac' does not exist in the object returned by the fromJSON()
      runs-on: ${{ fromJSON('{"win":"windows-latest","linux":"ubuntul-latest"}')['mac'] }}
      steps:
        - run: echo This is a special branch!
          # ERROR: Broken JSON string passed to fromJSON.
          if: contains(fromJSON('["main","release","dev"'), github.ref_name)

• Allow passing command arguments to -shellcheck argument. (#483, thanks @​anuraaga)
  • This is useful when you want to use alternative build of shellcheck like go-shellcheck.

    actionlint -shellcheck="go run github.com/wasilibs/go-shellcheck/cmd/shellcheck@latest"

• Support undocumented repository_visibility, artifact_cache_size_limit, step_summary, output, state properties in github context. (#489, thanks @​rasa for adding repository_visibility property)
• Remove macos-12 runner label from known labels because it was dropped from GitHub-hosted runners on Dec. 3 and is no longer available.
• Add windows-2025 runner label to the known labels. The runner is in public preview. (#491, thanks @​ericcornelissen)
• Add black to the list of colors for branding.color action metadata. (#485, thanks @​eifinger)
• Add table to the list of icons for branding.icon action metadata.
• Fix parsing escaped { in format() function call's first argument.
• Fix the incorrect join() function overload. join(s1: string, s2: string) was wrongly accepted.
• Update popular actions data set to the latest.
  • Add download-artifact/v3-node20 to the data set. (#468)
  • Fix missing the reviewdog/action-hadolint@v1 action input. (#487, thanks @​mi-wada)
• Link to the documents of the stable version in actionlint man page and -help output.
• Refactor LintStdin() API example and some unit tests. (#472, #475, thanks @​alexandear)
• Improve the configuration example in actionlint.yaml document to explain glob patterns for paths. (#481)

... (truncated)

Commits

• e11169d bump up version to v1.7.5
• ffd5949 update popular actions data set to the latest
• 8e2cbe9 update playground dev-dependencies (typescript v5.7 and mocha v11)
• ea8e01d Merge pull request #491 from ericcornelissen/runner-windows-2025
• 49b7457 Merge branch 'strict-available-contexts'
• d936cb4 update doc for strict context availability check
• b96989f fix tests and add test cases with no available contexts are allowed
• d5c1d55 do not allow contexts listed in 'Available Contexts' page
• d3399fe migrate script to generate problem matcher from commonjs to ESM
• 201ad96 update outdated URLs for security guide in documents
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[dependabot]

Superseded by #1073.