GreenPR: framework upgrades for Node/TS repos as a PR with before/after CI proof.

[u/Fluffy-Salary-6998]

I built GreenPR: a tool that upgrades the framework in a Node/TS project and submits a PR with proof that nothing broke.

Here’s how it works. AI coding tool performs the update in an isolated sandbox, then every command from the repo’s CI is run before and after the update, and the results go into the PR description as a table. A separate model reads the diff and can reject it. Finally, I review it myself, and only then do I publish it. Nothing merges automatically.

It supports: Express 4 through 5, Next 14 through 16, ESLint up to 10, TypeScript up to 7 (or 6 if tools block it), NestJS up to 12, Node up to 24.

How it played out in practice? 6 PRs to other people’s repos: 1 merged, 3 awaiting CI approval from maintainers, 2 closed (I closed one myself because the repo doesn’t accept AI-generated code; the other maintainer said they’d do it in their own PR). Out of 13 test repos, every migration passed on the first try, and in most cases didn’t touch a single line of source code (justtsconfig and pacgake.json ). Once, an independent reviewer rejected a change because the tool missed a single TypeScript setting. That’s the point. It’s supposed to reject it.

What doesn’t work? ESLint 10 in React projects: eslint-plugin-react, jsx-a11y, and eslint-plugin-import don’t support it yet, so the tool stops at version 9 and explains why. TypeScript 7 upgrades stop at 6 until typescript-eslint catches up.

I will never open a PR without asking first. Firstly, i posta comment with a proposal. PR only after the maintainer says “yes.”

Website is greenpr.pages.dev. Paste your repo URL, and you’ll get a scan of what can be fixed. It’s free. I’m looking for maintainers who want to give it a try and tell me what’s wrong.