Conversation
…tes-plugin and await-register-calls
|
Thank you so much. I’m excited to contribute more.
…On Sun, 1 Feb 2026 at 16:41, Matteo Collina ***@***.***> wrote:
***@***.**** approved this pull request.
lgtm
—
Reply to this email directly, view it on GitHub
<#6479 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BE3TNQF2HHLNOGULK5WW7E34JYNCRAVCNFSM6AAAAACTSM5LRCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTOMZVHE3TKNBZGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
These links are invalid. |
This comment was marked as abuse.
This comment was marked as abuse.
|
Thank you for your feedback. I’ve updated the codemod links in the V4
migration guide to point to valid GitHub directories/registry links. The
changes have been pushed to the existing PR.
Please let me know if there’s anything else I should adjust.
Best regards,
Oluchi
On Tue, 3 Feb 2026 at 19:13, Zion development ***@***.***>
wrote:
… *ziongamingdev-tech* left a comment (fastify/fastify#6479)
<#6479 (comment)>
Thank you
On Tue, Feb 3, 2026, 10:29 AM Jean ***@***.***> wrote:
> *jean-michelet* left a comment (fastify/fastify#6479)
> <#6479 (comment)>
>
> These links are invalid.
>
> —
> Reply to this email directly, view it on GitHub
> <#6479 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/BZSQWSJLG5NAJMEO7T53VFL4KDLIZAVCNFSM6AAAAACTSM5LRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNBSGU2TMNJZGY>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#6479 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BE3TNQBDSUYX5EP2V7W24YT4KDQNVAVCNFSM6AAAAACTSM5LRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNBSG4YTIMZQGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Good day Sir/Ma,
I updated the PR per previous feedback. Could you please review again when
you have a moment?
Warm regards,
Oluchi.
…On Tue, 3 Feb 2026 at 18:29, Jean ***@***.***> wrote:
*jean-michelet* left a comment (fastify/fastify#6479)
<#6479 (comment)>
These links are invalid.
—
Reply to this email directly, view it on GitHub
<#6479 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BE3TNQAAKTDFEO7P4UU6KLL4KDLIXAVCNFSM6AAAAACTSM5LRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNBSGU2TMNJZGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Pull request overview
Updates the Fastify v4 migration guide’s codemod section to address broken codemod links by switching to the codemod@latest CLI invocation and pointing readers at the Codemod registry.
Changes:
- Replace old
go.codemod.comlinks with anapp.codemod.comregistry reference for the v4 migration recipe. - Update the migration command snippet to a fenced
bashblock. - Reformat the list of codemods applied by the migration recipe (currently as plain lines).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
|
|
||
| ``` | ||
| ```bash | ||
| npx codemod@latest fastify/4/migration-recipe | ||
| ``` |
There was a problem hiding this comment.
The fenced code block appears without an introductory sentence, after removing the prior “Run the following migration recipe…” text. Consider adding back a short lead-in explaining what the command does (and optionally linking the recipe name to the new registry URL) so this section reads coherently.
Signed-off-by: Frazer Smith <[email protected]>
Signed-off-by: Frazer Smith <[email protected]>
Fix broken Fastify v4 codemod links on remove-app-use, reply-raw-access, wrap-routes-plugin and await-register-calls
Checklist
npm run test && npm run benchmark --if-presentand the Code of conduct