[APPS-2792] Add: v3 to v4 migration guide entry - #511
gh-worker-dd-mergequeue-cf854d[bot] merged 4 commits into
Conversation
|
5395c22 to
c01b3b9
Compare
4687e4c to
b39e663
Compare
b39e663 to
281ac50
Compare
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
e3c9bda to
3e35c51
Compare
fdf2c87 to
67a04f8
Compare
67a04f8 to
b52f75b
Compare
b52f75b to
c8de74e
Compare
e115347 to
086f9f8
Compare
b0d6a58 to
71d450e
Compare
3797fba to
03d1671
Compare
03d1671 to
a973d82
Compare
Documents the upcoming breaking change to how `npm run dev` runs backend functions: in-process execution instead of a cloud round trip, the new `npm run dev:verify` cloud-parity check, and the process.env allowlist during local execution.
a973d82 to
2fbb0ea
Compare
|
/merge 🤖 Posted by Claude Code |
|
View all feedbacks in Devflow UI.
🤖 Posted by Claude Code`
The expected merge time in
|
d2b4981
into
master
Motivation
npm run dev:verify, the runtime network/subprocess guard, build-time rejection of Node built-ins/raw network globals, Custom Credentials local resolution, and real-identity hydration forgetInitiatingUser()/getExecutionUser()), withprocess.envscoping.majorversion bump —MIGRATIONS.mdneeds a## v3 to v4entry describing it before that bump goes out.bump.yamldispatch) should wait until all the implementation PRs land.Changes
7 changes across MIGRATIONS.md, README.md
## v3 to v4entry covering in-process local execution,npm run dev:verify, and theprocess.envallowlist, plus its Table of Contents entryMIGRATIONS.mddatadog-app.local.json) and real-identity hydration forgetInitiatingUser()/getExecutionUser(), plus their Table of Contents entriesMIGRATIONS.mdMIGRATIONS.mddev:verifyscript, anddev:verifycan't simulate a real trigger's identityMIGRATIONS.mddns.lookup()exception to the runtime guard, module-cached state now covering the backend file's own code (not just a dependency's), and a call-serialization caveatMIGRATIONS.mddev:verifynudge beforedraft/upload/publish— accepting runs the check and blocks on cancellation, declining just reminds and continuesMIGRATIONS.mdv3 to v4section from the Migrations listREADME.mdQA Instructions
Docs-only change — no functional QA applies.
Every described behavior was cross-checked against the actual merged code, grouped by area:
dev:verify/DEV_VERIFY_MODE— verified againstlocal-execution.ts,dev-server.ts,constants.ts.network-guard.ts,local-execution.ts,reject-node-builtin-imports.ts,backend-static-checks-plugin.ts.process.envallowlist, its module-top-level-load gap, Custom Credentials resolution, and real-identity hydration — verified againstenv-guard.ts,local-execution.ts,custom-credentials-resolver.ts.dev:verifybehavior — the CLI-flag equivalent for a missing package script, its preview-identity limitation, and the inline pre-publish nudge — verified againstconstants.ts,dev-server.ts, and the nudge's separate private-repo implementation directly.Blast Radius
MIGRATIONS.md). Zero runtime risk.Out of Scope / Follow-ups
2 items deferred
majorversion bump (bump.yamldispatch) this entry documentsnpm run dev:verifypackage.json script this entry tells users to run is defined in thecreate-appstemplate, not in this repodev:verifyscript +--verifyCLI flag) — merge before the version bump ships so the documented script exists for new projects