chore(deps): update dependency jest-junit to v17#356
Conversation
📝 WalkthroughWalkthroughThe ChangesDependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 1/5 review remaining, refill in 44 minutes and 46 seconds. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 63: CI currently runs Node 18 but package.json uses "jest-junit":
"^17.0.0" which requires Node >=20; either update the CI Node version in
pullrequest.yml to 20+ (change the setup-node action or uses: node: '20') or pin
the dependency in package.json to a Node-18-compatible version by downgrading
"jest-junit" to a v15 or v16 range; update the chosen file (pullrequest.yml for
Node upgrade or package.json for dependency downgrade) and run install/test in
CI to verify the fix.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: c5c70ab7-60ab-484e-b64f-2dbb6d352d1a
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "eslint-plugin-react-hooks": "^4.6.0", | ||
| "jest": "^29.7.0", | ||
| "jest-junit": "^15.0.0", | ||
| "jest-junit": "^17.0.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "1) Find where jest-junit is referenced/configured:"
rg -n --hidden --glob '!**/node_modules/**' 'jest-junit' .
echo "2) Find Jest reporter wiring (reporters array / junit output settings):"
rg -n --hidden --glob '!**/node_modules/**' --glob '!**/dist/**' --glob '!**/build/**' 'reporters|outputDirectory|outputName' .
echo "3) Locate likely Jest config files:"
find . -maxdepth 6 -type f \( -iname 'jest.config.*' -o -iname '*jest*.config.*' -o -iname '*.jest.*' \) 2>/dev/null || true
echo "4) After installing deps, run tests and confirm JUnit XML is produced:"
# Example (adjust to your package manager / CI expectations):
# yarn test
# ls -la junit* */junit* 2>/dev/null || trueRepository: ZeroGachis/smartway-react-native-ui
Length of output: 2028
🏁 Script executed:
cat -n ./jest.config.tsRepository: ZeroGachis/smartway-react-native-ui
Length of output: 1071
🏁 Script executed:
cat -n ./.github/workflows/unit-tests.yml | head -60Repository: ZeroGachis/smartway-react-native-ui
Length of output: 1696
🏁 Script executed:
web_search
jest-junit v17.0.0 breaking changes changelogRepository: ZeroGachis/smartway-react-native-ui
Length of output: 179
🌐 Web query:
jest-junit version 17 release notes breaking changes
💡 Result:
jest-junit version 17.0.0 was tagged on 2026-04-24. The release page lists "Upgrade uuid package to latest - #284" but lacks detailed notes. The diff from v16.0.0 to v17.0.0 shows primarily maintenance updates: CI modernization, dependency upgrades (uuid to ^14.0.0, dev deps to Jest 30.2.0 and libxml2-wasm), switch from yarn to npm, removal of integration test dirs and Windows support, and snapshot/test updates. Breaking changes: - Node.js requirement raised from >=10.12.0 to >=20.0.0 (package.json engines field). - Removed integration-tests directories and related jest.config.js entries. - Switched XML validation library from libxmljs2 to libxml2-wasm in tests (may indirectly affect users if relying on specific behaviors). - Removed Windows-specific CI testing. No other explicit breaking API changes to reporter configuration or output format are documented. Existing configurations should work, but projects on Node <20 must upgrade Node.js.
Citations:
- 1: https://github.com/jest-community/jest-junit/releases
- 2: jest-community/jest-junit@v16.0.0...v17.0.0
- 3: https://github.com/jest-community/jest-junit/
🏁 Script executed:
find ./.github/workflows -type f -name '*.yml' -o -name '*.yaml' | xargs grep -l 'unit-tests'Repository: ZeroGachis/smartway-react-native-ui
Length of output: 115
🏁 Script executed:
cat -n ./.github/workflows/*.yml | grep -A 5 -B 5 'unit-tests' || trueRepository: ZeroGachis/smartway-react-native-ui
Length of output: 338
🏁 Script executed:
rg -n 'unit-tests.yml' ./.github/workflows/Repository: ZeroGachis/smartway-react-native-ui
Length of output: 166
Upgrade Node.js to >=20.0.0 in CI, or downgrade jest-junit to v15/v16.
The jest-junit v17.0.0 upgrade requires Node.js >=20.0.0, but the CI workflow (pullrequest.yml) currently runs Node 18. This will cause installation or runtime failures. Either upgrade the Node.js version in pullrequest.yml from 18 to 20+ or downgrade jest-junit back to v15/v16 compatible with Node 18.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 63, CI currently runs Node 18 but package.json uses
"jest-junit": "^17.0.0" which requires Node >=20; either update the CI Node
version in pullrequest.yml to 20+ (change the setup-node action or uses: node:
'20') or pin the dependency in package.json to a Node-18-compatible version by
downgrading "jest-junit" to a v15 or v16 range; update the chosen file
(pullrequest.yml for Node upgrade or package.json for dependency downgrade) and
run install/test in CI to verify the fix.
This PR contains the following updates:
^15.0.0->^17.0.0Release Notes
jest-community/jest-junit (jest-junit)
v17.0.0Compare Source
Upgrade uuid package to latest - #284
v16.0.0Compare Source
Allow adding properties to testcases in junit output by @eps1lon - #247
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 06:59 AM, only on Monday ( * 0-6 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.