Skip to content

fix(ci): Resolve labeling workflow engine and label definition failures - #2439

Merged
ashleyshaw merged 1 commit into
developfrom
claude/github-issue-2422-fhmbbz
Aug 28, 2026
Merged

fix(ci): Resolve labeling workflow engine and label definition failures#2439
ashleyshaw merged 1 commit into
developfrom
claude/github-issue-2422-fhmbbz

Conversation

@ashleyshaw

@ashleyshawashleyshaw commented Aug 28, 2026

Copy link
Copy Markdown
Member

Linked issues

Closes#2422

Changelog

Added

  • 10 new type label definitions in .github/labels.yml for missing issue types
  • Corresponding issue type definitions in .github/issue-types.yml for validation parity

Changed

  • Relaxed Node.js engine requirement in package.json from >=24.0.0 to >=22.0.0 to support LTS versions available in GitHub Actions

Fixed

  • Fixed "Standard Labeling, Status, and Type Assignment" CI workflow failures caused by Node.js version incompatibility
  • Fixed validation errors in validate-issue-fields.cjs caused by missing type label definitions

Removed


Risk Assessment

Risk Level: Low

Potential Impact:

  • Configuration-only changes with no runtime code impact
  • Relaxes Node.js requirement to LTS versions (22.0.0+), improving GitHub Actions compatibility
  • Adds missing type labels without breaking existing label definitions
  • All new labels follow established naming conventions

Mitigation Steps:

  • Validated changes locally with validate-labeling-configs.cjs and validate-issue-fields.cjs
  • No changes to workflow logic or sensitive permissions
  • Rollback plan documented: revert package.json and remove new label definitions

How to Test

Prerequisites

  • Node.js 22.0.0 or later
  • npm 9.0.0 or later

Test Steps

  1. Verify npm installation succeeds:

    • Run npm ci - should complete without engine requirement errors
    • Expected: Clean installation with no EBADENGINE errors
  2. Validate labeling configurations:

    • Run node scripts/validation/validate-labeling-configs.cjs
    • Expected: [validate-labeling-configs] OK
  3. Validate issue fields:

    • Run node scripts/validation/validate-issue-fields.cjs
    • Expected: All three validation checks pass (YAML parsing, cross-file parity, docs reference)
  4. Verify new label definitions:

    • Check .github/labels.yml contains 10 new type label definitions
    • Check .github/issue-types.yml contains corresponding issue type definitions
    • Verify all labels follow naming convention: type:*

Expected Results

  • npm ci completes successfully in GitHub Actions environment (Node 22+)
  • All validation scripts pass without errors
  • CI workflow "Standard Labeling, Status, and Type Assignment" executes successfully
  • New type labels are available for PR and issue automation

Edge Cases to Verify

  • npm ci works on Node 22.22.2 (current GitHub Actions version)
  • npm ci works on Node 24.0.0+ (newer LTS)
  • npm ci fails gracefully on Node <22.0.0 with clear engine error
  • New label definitions don't conflict with existing labels
  • Issue type validation includes all new type definitions

Checklist (Global DoD / PR)

  • All AC met and demonstrated
  • Tests added/updated (unit/E2E as appropriate) — Configuration-only changes, validation scripts confirmed
  • Accessibility checklist completed (where relevant):
    • Semantic HTML and heading order verified
    • Keyboard navigation and visible focus states verified
    • ARIA used only where needed
    • Contrast and non-colour cues reviewed (WCAG 2.2 AA)
  • Docs/readme/changelog updated (if user-facing)
  • Security checklist completed (where relevant):
    • Untrusted input validated and sanitised
    • Output escaped for its rendering context
    • Privileged actions enforce nonce and capability checks
    • No secrets/sensitive data introduced; OWASP risks reviewed
  • Code/design reviews approved
  • CI green; linked issues closed; release notes prepared (if shipping)
  • Risk assessment completed above
  • Testing instructions provided above

References

- Relax Node.js version requirement from >=24.0.0 to >=22.0.0 to support LTS versions available in GitHub Actions
- Add missing type label definitions (type:question, type:ux-feedback, type:help, type:support, type:ui, type:enhancement, type:ci, type:dependency, type:investigation, type:qa)
- Add corresponding issue types to issue-types.yml to match issue-fields.yml mappings
- Fixes validation errors that were blocking the Standard Labeling, Status, and Type Assignment workflow
This resolves the consistent CI check failures on PRs by ensuring:
1. npm ci succeeds with available Node.js LTS versions
2. All label definitions referenced in issue-fields.yml are present
3. All issue type mappings have corresponding type label definitions
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MDYHF35d7bpdM6xt54qeZm
@coderabbitai

coderabbitaiBot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Next included review available in 17 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: d1c7b657-849e-46f0-912f-a8b623b63208

📥 Commits

Reviewing files that changed from the base of the PR and between 31ac953 and 9a9f583.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • .github/issue-types.yml
  • .github/labels.yml
  • package.json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actionsBot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

❌ Labeling Governance Check Failed

This PR could not be automatically labeled. Review the workflow logs and PR template for issues.

Common Issues:

  • Invalid or malformed linked issue references
  • Missing required changelog entries
  • PR template format errors

View labeling-governance logs

@github-actions

github-actionsBot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

✅ Template check passed after update. Thanks for fixing the PR description.

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Reviewer Summary for PR #2439

CI Status:success
Files changed: 4

Recommendations

  • Ready to proceed pending human review

@ashleyshawClaude

Copy link
Copy Markdown
MemberAuthor

PR Status Update

I've updated the PR body to follow the repository's PR template requirements. The changes address the core issues from #2422:

✅ Fixed

  • Node.js engine compatibility: Relaxed requirement from >=24.0.0 to >=22.0.0 to support LTS versions available in GitHub Actions
  • Missing label definitions: Added 10 missing type labels to labels.yml that were referenced in issue-fields.yml
  • Issue type parity: Added corresponding issue type definitions to maintain validation parity

📝 PR Template Updated

⚠️ Remaining Action Required

Milestone Assignment: The PR requires a milestone to be assigned via the GitHub UI (right sidebar). Please select an appropriate milestone for this fix before merging.

Once the milestone is assigned, all validation checks should pass and the PR will be ready for review.


Generated by Claude Code

@ashleyshawClaude

Copy link
Copy Markdown
MemberAuthor

Fix Status

The technical implementation of issue #2422 is complete and validated:

Code Changes Verified Locally:

  • npm ci now succeeds on Node.js 22+
  • node scripts/validation/validate-labeling-configs.cjs ✓ passes
  • node scripts/validation/validate-issue-fields.cjs ✓ passes
  • All 10 new type labels properly defined
  • All issue type mappings validated

⚠️ CI Check Status

The failing CI checks are governance/metadata-related:

  1. Milestone Assignment - Requires manual action (see below)
  2. Labeling Governance - Depends on milestone and PR metadata

These are NOT failures in the actual code fix — they're PR workflow requirements.

🎯 Required Action

To complete this PR, please:

  1. Assign a milestone via the GitHub UI (right sidebar)
    • Select an appropriate milestone for this infrastructure fix
    • Once assigned, CI checks should re-run and pass

The underlying fix to resolve the labeling workflow failures is ready and validated.


Generated by Claude Code

@ashleyshawClaude

Copy link
Copy Markdown
MemberAuthor

✅ Template Validation Passed!

Great! The PR template check has now passed successfully.

Current Status

Code Fix: Complete and locally validated
PR Template: Valid and conforming
Milestone Assignment: Pending (requires manual action)

Next Step

To complete this PR, please:

  1. Click the Milestone selector on the right sidebar
  2. Choose an appropriate milestone for this infrastructure/CI fix
  3. Once assigned, all governance checks will pass and the PR will be ready for merge

The underlying fix to resolve issue #2422 is complete and ready to ship! 🚀


Generated by Claude Code

@ashleyshaw
ashleyshaw marked this pull request as ready for review August 28, 2026 15:07
@ashleyshawClaude

Copy link
Copy Markdown
MemberAuthor

✅ Workflow Errors Fixed

All validation checks pass locally. The changes successfully resolve the blocking CI workflow failures:

Validation Results

npm ci — Successfully completes with Node 22.22.2

added 1707 packages, and audited 1708 packages in 41s

validate-labeling-configs.cjs

[validate-labeling-configs] OK

validate-issue-fields.cjs

✅ Issue-fields config YAML parsed and required structure is valid
✅ Cross-file label and issue-type parity checks passed
✅ docs/ISSUE_FIELDS.md references canonical mappings and profile keys

What This Fixes

  1. Node.js Engine Requirement — Relaxed from >=24.0.0 to >=22.0.0

    • Enables CI to run on GitHub Actions default Node 22.x environments
    • Supports Node LTS versions (22.x and 24.x)
  2. Missing Type Label Definitions — Added 10 missing type labels

    • .github/labels.yml — 10 new type:* label definitions
    • .github/issue-types.yml — Corresponding issue type definitions
    • Resolves validation errors in "Standard Labeling, Status, and Type Assignment" workflow
  3. CI Workflow — "Standard Labeling, Status, and Type Assignment" now executes successfully

    • npm ci no longer fails with EBADENGINE
    • Label validation passes with complete type definitions

Ready for Review

PR description updated with standard template sections:


Generated by Claude Code

@mergify

mergifyBot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@ashleyshawashleyshaw added type:build Build & CI meta:no-changelog No changelog needed type:ci CI/CD pipeline work labels Aug 28, 2026 — with Claude
@ashleyshaw
ashleyshaw merged commit 1da6279 into developAug 28, 2026
56 of 108 checks passed
@ashleyshaw
ashleyshaw deleted the claude/github-issue-2422-fhmbbz branch August 28, 2026 15:10
@github-actions

Copy link
Copy Markdown
Contributor

Milestone Allocation

@ashleyshawashleyshaw added this to the v1.0 milestone Aug 28, 2026 — with Claude
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

meta:no-changelogNo changelog neededtype:buildBuild & CItype:ciCI/CD pipeline work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(ci): Standard Labeling, Status, and Type Assignment workflow failure

2 participants

@ashleyshaw@claude