Skip to content

fix: ci - resolve pre-existing test failures #1621

Open

Description

@ashleyshaw

Issue

Several test suites are failing and blocking CI checks:

  • scripts/__tests__/inject-footers-safe.test.js — Frontmatter extraction tests failing
  • .github/scripts/__tests__/inject-footers-safe.test.js — Same test suite duplicate location
  • scripts/workflows/__tests__/release-workflow-scripts.test.js — Telemetry payload test failing (unexpected failure_reason field)

Impact

  • Pre-commit/pre-push hooks block commits and pushes
  • CI validation workflows fail on all PRs
  • Prevents normal development workflow

Root Cause

Test expectations don't match current implementation behavior. These are not blocking valid code changes but preventing legitimate merges.

Remediation

  1. Fix extractFrontmatterSafely implementation or test expectations
  2. Update telemetry test to account for failure_reason field in payload
  3. Consolidate duplicate test files
  4. Re-enable CI enforcement once fixed

Priority

Medium (blocks workflow, pre-existing issue)


Definition of Ready (DoR)

  • Reproduction steps clearly documented
  • Expected vs actual behavior defined
  • Environment/version information captured
  • Related issues/PRs linked
  • Severity/impact assessed
  • Acceptance criteria for fix defined

Definition of Done (DoD)

  • Bug fix verified and reproduction steps no longer apply
  • Root cause identified and documented
  • Tests added/updated to prevent regression; CI green
  • No new warnings or errors introduced
  • Docs/changelog updated
  • Backport considered (if applicable)
  • Release notes prepared

Activity

  1. linear-code commented on Aug 7, 2026

    @linear-code
  2. github-actions commented on Aug 7, 2026

    @github-actions
    Contributor

    ✅ Template check passed after update. Thanks for fixing the issue body.

  3. github-actions commented on Aug 7, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 5 day(s)
    • SLA state: Within SLA
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-12T22:42:00.555Z

    Maintained by project-meta-sync workflow.

  4. self-assigned this
    on Aug 7, 2026
  5. added theissue type on Aug 7, 2026
  6. added this to the v1.1 milestone on Aug 29, 2026
  7. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • migrate:area:ci
    • migrate:priority:normal
    • migrate:type:bug

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

  8. changed the title [-]Fix pre-existing test failures blocking CI[/-] [+]fix: ci - resolve pre-existing test failures[/+] on Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

Priority

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions