bazel vendor ignores --target_pattern_file
#23628
Assignees
Labels
area-Bzlmod
Bzlmod-specific PRs, issues, and feature requests
P1
I'll work on this now. (Assignee required)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
type: feature request
Comments
github-actions
bot
added
the
team-ExternalDeps
meteorcloudy
added
type: feature request
P1
meteorcloudy
added
the
area-Bzlmod
|
@bazel-io fork 7.4.0 |
|
Thanks for reporting! I'm sending a fix and backport it to 7.4.0 |
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this issue
Sep 18, 2024
Fixes: bazelbuild#23628 RELNOTES: Bazel fetch and vendor command now supports --target_pattern_file for specifying target patterns. Closes bazelbuild#23640. PiperOrigin-RevId: 676063442 Change-Id: Ibbbf7879dfec4ec10093631fb002f87c9dddc8ef
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 19, 2024
…23663) Fixes: #23628 RELNOTES: Bazel fetch and vendor command now supports --target_pattern_file for specifying target patterns. Closes #23640. PiperOrigin-RevId: 676063442 Change-Id: Ibbbf7879dfec4ec10093631fb002f87c9dddc8ef Commit 3120d35 --------- Co-authored-by: Yun Peng <[email protected]> Co-authored-by: Xùdōng Yáng <[email protected]>
|
A fix for this issue has been included in Bazel 7.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug:
bazel vendorignores--target_pattern_fileand behaves as if no target pattern had been passedWhich category does this issue belong to?
External Dependency
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
No response
What is the output of
bazel info release?release 7.3.1
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: