[PR #681] [CLOSED] feat: nextjs-tracker — daily workflow to track Next.js canary changes #765

New issue

Closed

opened 2026-05-06 13:10:00 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 13:10:00 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/cloudflare/vinext/pull/681
Author: @southpolesteve
Created: 3/24/2026
Status: ❌ Closed

Base: main ← Head: feat/nextjs-tracker

📝 Commits (2)

6c428a7 refactor: extract Pages page data runtime
d5e6dde feat: add nextjs-tracker workflow and agent

📊 Changes

8 files changed (+1114 additions, -451 deletions)

View changed files

➕ .github/workflows/nextjs-tracker.yml (+136 -0)
➕ .opencode/agents/nextjs-tracker.md (+93 -0)
📝 packages/vinext/src/entries/pages-server-entry.ts (+107 -216)
➕ packages/vinext/src/server/pages-page-data.ts (+396 -0)
📝 packages/vinext/src/server/pages-page-response.ts (+1 -1)
📝 tests/__snapshots__/entry-templates.test.ts.snap (+104 -216)
📝 tests/entry-templates.test.ts (+19 -18)
➕ tests/pages-page-data.test.ts (+258 -0)

📄 Description

Adds a daily scheduled workflow that monitors Next.js canary commits and opens tracking issues for anything relevant to vinext.

Runs at 08:00 UTC via cron, or manually via workflow_dispatch
Fetches the last 24 hours of Next.js canary commits (configurable via since_hours input)
Passes commit metadata + file-level diffs to the nextjs-tracker Bonk agent
Agent classifies relevance, groups related commits, deduplicates against existing open issues, and creates labeled issues
Dry-run mode available: toggle dry_run: true on manual dispatch to get a stdout report of what would be opened without actually creating any issues

New files:

.github/workflows/nextjs-tracker.yml — the workflow
.opencode/agents/nextjs-tracker.md — agent config with relevance criteria, ignore list, dedup logic, and issue format

To validate before the first real run: trigger workflow_dispatch with dry_run: true and check the job logs.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/cloudflare/vinext/pull/681 **Author:** [@southpolesteve](https://github.com/southpolesteve) **Created:** 3/24/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feat/nextjs-tracker` --- ### 📝 Commits (2) - [`6c428a7`](https://github.com/cloudflare/vinext/commit/6c428a74f0f42a40982b0d448e949a50e58c89be) refactor: extract Pages page data runtime - [`d5e6dde`](https://github.com/cloudflare/vinext/commit/d5e6dde7656e3811a86720a80786e19525d2166b) feat: add nextjs-tracker workflow and agent ### 📊 Changes **8 files changed** (+1114 additions, -451 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/nextjs-tracker.yml` (+136 -0) ➕ `.opencode/agents/nextjs-tracker.md` (+93 -0) 📝 `packages/vinext/src/entries/pages-server-entry.ts` (+107 -216) ➕ `packages/vinext/src/server/pages-page-data.ts` (+396 -0) 📝 `packages/vinext/src/server/pages-page-response.ts` (+1 -1) 📝 `tests/__snapshots__/entry-templates.test.ts.snap` (+104 -216) 📝 `tests/entry-templates.test.ts` (+19 -18) ➕ `tests/pages-page-data.test.ts` (+258 -0) </details> ### 📄 Description Adds a daily scheduled workflow that monitors Next.js canary commits and opens tracking issues for anything relevant to vinext. - Runs at 08:00 UTC via cron, or manually via `workflow_dispatch` - Fetches the last 24 hours of Next.js canary commits (configurable via `since_hours` input) - Passes commit metadata + file-level diffs to the `nextjs-tracker` Bonk agent - Agent classifies relevance, groups related commits, deduplicates against existing open issues, and creates labeled issues - Dry-run mode available: toggle `dry_run: true` on manual dispatch to get a stdout report of what would be opened without actually creating any issues New files: - `.github/workflows/nextjs-tracker.yml` — the workflow - `.opencode/agents/nextjs-tracker.md` — agent config with relevance criteria, ignore list, dedup logic, and issue format To validate before the first real run: trigger `workflow_dispatch` with `dry_run: true` and check the job logs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>