chore(release): 29.4.1 #4973
chore(release): 29.4.1 #4973
Conversation
WalkthroughThis change updates the project to patch release 29.4.1, as documented in the changelog and reflected in the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🔭 Outside diff range comments (1)
package.json (1)
54-63: Address remaining “ejs” references in lockfilesOur search confirmed that
ejsis no longer listed in anypackage.jsonor imported in source files, but it still appears in the generated lockfiles for several sub-projects. To fully remove the package:• Regenerate the lockfile in each affected directory (e.g.
website/,e2e/,examples/) by running your package manager’s install command there (e.g.npm install,yarn install, orpnpm install).
• Commit the updatedpackage-lock.json(or equivalent) so that no residualejsentries remain.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
CHANGELOG.md(1 hunks)package.json(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: in the ts-jest project, dependencies are only installed at the root level using the root package-loc...
Learnt from: ahnpnl
PR: kulshekhar/ts-jest#4950
File: .github/actions/setup-workspace/action.yml:28-28
Timestamp: 2025-07-21T14:09:03.234Z
Learning: In the ts-jest project, dependencies are only installed at the root level using the root package-lock.json file. Subdirectory package-lock.json files in e2e/ and examples/ directories don't affect the main workspace dependency installation, so they should not be included in GitHub Actions cache keys for the main workspace.
Applied to files:
package.json
🔇 Additional comments (1)
CHANGELOG.md (1)
1-7: Changelog entry is clear and properly linkedThe new 29.4.1 section clearly states the security-motivated dependency swap and references the correct commit and issue. No action required.
| { | ||
| "name": "ts-jest", | ||
| "version": "29.4.0", | ||
| "version": "29.4.1", |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Double-check downstream artefacts after the version bump
Updating the version field is necessary, but please verify that:
- A matching Git tag (
v29.4.1) is pushed. - The changelog was generated after the final commit so that the diff URL in CHANGELOG.md points to an existing tag.
- The published package on the registry will reflect this same version (CI/CD pipeline sometimes caches the previous build).
Run the quick scan below to ensure no lingering references to the old version are embedded in the repo or build artefacts:
🏁 Script executed:
#!/bin/bash
# Fail if any file (other than package.json / CHANGELOG) still mentions 29.4.0
rg -n '"29\.4\.0"' --color=always --glob '!.*/{package.json,CHANGELOG.md}'Length of output: 378
Action Required: Regenerate Lockfiles & Verify Release Artifacts
The version bump in package.json uncovered lingering references to 29.4.0 in your lock files. Please:
-
Regenerate and commit updated lockfiles so they reference
29.4.1
• examples/package-lock.json
• e2e/package-lock.json
(e.g. runnpm installornpm ciin each folder) -
Ensure a Git tag matching the new version is pushed:
git tag v29.4.1 && git push origin v29.4.1 -
Confirm CHANGELOG.md was generated after the final commit so its diff URL points at
v29.4.1. -
Verify your CI/CD publishes the correct package version (caching can sometimes hold onto the previous build).
🤖 Prompt for AI Agents
In package.json at line 3, after updating the version to 29.4.1, you need to
regenerate the lockfiles in examples/package-lock.json and e2e/package-lock.json
by running npm install or npm ci in those directories to update references from
29.4.0 to 29.4.1. Then commit these updated lockfiles. Next, create and push a
Git tag for v29.4.1 using git tag v29.4.1 and git push origin v29.4.1. Also,
ensure the CHANGELOG.md is generated after the final commit so its diff URL
points to v29.4.1. Finally, verify your CI/CD pipeline publishes the correct
package version without caching issues.
Summary by CodeRabbit