ci: ignore yarn & bazel updates
#2784
Merged
Conversation
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
alan-agius4
added
the
action: review
angular-robot
bot
added
the
area: build & ci
alan-agius4
added
action: merge
angular-robot
bot
added
the
area: build & ci
alan-agius4
commented
May 12, 2025
alan-agius4
added
the
action: review
alan-agius4
force-pushed
the
yarn-ignore
branch
3 times, most recently
from
d764053 to
2d4503e
Compare
devversion
approved these changes
May 12, 2025
Contributor
Author
|
Do not merge this yet as I want to reformat. |
- `yarn` is copied locally - `bazel` major version should not be updated
Here's a breakdown of their preferences:
* **`matchDepNames` is generally preferred for clarity and accuracy.**
* `matchDepNames` was introduced specifically to match against the `depName` field, which typically represents the "short" or primary name of a dependency (e.g., `react`, `lodash`).
* Using `matchDepNames` makes your Renovate configuration more explicit and easier to understand, as its name directly reflects its intended behavior.
* **`matchPackageNames` has historical baggage and can be misleading.**
* Historically, `matchPackageNames` in Renovate also matched against the `depName` by default, despite its name suggesting it would match the `packageName` field. This was due to an earlier implementation decision.
* While `matchPackageNames` might still match `depName` in many current setups (for backward compatibility), it can be confusing and lead to unexpected behavior if you're expecting it to match the `packageName` (which is often a more complete or specific identifier, like `org.apache.maven:maven-core`).
alan-agius4
added
action: merge
devversion
approved these changes
May 12, 2025
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
yarnis copied locally