Skip to content

feat: link the upstream issue/PR for actions with no node24 release; flag archived repos - #3

Merged
Blackman99 merged 1 commit into
mainfrom
feat/upstream-issue
Oct 26, 2026
Merged

Blackman99 merged 1 commit into
mainfrom
feat/upstream-issue

Conversation

@Blackman99

Copy link
Copy Markdown
Owner

Roadmap item: track upstream "no node24 release yet" actions.

  • no-fix findings now search the action's repo once for an issue/PR whose title mentions node24 (open first, then most discussed) and link it in text, Markdown and JSON (upstream_issue).
  • Archived upstream repos are flagged: replace the action.
  • --no-upstream skips the lookups; results are disk-cached with the tags; rate-limited searches are skipped silently.
  • Docs, FAQ, changelog (Unreleased), roadmap and landing demo updated. 6 new tests.

@changeset-bot

changeset-bot Bot commented Oct 26, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 4a60b39

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@Blackman99 Blackman99 added the enhancement New feature or request label Oct 26, 2026

@Blackman99 Blackman99 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed against GOAL.md: on goal. For actions with no node24 release, actnode can now say where the upstream fix is being tracked, and it flags archived repos that will never get one.

  • Lookups are bounded to one search per repo per run and disk-cached. Failures and rate limits return None without caching the miss, so a flaky network never blocks a scan.
  • --no-upstream gives an offline/deterministic path.
  • _pick_issue matches node24, node 24, node.js 24 and nodejs-24 in titles, preferring open, then most-discussed.

Small note for later: the archived check costs one extra API call per no-fix action. That's fine at this volume, but worth caching to disk alongside the issue lookup if anyone hits rate limits. Will merge once CI is green.

@Blackman99
Blackman99 merged commit 0d7e7b2 into main Oct 26, 2026
10 checks passed
@Blackman99
Blackman99 deleted the feat/upstream-issue branch October 26, 2026 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant