ci: bump checkout/setup-node to v5 before the June 16 Node 20 deprecation - #54
Open
eunice-guo wants to merge 1 commit into
Open
ci: bump checkout/setup-node to v5 before the June 16 Node 20 deprecation#54eunice-guo wants to merge 1 commit into
eunice-guo wants to merge 1 commit into
Conversation
GitHub force-migrates v4 actions (Node 20 runtime) to Node 24 on 2026-06-16; pinning to v5 keeps the daily feed job from breaking. Also bumps the script's Node from EOL 20 to LTS 22. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The daily Generate Feeds job currently uses
actions/checkout@v4andactions/setup-node@v4, which run on the Node 20 action runtime. Every recent run logs:So this is a time-boxed breakage, not a hypothetical — the scheduled job risks failing right after 2026-06-16.
Change
actions/checkout@v4→@v5actions/setup-node@v4→@v5(these run on the Node 24 runtime)node-version: '20'→'22'for the feed script (20 is past active LTS)No workflow logic or feed-generation behavior changes.
Note for maintainer (not part of this PR)
While here I traced the "thin podcast / empty blog" feel some users notice — it's working as designed, not a bug:
fetchPodcastContentreturns exactly one episode per run (the newest unseen one that pod2txt can transcribe), so it drains a backlog 1/day.state.seenArticles;MAX_INDEX_SCANis also pinned toMAX_ARTICLES_PER_BLOG = 3, so if more than 3 posts land between runs the overflow never gets scanned. Happy to send a follow-up decoupling scan-depth from the output cap if that's of interest.🤖 Generated with Claude Code