Bump matlab-actions/setup-matlab from 2.1.2 to 3.0.1

[dependabot]

Bumps matlab-actions/setup-matlab from 2.1.2 to 3.0.1.

Release notes

Sourced from matlab-actions/setup-matlab's releases.

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 Setup MATLAB action now uses Node.js 24. Specify this version of the action in your workflow as matlab-actions/setup-matlab@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.7.0

Features

• You can control how to install the system dependencies for MATLAB on a runner by using the new install-system-dependencies input of the Setup MATLAB action. For example, if you specify the input as true, the action automatically installs the required dependencies. For more information, see Set Up MATLAB.

v2.6.1

Bug Fixes

• The Setup MATLAB action now sets up the specified products regardless of the contents of the tool cache on a self-hosted runner. Previously, if the runner’s tool cache contained MATLAB and other MathWorks products from an earlier setup, subsequent runs of the action ignored any newly specified products in the workflow file.

v2.6.0

Features

• With the cache input specified as true, the action now caches MATLAB if it is set up successfully. Previously, the action cached MATLAB only if the entire job completed successfully.

Maintenance

• Action dependencies have been updated based on npm audit and npm outdated.

v2.5.0

Features

• Upgraded the actions/cache package to v4.

v2.4.0

Features

• On Windows® systems, the Setup MATLAB action automatically adds the MATLAB Runtime folder to the PATH system environment variable.

v2.3.1

Bug Fixes

• You can use the Setup MATLAB action multiple times within a workflow to set up different releases of MATLAB. Previously, attempting to set up different releases in the same workflow resulted in an error. For more information, see #130.

v2.3.0

Features

• All HTTP clients now include retries for improved robustness.

v2.2.0

• Install Intel version of MATLAB on Apple silicon runners when a release prior to R2023b is requested

Commits

• a0180c9 Build for 421beef
• 421beef [skip ci] Bump v3.0.1
• 245ed85 Format and update actions (#193)
• cd7fcc5 Bump handlebars from 4.7.8 to 4.7.9 (#188)
• 47dd637 Bump brace-expansion (#189)
• 89267e6 [skip ci] Bump v3.0.0
• 72bbaca Update checkout action's version
• 2881f9b Replace v2 with v3
• d48da49 Use node24 actions for workflows (#191)
• a85f4bd Bump picomatch from 2.3.1 to 2.3.2 (#190)
• 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/setup-matlab-3.0.1 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/27591380824/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.