Skip to content
OpenSpec Sync

fix(e2e): the chrome destinations are a named gap, not a mystery fail… #14

Sign in to view logs

fix(e2e): the chrome destinations are a named gap, not a mystery fail…

fix(e2e): the chrome destinations are a named gap, not a mystery fail… #14

Triggered via push September 5, 2026 14:59
@rubenvdlinderubenvdlinde
pushed 5aacaf1
development
Status Success
Total duration 4m 42s
Artifacts –

openspec-sync.yml

on: push
sync  /  Sync OpenSpec to GitHub Issues
4m 37s
sync / Sync OpenSpec to GitHub Issues
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 1 notice
sync / Sync OpenSpec to GitHub Issues
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/github-script@v7. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
sync / Sync OpenSpec to GitHub Issues
OpenSpec issues will be created and updated, but NOT placed on the project board or given a Status. ProjectsV2 needs a project-scoped token and this run uses GITHUB_TOKEN. See ConductionNL/.github#432.