Summary
The Feature Submission.yml workflow fails on every issue opened in this repo. It has never succeeded in the visible run history (checked back through mid-2025), including the recent [AI Conference] topic submissions.
Example runs:
Cause
The workflow's createCard job uses peter-evans/create-or-update-project-card to add each new issue to:
project-name: CVE Program Automation Upgrade Feature Tracker
column-name: Submitted
and fails with ##[error] Not Found. That action targets classic GitHub Projects, which GitHub has sunset — the board it's pointing at no longer exists (or is no longer reachable via the classic API), so every run 404s.
Impact
None on the issues themselves — they're created normally. The only effect is a red ✗ on every submission and the loss of whatever triage flow the board used to provide. But if the team is still relying on that board to see incoming feature requests, submissions since the classic-projects sunset may not be landing anywhere they're watched.
Suggested fix
Either:
- Migrate to Projects v2 — replace the step with GitHub's own
actions/add-to-project, pointing at a v2 project URL (requires a token with project scope), or
- Remove the workflow if the tracker board is no longer part of the triage process — which would also stop the misleading failure notification on every new issue.
Happy to provide more detail from the run logs if useful.
Summary
The
Feature Submission.ymlworkflow fails on every issue opened in this repo. It has never succeeded in the visible run history (checked back through mid-2025), including the recent[AI Conference]topic submissions.Example runs:
Cause
The workflow's
createCardjob usespeter-evans/create-or-update-project-cardto add each new issue to:and fails with
##[error] Not Found. That action targets classic GitHub Projects, which GitHub has sunset — the board it's pointing at no longer exists (or is no longer reachable via the classic API), so every run 404s.Impact
None on the issues themselves — they're created normally. The only effect is a red ✗ on every submission and the loss of whatever triage flow the board used to provide. But if the team is still relying on that board to see incoming feature requests, submissions since the classic-projects sunset may not be landing anywhere they're watched.
Suggested fix
Either:
actions/add-to-project, pointing at a v2 project URL (requires a token withprojectscope), orHappy to provide more detail from the run logs if useful.