chore(deps): upgrade Nx 21.5.3 to 22.6.5#473
Merged
karelhala merged 1 commit intoRedHatInsights:mainfrom Apr 28, 2026
Merged
Conversation
RHCLOUD-47079 Upgrade all @nx/* packages from 21.5.3 to 22.6.5 to remediate picomatch vulnerabilities (GHSA-3v7f-55p6-f55p, GHSA-c2c7-rcm5-vvqj). Changes: - All 11 @nx/* packages: 21.5.3 → 22.6.5 - nx: 21.5.3 → 22.6.5 - jest.config.ts: getJestProjects → getJestProjectsAsync (breaking) - nx.json: releaseTagPattern → releaseTag.pattern (migration) - .gitignore: added .claude/ entries (Nx migration) - @swc/*: updated to match Nx 22 peer expectations - cypress: 14.5.4 → 15.9.0 - @emotion/*: minor bumps Validated: build (17 projects), unit tests, integration tests.
platex-rehor-bot
force-pushed
the
bot/RHCLOUD-47079
branch
from
3aaedba to
c2c35f9
Compare
karelhala
approved these changes
Apr 28, 2026
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
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.
Summary
Upgrades all
@nx/*packages from 21.5.3 to 22.6.5 to eliminate vulnerablepicomatch@4.0.2instances (GHSA-3v7f-55p6-f55p, GHSA-c2c7-rcm5-vvqj).RHCLOUD-47079
Changes
@nx/*packages: 21.5.3 → 22.6.5,nx: 21.5.3 → 22.6.5jest.config.ts:getJestProjects→getJestProjectsAsync(removed in Nx 22)nx.json:releaseTagPattern→releaseTag.pattern(Nx 22 migration).gitignore: added.claude/worktreesand.claude/settings.local.json(Nx 22 migration)@swc/*packages updated to match Nx 22 peer expectationscypress: 14.5.4 → 15.9.0@emotion/*: minor version bumpsAGENTS.md: updated Nx version referencePicomatch verification
npm ls picomatchconfirms no instances in the vulnerable range (4.0.0–4.0.3):picomatch@4.0.2instances →picomatch@4.0.4✅picomatch@2.3.2(via micromatch) — not in vulnerable range ✅Validation
npm run build:no-cachenpm run test:unitnpm run test:integrationKnown issue:
npx nx release --dry-runThe dry-run release exits with code 1 due to a pre-existing issue — not introduced by this PR:
This occurs because existing breaking conventional commits in git history would trigger a major bump for
shared(2.0.5 → 3.0.0), but all client packages have^2.0.5which doesn't accept 3.x. On Nx 21, this was a silent warning (exit 0). Nx 22 madepreserveMatchingDependencyRangesstricter (exit 1). The fix is to either update the dependency ranges before the next release, or to perform the pending release first.Test plan
npm run build:no-cache— all 17 projects build successfullynpm run test:unit— all unit tests passnpm run test:integration— all integration tests passnpm ls picomatch— no instances in 4.0.0–4.0.3 range🤖 Generated with Claude Code