Skip to content

PIT-77: improve vercel-target support - #189

Merged
tmthrgd-aligent merged 5 commits into
mainfrom
fix/PIT-77_silence_warning
Oct 9, 2026
Merged

tmthrgd-aligent merged 5 commits into
mainfrom
fix/PIT-77_silence_warning

Conversation

@tmthrgd-aligent

Copy link
Copy Markdown
Contributor

This silences a warning when both --prod and --target are specified, documents the new flag, and allows multiple targets to be deployed in parallel.

Note: The change to the PR comment will cause new comments to be left on existing PRs when deploying the previews, as the marker has changed.

When the new vercel-target input, both the --target and --prod flags are
set. This causes the following warning to be printed:
	WARNING! Both `--prod` and `--target` detected. Ignoring `--prod`.

It doesn't cause any issues but why leave a warning around?
I neglected to add the vercel-target input to the vercel-production.md
and vercel-preview.md docs.
This allows deploys to different targets to run concurrently with each
other.
Without this change, trying to deploy a preview to multiple targets will
clash with one overwriting the other.

It also wouldn't be clear what the target environment was in the comment.

Note: This change will cause new comments to be left on existing PRs
when deploying the previews as the marker has changed.
The vercel-preview.yml concurrency group is now very long. This trips
the yamllint. It is possible, though awkward, to wrap the line. Rather
than do that though, we suppress the check for this line as we have
done in several other workflows.
@tmthrgd-aligent
tmthrgd-aligent merged commit 2cc06c0 into main Oct 9, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants