Skip to content

ci: time-limit the Playwright install in the publish workflow - #17

Merged
asif7774 merged 4 commits into
mainfrom
chore/publish-timeout
Oct 27, 2026
Merged

asif7774 merged 4 commits into
mainfrom
chore/publish-timeout

Conversation

@asif7774

Copy link
Copy Markdown
Member

Adds timeout-minutes: 10 to the Playwright browser install step in npm-publish.yml, matching ci.yml (#16). Without it, a stalled download holds the publish job until GitHub's 6-hour default.

Also renames the step from "Install Chromium for browser tests" to "Install Playwright browsers", since it installs Chromium, Firefox and WebKit.

No library code changes.

A stalled browser download would hold the publish job until GitHub's
6-hour default; ci.yml already caps the same step at 10 minutes. Also
renames the step, which installs all three engines, not only Chromium.
@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Security Evidence

Commit: b7268083726fa1344a5e727be94d75cef24b0c73

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 1 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Risk Taxonomy

Commit: b7268083726fa1344a5e727be94d75cef24b0c73

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 1 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

  • 1 security-sensitive path(s) changed

Paths:

  • .github/workflows/npm-publish.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

  • CI workflow changes may ship without failure-mode evidence
  • Dependency or CI drift could surface after merge
  • 1 CI or workflow path(s) changed

Paths:

  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Reference Set Readiness

Commit: b7268083726fa1344a5e727be94d75cef24b0c73

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 1 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Missing Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence Missing Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Hosted Promotion Readiness

Commit: b7268083726fa1344a5e727be94d75cef24b0c73

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 1 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Config Audit

Commit: b7268083726fa1344a5e727be94d75cef24b0c73

No changed-config issues detected (success)

Scanned 1 config file(s) present at this commit across 1 changed config path(s) and found no issues in the supported security rules.

Changed config files:

  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Harness Audit

Commit: b7268083726fa1344a5e727be94d75cef24b0c73

No harness issues detected (success)

Scanned 1 changed config file(s) and found no harness issues.

Changed config files:

  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Security Evidence

Commit: 38f4a526a28714befad757f578a2840066b4ba73

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 2 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Risk Taxonomy

Commit: 38f4a526a28714befad757f578a2840066b4ba73

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 2 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

  • 2 security-sensitive path(s) changed

Paths:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

  • CI workflow changes may ship without failure-mode evidence
  • Dependency or CI drift could surface after merge
  • 2 CI or workflow path(s) changed

Paths:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Reference Set Readiness

Commit: 38f4a526a28714befad757f578a2840066b4ba73

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 2 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Missing Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence Missing Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Hosted Promotion Readiness

Commit: 38f4a526a28714befad757f578a2840066b4ba73

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 2 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Config Audit

Commit: 38f4a526a28714befad757f578a2840066b4ba73

No changed-config issues detected (success)

Scanned 2 config file(s) present at this commit across 2 changed config path(s) and found no issues in the supported security rules.

Changed config files:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Harness Audit

Commit: 38f4a526a28714befad757f578a2840066b4ba73

No harness issues detected (success)

Scanned 2 changed config file(s) and found no harness issues.

Changed config files:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Security Evidence

Commit: fc2f7482bb3a70f60138a3c3a23a08446a8ec433

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 2 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Risk Taxonomy

Commit: fc2f7482bb3a70f60138a3c3a23a08446a8ec433

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 2 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

  • 2 security-sensitive path(s) changed

Paths:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

  • CI workflow changes may ship without failure-mode evidence
  • Dependency or CI drift could surface after merge
  • 2 CI or workflow path(s) changed

Paths:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Reference Set Readiness

Commit: fc2f7482bb3a70f60138a3c3a23a08446a8ec433

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 2 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Missing Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence Missing Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / Hosted Promotion Readiness

Commit: fc2f7482bb3a70f60138a3c3a23a08446a8ec433

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 2 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Config Audit

Commit: fc2f7482bb3a70f60138a3c3a23a08446a8ec433

No changed-config issues detected (success)

Scanned 2 config file(s) present at this commit across 2 changed config path(s) and found no issues in the supported security rules.

Changed config files:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 26, 2026

Copy link
Copy Markdown

ECC Tools / PR Harness Audit

Commit: fc2f7482bb3a70f60138a3c3a23a08446a8ec433

No harness issues detected (success)

Scanned 2 changed config file(s) and found no harness issues.

Changed config files:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 27, 2026

Copy link
Copy Markdown

ECC Tools / Security Evidence

Commit: 0268d9f3ce7345e6dffe397222f0f9ac96b0b1a9

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 2 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 27, 2026

Copy link
Copy Markdown

ECC Tools / PR Risk Taxonomy

Commit: 0268d9f3ce7345e6dffe397222f0f9ac96b0b1a9

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 2 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

  • 2 security-sensitive path(s) changed

Paths:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

  • CI workflow changes may ship without failure-mode evidence
  • Dependency or CI drift could surface after merge
  • 2 CI or workflow path(s) changed

Paths:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 27, 2026

Copy link
Copy Markdown

ECC Tools / Reference Set Readiness

Commit: 0268d9f3ce7345e6dffe397222f0f9ac96b0b1a9

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 2 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Missing Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence Missing Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 27, 2026

Copy link
Copy Markdown

ECC Tools / Hosted Promotion Readiness

Commit: 0268d9f3ce7345e6dffe397222f0f9ac96b0b1a9

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 2 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 27, 2026

Copy link
Copy Markdown

ECC Tools / PR Config Audit

Commit: 0268d9f3ce7345e6dffe397222f0f9ac96b0b1a9

No changed-config issues detected (success)

Scanned 2 config file(s) present at this commit across 2 changed config path(s) and found no issues in the supported security rules.

Changed config files:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Oct 27, 2026

Copy link
Copy Markdown

ECC Tools / PR Harness Audit

Commit: 0268d9f3ce7345e6dffe397222f0f9ac96b0b1a9

No harness issues detected (success)

Scanned 2 changed config file(s) and found no harness issues.

Changed config files:

  • .github/workflows/ci.yml
  • .github/workflows/npm-publish.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@asif7774
asif7774 merged commit f00ca89 into main Oct 27, 2026
2 checks passed
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