Add write-only value version to project environment variables - #571
Merged
Conversation
dglsparsons
marked this pull request as ready for review
August 5, 2026 19:45
dglsparsons
requested review from
craigandrews,
ecklf,
jarneson and
kitfoster
as code owners
August 5, 2026 19:45
ecklf
approved these changes
Aug 6, 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.
Adds value_wo_version to project environment variables as a persisted trigger for rotating ephemeral values. Bumping the version resends value_wo, while unrelated updates omit the secret from the Vercel PATCH request.
Existing value_wo configurations remain compatible, and the generated documentation and example show how to opt into versioned rotation.
Closes #570.