Repository navigation
fix(functions): print server warnings from function deploys - #690
Merged
Paveltarno merged 2 commits intoNov 3, 2026
Merged
Conversation
Since apper #35392 the server no longer creates new automations declared in
function.jsonc and reports that in the deploy response's `warnings`. The CLI
parsed the response as `{ status }`, so the warning (and the private data
source warnings) were dropped and deploy just printed "deployed".
Keep `warnings` in DeploySingleFunctionResponseSchema, carry it on the deploy
result, and print it from formatDeployResult, which now also handles actor
warnings for both `deploy` and `actors deploy`.
Paveltarno
enabled auto-merge (squash)
November 3, 2026 11:43
Paveltarno
disabled auto-merge
November 3, 2026 11:58
Paveltarno
enabled auto-merge (squash)
November 3, 2026 11:58
Paveltarno
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Since apper #35392 (Oct 28) the server no longer creates new
automationsdeclared infunction.jsonc. It deploys the code and says so in the deploy response'swarnings:{ "status": "deployed", "warnings": ["myFn: automations not created (nightly) and none removed. ..."] }The CLI parsed that response as
z.object({ status }), so Zod strippedwarningsandbase44 deploy/base44 functions deployjust printed "deployed". The server's private-data-source deploy warnings were dropped the same way. The CLI hit this on a real app. Slack threadFix
DeploySingleFunctionResponseSchemakeepswarnings(default[]), matchingDeployActorResponseSchema. The server sends it on both thedeployedandunchangedpaths.SingleFunctionDeployResultcarries the warnings.formatDeployResultprints each warning withlog.warnunder the result line. That function is already shared by function and actor results, so the two hand-written actor warning loops (deploy,actors deploy) are gone and both resource types use one path."<function>: ", so the name is added only when a warning doesn't start with it. Otherwise it would printmyFn: myFn: .... Actor output doesn't change.Under
--jsonthe warnings go to stderr through the logger, like actor warnings do today.Tests
functions deploy: warnings are printed fordeployedandunchanged, an already-prefixed warning isn't prefixed again, and an unprefixed one gets the function name.deploy: function warnings are printed during the unified deploy.bun run typecheckandbun run lintpass. The full suite passes exceptdev.spec.ts › Deno fallback runtime, which needsdenoon PATH and fails locally without this change too.🤖 Generated with Claude Code