fix: mark vercel.ts config as used#821
Merged
BartWaardenburg merged 2 commits intoJun 1, 2026
Merged
Conversation
Update the documented built-in plugin count after adding the Vercel plugin and list deployment-oriented plugins separately in the README table. Rename the Vercel regression fixture and integration test from issue 819 to issue 820 so the test history matches the bug this PR closes. Refs fallow-rs#820.
BartWaardenburg
approved these changes
Jun 1, 2026
Collaborator
BartWaardenburg
left a comment
There was a problem hiding this comment.
Reviewed the Vercel plugin fix and the follow-up cleanup. Local verification passed.
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.
What
Adds a built-in Vercel plugin that treats documented Vercel programmatic config files as used config entrypoints.
Why
Closes #820.
Vercel discovers and executes
vercel.tsby convention during builds, so it should not be reported as an unused file just because application source does not import it.Test plan
cargo fmt --all -- --checkcargo clippy --workspace -- -D warningscargo test --workspace