Skip to content

ci: add zizmor workflow and update playwright [backport to v4]#10663

Open
hi-ogawa wants to merge 5 commits into
vitest-dev:v4from
hi-ogawa:backport/zizmor-v4
Open

ci: add zizmor workflow and update playwright [backport to v4]#10663
hi-ogawa wants to merge 5 commits into
vitest-dev:v4from
hi-ogawa:backport/zizmor-v4

Conversation

@hi-ogawa

@hi-ogawa hi-ogawa commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

Description

v4 branch merge (e.g. #10661) is blocked by missing zizmor https://github.com/vitest-dev/vitest/settings/rules/16737607

Let's try adding back zizmor to v4.

To make zizmor pass easily, workflows that are useless on backport v4 branches yml are removed like the ones with old issues-helper.

Also updated playwright since playwright 1.59 + node 24 hangs install.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
  • Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

hi-ogawa and others added 2 commits June 26, 2026 09:59
Co-authored-by: OpenCode (claude-opus-4-8) <noreply@opencode.ai>
Apply workflow hardening to satisfy zizmor:
- add persist-credentials: false to checkouts in ci.yml and cr.yml
- drop the debug 'Print versions' step (template-injection) from
  setup-playwright action
- add .github/zizmor.yml to ignore concurrency-limits for publish.yml

Remove repo-management workflows that only run from the default branch
(main) and never execute on v4, so they only produced zizmor noise:
ecosystem-ci-trigger, issue-close-require, lock-closed-issues,
issue-labeled, pr-labeled-automated.

Co-authored-by: OpenCode (claude-opus-4-8) <noreply@opencode.ai>
@hi-ogawa hi-ogawa marked this pull request as ready for review June 26, 2026 01:12
@hi-ogawa hi-ogawa requested a review from sheremet-va June 26, 2026 01:13
hi-ogawa and others added 2 commits June 26, 2026 10:39
The push trigger is inert on v4 (push events use the branch's own
workflow file, filtered to main), but gating relies on the
pull_request trigger, which works regardless. Keeping the file
identical to main avoids drift.

Co-authored-by: OpenCode (claude-opus-4-8) <noreply@opencode.ai>
Playwright <1.60.0 hangs after the browser zip download completes on
Node.js 24.16.0 due to a Node regression in zip extraction
(nodejs/node#63487, microsoft/playwright#41000). This stalls the
node-24 browser CI jobs on v4 until they time out. Bump to ^1.61.0,
matching main, where the issue is resolved.

Co-authored-by: OpenCode (claude-opus-4-8) <noreply@opencode.ai>
@hi-ogawa hi-ogawa changed the title ci: add zizmor workflow [backport to v4] ci: add zizmor workflow and update playwright [backport to v4] Jun 26, 2026
Playwright 1.60+ run-server binds to ::1 (IPv6) when host is
localhost, so the test's 'Listening on ws://localhost:9898' wait
never matches the 'ws://[::1]:9898/' output and times out. Pass
--host 127.0.0.1 --unsafe and use 127.0.0.1 everywhere, matching
main (vitest-dev#10426).

Co-authored-by: OpenCode (claude-opus-4-8) <noreply@opencode.ai>
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.

1 participant