Image builds now run on the dejima-privileged runner label, since they run docker builds; a comment in the workflow notes that jobs without docker builds should use dejima-confined. There are no such jobs yet.
The matrix jobs are now named app, session-manager and streamer instead of build (., dotcom-arcade) and so on.
The publishing section of the deployment docs mentions the runner labels.
Tested by parsing the workflow (runner label, job name and matrix names as expected). The real run happens on merge to main.
**Summary generated by LLM agent**
Image builds now run on the `dejima-privileged` runner label, since they run docker builds; a comment in the workflow notes that jobs without docker builds should use `dejima-confined`. There are no such jobs yet.
The matrix jobs are now named `app`, `session-manager` and `streamer` instead of `build (., dotcom-arcade)` and so on.
The publishing section of the deployment docs mentions the runner labels.
Tested by parsing the workflow (runner label, job name and matrix names as expected). The real run happens on merge to `main`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary generated by LLM agent
Image builds now run on the
dejima-privilegedrunner label, since they run docker builds; a comment in the workflow notes that jobs without docker builds should usedejima-confined. There are no such jobs yet.The matrix jobs are now named
app,session-managerandstreamerinstead ofbuild (., dotcom-arcade)and so on.The publishing section of the deployment docs mentions the runner labels.
Tested by parsing the workflow (runner label, job name and matrix names as expected). The real run happens on merge to
main.