ci: the workflows run github-script, create-pull-request and repository-dispatch on Node.js 24, pinned by commit, and CodeRabbit skips the index pull request by jddunn · Pull Request #17 · framerslab/codex

jddunn · 2026-10-21T17:58:30Z

Two follow-ups to #12, #13 and #16.

Three JavaScript actions still targeted Node.js 20. The runner forces them onto Node.js 24 and warns on every run, for example run 39584989953 of the landing workflow: "Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/github-script@v7" (https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/), and run 39477712571 of the weekly bump and run 39654677206 of the weekly changelog, the same for peter-evans/create-pull-request@22a9089 (v7.0.11). The action.yml of each release in use says using: node20: actions/github-script v7 (13 steps in the two landing workflows, Trusted Weavers, async processing and the pull request enhancement), peter-evans/create-pull-request v7.0.11 (the bump, the index publish, and since #16 the changelog and the block tag enhancement) and peter-evans/repository-dispatch v3 (async processing). Every other action the workflows use already runs on Node.js 24 (actions/checkout@v5, setup-node@v5, cache@v5, upload-artifact@v7, download-artifact@v8, setup-python@v6, pnpm/action-setup@v6; each action.yml read at the ref in use).

Each index pull request spent one CodeRabbit review. The index publish opens its pull request with FRAMERS_BUMP_TOKEN, a person's token, and CodeRabbit counts a review against that person's allowance each time it evaluates a pull request ("Review rate limits", https://docs.coderabbit.ai/management/rate-limits). On 21 October that allowance was one review an hour in the morning (CodeRabbit's comments on #12 to #15) and two by the evening (#17 to #19), and an index pull request follows every push to master that changes weaves/, scripts/ or schema/. #14, the first, carried codex-index.json, codex-report.json and codex-search.json; on #19, the second, CodeRabbit selected the same three files and stopped at its review limit.

The change

Each action moves to the release whose action.yml says using: node24, pinned to that release's commit with the release named beside it, as the bump pins its actions. Each is the action's newest release. Each commit was read with gh api, from git/ref/tags/<release> and, for an annotated tag, from the tag object to its commit, and the action.yml was read at that commit:

Action	Was	Now	Commit
`actions/github-script`	`v7` (node20)	v9.0.0 (node24)	`3a2844b`, from the annotated tag `d746ffe`
`peter-evans/create-pull-request`	v7.0.11 (node20)	v8.1.1 (node24)	`5f6978f`
`peter-evans/repository-dispatch`	`v3` (node20)	v4.0.1 (node24)	`28959ce`

repository-dispatch v4.0.0's action.yml still says using: 'node20'; v4.0.1 ("Fix node version in actions.yml") is the first that runs on Node.js 24.

Breaking changes, from each release page, and how each is handled:

github-script v8.0.0 (https://github.com/actions/github-script/releases/tag/v8, the release named v8.0.0), create-pull-request v8.0.0 (https://github.com/peter-evans/create-pull-request/releases/tag/v8.0.0) and repository-dispatch v4.0.0 (https://github.com/peter-evans/repository-dispatch/releases/tag/v4.0.0): runner v2.327.1 or later. GitHub's hosted runners, which every workflow here uses, are later. create-pull-request v8.1.0 (https://github.com/peter-evans/create-pull-request/releases/tag/v8.1.0) and v8.1.1 (https://github.com/peter-evans/create-pull-request/releases/tag/v8.1.1) add retries on server errors and on 422 after creation and a warning in place of a failed remote prune, and change none of the inputs the four workflows use; between the two pins, src/create-or-update-branch.ts and src/git-command-manager.ts are unchanged, so the branch is still built from the commit checked out and add-paths still goes to one git add.
github-script v9.0.0 (https://github.com/actions/github-script/releases/tag/v9.0.0): require('@actions/github') fails, since that package is ESM only, and the script now gets getOctokit (and octokit) as parameters, so a script that declares either with const or let no longer compiles. No script here requires @actions/github or declares either name. Every octokit method the scripts call (issues.addLabels, createComment, createLabel, getLabel, listComments, removeLabel, updateComment, pulls.createReview, get, list, repos.createCommitStatus, actions.listWorkflowRuns and paginate) is in v9's bundled dist/index.js at the pinned commit with the same route, and require('fs') resolves through the same wrap-require.ts as v7.

CodeRabbit. A new .coderabbit.yaml sets two keys, both in CodeRabbit's configuration reference (https://docs.coderabbit.ai/reference/configuration) and its schema (https://coderabbit.ai/integrations/schema.v2.json); every other setting keeps CodeRabbit's default:

reviews.auto_review.ignore_title_keywords: ['ci(codex): update search index'] (https://docs.coderabbit.ai/reference/configuration, reviews.auto_review.ignore_title_keywords): "Skip reviews when the PR title contains any of these keywords (case-insensitive)". The index pull request's title, set by auto-index.yml, is ci(codex): update search index and block tags, and no other workflow's pull request title holds the keyword (the bump's, the changelog's and the block tag enhancement's). The rate limits page (https://docs.coderabbit.ai/management/rate-limits) lists "pull requests excluded by automatic review controls" among the actions that "never draw down the allowance", and names title filters among those controls.
reviews.path_filters (https://docs.coderabbit.ai/reference/configuration, reviews.path_filters): !codex-index.json, !codex-search.json, !codex-report.json, !codex-blocks.json, the files the index publish commits (its add-paths). A pattern that starts with ! excludes, so no review reads them in any pull request.

Not used: the schema has no key that matches a head branch (its only branch key is reviews.auto_review.base_branches, the target branch), and ignore_usernames would skip every pull request of the token's owner. UNVERIFIED and not relied on: whether a pull request whose every file path_filters excludes still draws a review; the title keyword skips the index pull request either way. CodeRabbit read the file from this branch on each of its runs here ("Configuration used: Repository: framerslab/codex/.coderabbit.yaml").

Docs: .github/WORKFLOWS.md describes CodeRabbit's handling of the index pull request in the index publish's section, and how a maintainer pins an action to a release that runs on Node.js 24.

Tests, first

tests/actions-on-node24.test.js (new, 5 cases) holds each release and its commit as read from GitHub, checks every uses: line of every workflow that names one of the three actions against it, compiles every actions/github-script body with v9's parameters (require, __original_require__, github, octokit, getOctokit, context, core, exec, glob, io, from src/main.ts at the pinned commit), and checks that no body requires @actions/github.
tests/coderabbit-config.test.js (new, 3 cases) reads .coderabbit.yaml beside the workflows: only the two keys; a title keyword that the index pull request's title holds and no other workflow's pull request title holds; and path filters that exclude exactly the index publish's add-paths.
On 3c9b662, which carried the tests alone, Test Suite run 39648548517 failed 6 of 314: the three pins (actions/github-script@v7, create-pull-request@22a9089 # v7.0.11, repository-dispatch@v3) and the three CodeRabbit cases (no .coderabbit.yaml). The compile and require checks passed on the old scripts, as they should. On 1ef2824, run 39648749940 passed all 314.
ci: the changelog and the enhanced block tags reach master through pull requests opened with FRAMERS_BUMP_TOKEN, and the activity script sends only queries GitHub accepts #16 landed first, with two more uses of create-pull-request at v7.0.11 (changelog.yml, ai-enhance-blocks.yml) and tests that require each to match the bump's pin. 15566d1 takes master alone: run 39662250360 failed 3 of 384, the create-pull-request pin case here (ai-enhance-blocks.yml:198) and ci: the changelog and the enhanced block tags reach master through pull requests opened with FRAMERS_BUMP_TOKEN, and the activity script sends only queries GitHub accepts #16's two pin cases (expected 'peter-evans/create-pull-request@22a90…' to be 'peter-evans/create-pull-request@5f697…'). a98dd1f moves both to the bump's pin, copied from bump-framers-deps.yml: run 39662633428 passed all 384, and rename-guard run 39662633418 passed.

After the merge

The merge changes auto-index.yml, so it starts the index workflow on master. The index files carry the time they were built (lastIndexed, generatedAt), so the build always differs from master's and create-pull-request v8.1.1 opens or updates the index pull request; its checks start the landing workflow on github-script v9.0.0, and CodeRabbit should skip it by its title. That run, its annotations and CodeRabbit's skip go in a comment here. ai-enhance-pr.yml and auto-merge-weavers.yml run only on pull requests into main, a branch this repository does not have; async-processing.yml runs its github-script steps only for such a pull request and its repository-dispatch step only on a push to main, so a manual run reaches neither. Those steps run on no event here, and the tests above are their only proof.

Reviews

Codex, the app: asked by comment on the head, a98dd1f: "Didn't find any major issues." It left no review comment on any head.
Codex CLI, codex exec review --base origin/master with the review model gpt-6.1-sol at medium effort (read from the run's session record), on a98dd1f: "No actionable regressions were identified in the action upgrades, CodeRabbit configuration, or accompanying tests."
Qodo, on 1ef2824: "Bugs (0)", "Rule violations (0)", "Requirement gaps (0)": no issues found. It left no review of 15566d1 or a98dd1f, so it is missing on the head.
CodeRabbit: rate limited on 1ef2824. On 15566d1 it reviewed all 11 files with this branch's .coderabbit.yaml ("Configuration used: Repository: framerslab/codex/.coderabbit.yaml"): "No actionable comments were generated in the recent review." Rate limited again on a98dd1f, which moves two uses: lines (changelog.yml, ai-enhance-blocks.yml) to the pin it reviewed in the other workflows, so it is missing on the head.
Sourcery: it wrote its reviewer's guide, and its review stopped at its weekly review budget ("you've used your own review budget of 250,000 diff characters for the last 7 days"): missing.
No review thread was opened on any head, and none is open.

Risks

A pinned commit does not move with its release's major tag; a later release reaches these workflows only by a change like this one.
A pull request titled like the index pull request by hand is skipped by CodeRabbit too; @coderabbitai review reviews it on request.

🤖 Generated with Claude Code

…tory-dispatch at the commit of the release that runs on Node.js 24, every github-script body compiles as v9 runs it, and CodeRabbit skips the index pull request by its title and reviews none of its files

coderabbitai · 2026-10-21T17:58:39Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: framerslab/codex/.coderabbit.yaml
Review profile: CHILL
Plan: Team
Run ID: 703a0c6c-1f02-40a0-bb21-bf43d2c65965

📥 Commits

Reviewing files that changed from the base of the PR and between 69ee9b6 and 15566d1.

📒 Files selected for processing: 11

.coderabbit.yaml
.github/WORKFLOWS.md
.github/workflows/ai-enhance-pr.yml
.github/workflows/async-processing.yml
.github/workflows/auto-index.yml
.github/workflows/auto-merge-weavers.yml
.github/workflows/bump-framers-deps.yml
.github/workflows/landing-follows-the-base.yml
.github/workflows/landing-follows-the-bump-checks.yml
tests/actions-on-node24.test.js
tests/coderabbit-config.test.js

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

📝 Walkthrough

The PR adds CodeRabbit rules for generated index pull requests, pins GitHub Actions to specified release commits across workflows, and adds tests and contributor guidance for these configurations.

Changes: Generated index review filtering

Layer / File(s)	Summary
Configure and verify index review filtering `.coderabbit.yaml`, `tests/coderabbit-config.test.js`, `.github/WORKFLOWS.md`	CodeRabbit skips automatic reviews for index pull requests and excludes the four published index files. Tests check the title rule and path filters. Contributor documentation describes the configuration.

GitHub Actions release pins

Layer / File(s)	Summary
Update workflow action pins `.github/workflows/ai-enhance-pr.yml`, `.github/workflows/async-processing.yml`, `.github/workflows/auto-index.yml`, `.github/workflows/auto-merge-weavers.yml`, `.github/workflows/bump-framers-deps.yml`, `.github/workflows/landing-follows-the-base.yml`, `.github/workflows/landing-follows-the-bump-checks.yml`	Workflows use pinned commits for `actions/github-script` v9.0.0, `peter-evans/repository-dispatch` v4.0.1, and `peter-evans/create-pull-request` v8.1.1.
Document and validate action releases `.github/WORKFLOWS.md`, `tests/actions-on-node24.test.js`	Contributor guidance describes release checks and pinning. Tests check action references, compile GitHub Script bodies, and reject direct `@actions/github` imports.

Priority: ⚪ Pending latest changes

Estimated code review effort: 2 (Simple) | ~15 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 15566

No identified issue blocks merging after normal checks.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description provides a detailed summary, rationale, changed actions, configuration, tests, risks, and validation results. However, it does not follow the repository template and omits required sec…	Rewrite the description using the repository template. Complete all applicable checklist items, list the changed files, provide explicit validation output, and mark non-applicable content-contribution sections with an explanation.

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title clearly summarizes the two primary changes: upgrading and pinning workflow actions for Node.js 24, and skipping generated index pull requests in CodeRabbit. It is longer than preferred but r…
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title clearly summarizes the two primary changes: upgrading and pinning workflow actions for Node.js 24, and skipping generated index pull requests in CodeRabbit. It is longer than preferred but remains specific and relevant.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. (9 skipped: 9 unsupported.)

Full details: Description check

Explanation

The description provides a detailed summary, rationale, changed actions, configuration, tests, risks, and validation results. However, it does not follow the repository template and omits required sections such as Type of Content, the pre-submission checklist, content categorization, schema compliance, license compliance, and the template’s file and validation sections.

Resolution

Rewrite the description using the repository template. Complete all applicable checklist items, list the changed files, provide explicit validation output, and mark non-applicable content-contribution sections with an explanation.

✨ Finishing Touches: 💡 1

🛠️ Fix failing CI checks: 💡

Commit to this branch
Create a new PR

📝 Generate docstrings

Commit to this branch
Create a new PR

🧪 Generate unit tests (beta)

Commit to this branch
Create a new PR

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

sourcery-ai · 2026-10-21T17:58:42Z

Reviewer's Guide

The PR modernizes the three remaining JavaScript actions to Node.js 24 using release commit pins, adds compatibility and coverage tests for all workflow usages, and configures CodeRabbit to skip automated index pull requests and their generated files.

File-Level Changes

Change	Details	Files
Upgrades all workflow JavaScript actions to Node.js 24 releases and pins them immutably by commit.	Updates github-script, create-pull-request, and repository-dispatch references to Node.js 24-capable releases with release comments. Adds repository-wide tests ensuring every relevant action use is pinned correctly. Validates github-script v9 compatibility by compiling all scripts with its injected parameters and rejecting obsolete @actions/github imports.	`tests/actions-on-node24.test.js` `.github/workflows/*.yml`
Excludes automated index pull requests from CodeRabbit reviews while filtering their generated files from other reviews.	Adds tests validating the minimal CodeRabbit configuration and its documented keys. Verifies the configured title keyword matches the index workflow's pull request but no other workflow-created pull request. Verifies every index publish path is excluded and no unrelated paths are filtered.	`tests/coderabbit-config.test.js` `.coderabbit.yaml` `.github/workflows/auto-index.yml`

Tips and commands

Interacting with Sourcery

Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others.
Change the review language.
Add, remove or edit custom review instructions.
Adjust other review settings.

Getting Help

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

…repository-dispatch to v4.0.1, the releases that run on Node.js 24, each pinned to its release's commit with the release named beside it; CodeRabbit skips the index pull request by its title and reviews none of the index files

…intainer pins an action to the commit of a release that runs on Node.js 24

chatgpt-codex-connector · 2026-10-21T18:05:01Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-21T19:43:32.364856Z	`a98dd1f`	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

sourcery-ai · 2026-10-21T18:05:04Z

Sorry @jddunn, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 days and 22 hours by commenting @sourcery-ai review. Upgrade to get a review now.

qodo-free-for-open-source-projects · 2026-10-21T18:05:29Z

PR Summary by Qodo

Pin CI actions to Node.js 24 releases and skip index PR reviews

⚙️ Configuration changes 🧪 Tests 📝 Documentation 🕐 20-40 Minutes

AI Description

• Pin three JavaScript actions to Node.js 24 releases to eliminate deprecation warnings.
• Skip automatic CodeRabbit reviews of index pull requests and exclude generated index files.
• Add regression tests and maintainer guidance for action pins and review settings.

Diagram

graph TD
  T["Regression tests"] --> W["GitHub workflows"] --> CP["Create pull request"] --> PR["Index pull request"] --> CR{{"CodeRabbit reviews"}}
  W --> GS["GitHub script"]
  W --> RD["Repository dispatch"]
  T --> CR

High-Level Assessment

The following are alternative approaches to this PR:

1. Filter generated paths only

➕ Avoids coupling the review skip to the index PR title.
➖ Whether an all-filtered pull request still consumes a CodeRabbit review is unverified.

Recommendation: Keep the title-based automatic-review skip alongside the path filters: the title control addresses the review allowance, while the filters prevent generated files from appearing in other reviews. The tests guard against changes to the workflow title or published file list, though a manually titled PR could also be skipped.

Files changed (11) +190 / -16

Tests (2) +154 / -0

actions-on-node24.test.jsGuard action pins and github-script compatibility +81/-0

Guard action pins and github-script compatibility
• Checks every use of the three actions against their release commits. Also compiles github-script bodies with v9 parameters and rejects incompatible @actions/github requires.
tests/actions-on-node24.test.js

coderabbit-config.test.jsGuard index PR review exclusions +73/-0

Guard index PR review exclusions

• Checks that CodeRabbit uses only the intended settings, that the title filter matches the index PR but no other workflow-created PR, and that excluded paths match the published files.

tests/coderabbit-config.test.js

Documentation (1) +2 / -0

WORKFLOWS.mdDocument review exclusions and action pinning +2/-0

Document review exclusions and action pinning
• Explains how CodeRabbit handles index pull requests and how maintainers verify and pin Node.js 24 action releases.
.github/WORKFLOWS.md

Other (8) +34 / -16

.coderabbit.yamlSkip index PR reviews and generated files +18/-0

Skip index PR reviews and generated files

• Adds a title keyword that excludes the index pull request from automatic review. Path filters exclude its four generated files from reviews of any pull request.

.coderabbit.yaml

ai-enhance-pr.ymlPin enhancement scripts to github-script v9 +3/-3

Pin enhancement scripts to github-script v9
• Moves all three github-script steps to the commit for v9.0.0.
.github/workflows/ai-enhance-pr.yml

async-processing.ymlPin async actions to Node.js 24 releases +4/-4

Pin async actions to Node.js 24 releases
• Moves three github-script steps to v9.0.0 and repository-dispatch to v4.0.1, each pinned by commit.
.github/workflows/async-processing.yml

auto-index.ymlUpgrade the index PR creation action +1/-1

Upgrade the index PR creation action
• Pins create-pull-request to the v8.1.1 commit without changing its index publication inputs.
.github/workflows/auto-index.yml

auto-merge-weavers.ymlPin weaver automation scripts to github-script v9 +5/-5

Pin weaver automation scripts to github-script v9
• Moves five github-script steps to the commit for v9.0.0.
.github/workflows/auto-merge-weavers.yml

bump-framers-deps.ymlUpgrade the dependency-bump PR action +1/-1

Upgrade the dependency-bump PR action
• Pins create-pull-request to the v8.1.1 commit for weekly dependency bump pull requests.
.github/workflows/bump-framers-deps.yml

landing-follows-the-base.ymlPin base-following script to github-script v9 +1/-1

Pin base-following script to github-script v9
• Moves its github-script step to the commit for v9.0.0.
.github/workflows/landing-follows-the-base.yml

landing-follows-the-bump-checks.ymlPin landing-guard script to github-script v9 +1/-1

Pin landing-guard script to github-script v9
• Moves its github-script step to the commit for v9.0.0.
.github/workflows/landing-follows-the-bump-checks.yml

qodo-free-for-open-source-projects · 2026-10-21T18:09:17Z

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can start a comment with 'qodo' or '@qodo' to chat about any finding

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

…4-and-index-review-skip

…sts with create-pull-request v8.1.1, the release the bump and the index publish pin, which runs on Node.js 24

jddunn · 2026-10-21T19:41:37Z

@codex review

chatgpt-codex-connector · 2026-10-21T19:43:30Z

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: a98dd1f235

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

jddunn · 2026-10-21T22:45:03Z

After the merge (24686d5, 22:36:51 UTC, by the merge loop once the comment pass was done and the landing label was on):

master's Test Suite on 24686d5, run 39687760664: Vocabulary & NLP Tests, Unit Tests (384 of 384, 16 files), Integration Tests, Cache Tests and Update Badges passed. rename-guard, run 39687760610, passed.
The merge changes auto-index.yml, so it started Build and Publish Codex Index on master, run 39687760559, green. Its publish job ran create-pull-request v8.1.1 (5f6978f) and opened ci(codex): update search index and block tags #20 from ci/codex-index at 22:38:35 UTC, carrying codex-index.json, codex-report.json and codex-search.json. The job's one annotation is the ubuntu-latest notice. The publish that opened ci(codex): update search index and block tags #19, run 39654615846 on v7.0.11, also carried "Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: peter-evans/create-pull-request@22a9089".
CodeRabbit on ci(codex): update search index and block tags #20: its status reads "Review skipped: ignored keyword in the PR title", and its comment says "Review skipped", "Ignore keyword(s) in the title", names ci(codex): update search index, and "Configuration used: Repository: framerslab/codex/.coderabbit.yaml".
ci(codex): update search index and block tags #20's own Test Suite (run 39687962820) and rename-guard (run 39687962908) passed, and landing-follows-the-bump-checks.yml, now on github-script v9.0.0 (3a2844b), labelled it landing at 22:43:13 UTC and wrote its guards comment (run 39688496245). Each of its seven runs for the events of ci(codex): update search index and block tags #20's guards (22:38:40 to 22:43:06 UTC) passed, each with the ubuntu-latest notice as its one annotation and no Node.js 20 warning.
Not exercised, as the description says: the github-script steps of ai-enhance-pr.yml, auto-merge-weavers.yml and async-processing.yml, and async processing's repository-dispatch step, run only for main, a branch this repository does not have. tests/actions-on-node24.test.js is their proof.

#20 lands through the merge loop under the same review rule.

test: the workflows run github-script, create-pull-request and reposi…

3c9b662

…tory-dispatch at the commit of the release that runs on Node.js 24, every github-script body compiles as v9 runs it, and CodeRabbit skips the index pull request by its title and reviews none of its files

jddunn added 2 commits October 21, 2026 10:59

docs: CodeRabbit skips the index pull request and its files, and a ma…

1ef2824

…intainer pins an action to the commit of a release that runs on Node.js 24

jddunn marked this pull request as ready for review October 21, 2026 18:04

jddunn added 2 commits October 21, 2026 12:27

Merge remote-tracking branch 'origin/master' into ci/actions-on-node2…

15566d1

…4-and-index-review-skip

ci: the changelog and the block tag enhancement open their pull reque…

a98dd1f

…sts with create-pull-request v8.1.1, the release the bump and the index publish pin, which runs on Node.js 24

jddunn mentioned this pull request Oct 21, 2026

ci: the changelog and the enhanced block tags reach master through pull requests opened with FRAMERS_BUMP_TOKEN, and the activity script sends only queries GitHub accepts #16

Merged

jddunn added the landing Checks and guards passed; lands after the comment pass label Oct 21, 2026

jddunn merged commit 24686d5 into master Oct 21, 2026
14 checks passed

jddunn deleted the ci/actions-on-node24-and-index-review-skip branch October 21, 2026 22:36

Navigation Menu

Repository navigation

ci: the workflows run github-script, create-pull-request and repository-dispatch on Node.js 24, pinned by commit, and CodeRabbit skips the index pull request - #17

ci: the workflows run github-script, create-pull-request and repository-dispatch on Node.js 24, pinned by commit, and CodeRabbit skips the index pull request#17
jddunn merged 5 commits into
masterfrom
ci/actions-on-node24-and-index-review-skip

jddunn commented Oct 21, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Oct 21, 2026 •

edited

Loading

Uh oh!

sourcery-ai Bot commented Oct 21, 2026

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

chatgpt-codex-connector Bot commented Oct 21, 2026 •

edited

Loading

Uh oh!

sourcery-ai Bot commented Oct 21, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Oct 21, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Oct 21, 2026

Uh oh!

jddunn commented Oct 21, 2026

Uh oh!

chatgpt-codex-connector Bot commented Oct 21, 2026

Uh oh!

Uh oh!

jddunn commented Oct 21, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

jddunn commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

The change

Tests, first

After the merge

Reviews

Risks

Uh oh!

coderabbitai Bot commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sourcery-ai Bot commented Oct 21, 2026

Reviewer's Guide

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

chatgpt-codex-connector Bot commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

sourcery-ai Bot commented Oct 21, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Oct 21, 2026

PR Summary by Qodo

Uh oh!

qodo-free-for-open-source-projects Bot commented Oct 21, 2026

Code Review by Qodo

Great, no issues found!

Uh oh!

jddunn commented Oct 21, 2026

Uh oh!

chatgpt-codex-connector Bot commented Oct 21, 2026

Uh oh!

Uh oh!

jddunn commented Oct 21, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

jddunn commented Oct 21, 2026 •

edited

Loading

coderabbitai Bot commented Oct 21, 2026 •

edited

Loading

chatgpt-codex-connector Bot commented Oct 21, 2026 •

edited

Loading