Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 12, 2025

This PR contains the following updates:

Package Change Age Confidence
@blueprintjs/core (source) 6.3.2 -> 6.3.4 age confidence

Release Notes

palantir/blueprint (@​blueprintjs/core)

v6.3.4

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies This pull request updates dependency files label Nov 12, 2025
Comment on lines +1489 to +1492
resolution: "@blueprintjs/core@npm:6.3.4"
dependencies:
"@blueprintjs/colors": "npm:^5.1.9"
"@blueprintjs/icons": "npm:^6.2.0"
"@blueprintjs/colors": "npm:^5.1.11"
"@blueprintjs/icons": "npm:^6.3.1"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Multiple versions of @blueprintjs/icons are present in yarn.lock, potentially leading to bundle bloat or runtime conflicts.
Severity: HIGH | Confidence: 0.90

🔍 Detailed Analysis

The yarn.lock file now includes two different versions of @blueprintjs/icons: 6.2.0 and 6.3.1. This occurs because @blueprintjs/datetime and @blueprintjs/select depend on ^6.2.0, while @blueprintjs/core depends on ^6.3.1. If yarn does not properly deduplicate these dependencies, both versions could end up in the final bundle, leading to increased bundle size and potential runtime conflicts or unexpected behavior due to different versions of the same component being loaded.

💡 Suggested Fix

Ensure that all BlueprintJS packages depend on a compatible, single version of @blueprintjs/icons. Update or downgrade dependencies as necessary to resolve the version conflict.

🤖 Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: yarn.lock#L1489-L1492

Potential issue: The `yarn.lock` file now includes two different versions of
`@blueprintjs/icons`: `6.2.0` and `6.3.1`. This occurs because `@blueprintjs/datetime`
and `@blueprintjs/select` depend on `^6.2.0`, while `@blueprintjs/core` depends on
`^6.3.1`. If yarn does not properly deduplicate these dependencies, both versions could
end up in the final bundle, leading to increased bundle size and potential runtime
conflicts or unexpected behavior due to different versions of the same component being
loaded.

Did we get this right? 👍 / 👎 to inform future reviews.

@renovate renovate bot force-pushed the renovate/blueprintjs-core-6.x-lockfile branch from a800bd3 to 5f2956b Compare November 12, 2025 09:44
@coveralls
Copy link

coveralls commented Nov 12, 2025

Pull Request Test Coverage Report for Build 19293369591

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 39.81%

Totals Coverage Status
Change from base Build 19293343881: 0.0%
Covered Lines: 4845
Relevant Lines: 11257

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/blueprintjs-core-6.x-lockfile branch from 5f2956b to bdfffe4 Compare November 12, 2025 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies This pull request updates dependency files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants