feat(config)!: remove function memoryMib (fixed by platform)#173
Merged
Conversation
3 tasks
Function memory is no longer user-configurable. Remove `FunctionMemoryMib` and drop `memoryMib` from `FunctionTuning`, `ResolvedFunctionConfig`, and `DeployFunctionInput`; the real NeonApi adapter no longer sends a `memory_mib` form field, and config-runtime stops threading it through plan/apply steps. A `neon.ts` setting `branch.preview.functions[slug].memoryMib` is now a type error and rejected by the schema. config 0.3.0 -> 0.4.0, config-runtime 0.4.0, env 0.3.0 (changeset included).
andrelandgraf
force-pushed
the
feat/remove-function-memory-v2
branch
from
777091a to
b1a7a9e
Compare
The `loads a neon.ts branch policy` test loads a temp `neon.ts` via jiti; under CI's `--coverage` instrumentation that cold TypeScript transpile can exceed the default 5s vitest timeout (it ran ~250ms locally but flaked at 5.6s in CI). Give it an explicit 30s timeout.
bayandin
approved these changes
Jun 9, 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
2 participants
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.
Summary
Function memory is no longer user-configurable; it is fixed by the platform policy. This removes the setting from every layer.
@neondatabase/config: dropFunctionMemoryMib; removememoryMibfromFunctionTuning,ResolvedFunctionConfig, andDeployFunctionInput. The real NeonApi adapter no longer sends amemory_mibform field.@neondatabase/config-runtime: stop threadingmemoryMibthrough plan/apply steps.neon.tssettingbranch.preview.functions[slug].memoryMibis now a type error and is rejected by the schema.Versions: config
0.3.0 -> 0.4.0, config-runtime0.4.0, env0.3.0(changeset included).Test plan
pnpm --filter @neondatabase/config --filter @neondatabase/config-runtime --filter @neondatabase/env tscpnpm lint:ci