Bump matlab-actions/run-command from 2.1 to 3.2

[dependabot]

Bumps matlab-actions/run-command from 2.1 to 3.2.

Release notes

Sourced from matlab-actions/run-command's releases.

v3.2.0

Features

• You can control whether to generate build and test summaries in the GitHub job summary by using the generate-summary input. If you specify generate-summary as false, the action does not generate build and test summaries.

v3.1.2

Maintenance

• The Run MATLAB Command action now generates signed attestations for workflow artifacts by using the attest action.

v3.1.1

Bug Fixes

• This release fixes an issue with JSON encoding of multiple test session results for display in the GitHub job summary.

v3.1.0

Bug Fixes

• This release fixes an issue with JSON encoding of Simulink® test results for display in the GitHub job summary.

v3.0.2

Features

• To improve visual clarity, the Run MATLAB Command action no longer displays the action name when including build or test results in the GitHub job summary.

v3.0.1

Dependency Update

• This release does not include any new features. It updates the third-party libraries used by the action.

v3.0.0

Compatibility Considerations

• The Run MATLAB Command action now uses Node.js 24. Specify this version of the action in your workflow as matlab-actions/run-command@v3. GitHub-hosted runners automatically support the new action version. To use the new action version on a self-hosted runner, ensure that the runner uses GitHub Actions runner version v2.327.1 or later.

v2.4.1

Bug Fixes

• This release updates the common-utils dependency version to v1.0.1.

v2.4.0

Features

• If you have a MATLAB Test™ license, you can view your MATLAB and Simulink test results in your GitHub job summary. For more information, see View Test Results.
• You can view your MATLAB buildtool task results in your GitHub job summary.

Maintenance

• This release moves utilities to common-utils.

v2.3.0

Features

• Enabled online batch licensing.

v2.2.2

Maintenance

... (truncated)

Commits

• bcd446a Build for adaa767
• adaa767 [skip ci] Bump v3.2.0
• 67cdfd4 Add generate-job-summary input to control CI job summary generation (#98)
• e8cdbd0 [skip ci] Bump v3.1.2
• 3f8ea5f Add attestations (#99)
• 16e9f86 [skip ci] Bump v3.1.1
• b7aa89c Update common-utils version to v2.2.2 (#97)
• 51f4256 [skip ci] Bump v3.1.0
• 198e150 Update common-utils version to v2.2.1 (#96)
• b2bfb1b [skip ci] Bump v3.0.2
• 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 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)

[github-actions]

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, 👼 SARIF report, or 📝 job summary for details.

Unrecognized words (6)

ARWHEAD
cellstr
CERI
hardcoded
submaxfun
whitespaces

To accept these unrecognized words as correct, you could run the following commands

... in a clone of the git@github.com:blockwise-direct-search/bds.git repository
on the dependabot/github_actions/matlab-actions/run-command-3.2 branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/v0.0.26/apply.pl' |
perl - 'https://github.com/blockwise-direct-search/bds/actions/runs/27591402392/attempts/1' &&
git commit -m 'Update check-spelling metadata'

OR

To have the bot accept them for you, comment in the PR quoting the following line:
@check-spelling-bot apply updates.

Available 📚 dictionaries could cover words not in the 📘 dictionary

Dictionary	Entries	Covers	Uniquely
cspell:python/src/common/extra.txt	741	1	1
cspell:software-terms/dict/softwareTerms.txt	1288	1	1

Consider adding them (in .github/workflows/spelling.yml) in jobs:/spelling: for uses: check-spelling/check-spelling@v0.0.26 in its with:

        with:
          extra_dictionaries: |
            cspell:python/src/common/extra.txt
            cspell:software-terms/dict/softwareTerms.txt

ℹ️ Because this workflow is running on: pull_request_target, changes to this workflow file will not take effect as part of a pull request (including this one). You should:

1. Create a new branch.
2. Add dictionaries to the workflow file (.github/workflows/spelling.yml) on that branch.
3. Test them by pushing that branch.
4. Do not remove entries from expect files on that branch because the workflow changes that will eventually provide the dictionary coverage won't be applicable to the workflow in the corresponding pull request (they are only available after they're merged to the branch).
5. Once that branch is merged, you can remove the entries that are no longer needed in another branch.

---

To stop checking additional dictionaries, add (in .github/workflows/spelling.yml) for uses: check-spelling/check-spelling@v0.0.26 in its with:

check_extra_dictionaries: ""

Warnings ⚠️ (3)

See the 📂 files view, the 📜action log, 👼 SARIF report, or 📝 job summary for details.

⚠️ Warnings	Count
⚠️ bad-regex	2
⚠️ duplicate-pattern	2
⚠️ non-alpha-in-dictionary	12

See ⚠️ Event descriptions for more information.

If the flagged items are 🤯 false positives

If items relate to a ...

• binary file (or some other file you wouldn't want to check at all).

  Please add a file path to the excludes.txt file matching the containing file.

  File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

  ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

• well-formed pattern.

  If you can write a pattern that would match it,
  try adding it to the patterns.txt file.

  Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

  Note that patterns can't match multiline strings.