Skip to content

Request to add matlab-actions/run-tests Action to allow list #644

Open
sgilmore10 wants to merge 2 commits intoapache:mainfrom
sgilmore10:matlab-actions-run-tests
Open

Request to add matlab-actions/run-tests Action to allow list #644
sgilmore10 wants to merge 2 commits intoapache:mainfrom
sgilmore10:matlab-actions-run-tests

Conversation

@sgilmore10
Copy link
Copy Markdown
Member

Overview

Action name: run-tests
Action URL: https://github.com/matlab-actions/run-tests
Version to pin: 4a3d2e8bdc811f72defb8122e46a009312acc198

Action Description

From the Run Tests README.md:

The Run MATLAB Tests action enables you to run MATLAB® and Simulink® tests and generate test and coverage artifacts on a GitHub®-hosted or self-hosted runner.

Motivation

The apache/arrow repository uses the matlab-actions/run-tests action to run automated MATLAB unit tests in its CI/CD pipeline to test the MATLAB Apache Arrow bindings. However, beginning on March 20th, the MATLAB CI checks have not been able to run because matlab-actions/run-tests is not on the allow list.

Related PRs


Checklist

  • The action is listed in the GitHub Actions Marketplace
  • The action is not already on the list of approved actions
  • The action has a sufficient number of contributors or has contributors within the ASF community (It is actively maintained by MathWorks/has 9 contributors)
  • The action has a clearly defined license
  • The action is actively developed or maintained
  • The action has CI/unit tests configured
  • Compiled JavaScript in dist/ matches a clean rebuild (verify with uv run utils/verify-action-build.py org/repo@hash) (Don't think this applies since matlab-actions/setup-matlab does not have a dist folder).

@raboof
Copy link
Copy Markdown
Member

raboof commented Apr 1, 2026

I see this action is only used in apache/arrow and the workflow has permissions: contents: read which makes it easier to trust, even though there seems to be a bunch of generated code in 'dist' and 'lib'.

We have utils/verify-action-build.py to verify this generated code, but that doesn't seem to quite work for this action yet.

Given the permissions are limited and we trusted the publisher I'm leaning towards approving this PR. Could you update it to keep the alphabetical ordering, though?

@raboof
Copy link
Copy Markdown
Member

raboof commented Apr 1, 2026

[ ] Compiled JavaScript in dist/ matches a clean rebuild (verify with uv run utils/verify-action-build.py org/repo@hash) (Don't think this applies since matlab-actions/setup-matlab does not have a dist folder).

looking at matlab-actions/run-tests@4a3d2e8 it definitely seems to

@sgilmore10
Copy link
Copy Markdown
Member Author

[ ] Compiled JavaScript in dist/ matches a clean rebuild (verify with uv run utils/verify-action-build.py org/repo@hash) (Don't think this applies since matlab-actions/setup-matlab does not have a dist folder).

looking at matlab-actions/run-tests@4a3d2e8 it definitely seems to

I must have missed that. My apologies!

@raboof
Copy link
Copy Markdown
Member

raboof commented Apr 1, 2026

No worries!

@sgilmore10 sgilmore10 force-pushed the matlab-actions-run-tests branch from edb85d2 to d511c85 Compare April 1, 2026 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants