chore(release): 29.4.3

[ahnpnl]

Summary by CodeRabbit

• New Version

  • Released 29.4.3.

• Bug Fixes

  • Replaced the deprecated isolatedModules setting with a transpilation option to ensure compatibility and stability.

• Documentation

  • Updated help and deprecation messages to include direct links to the transpilation setup guide.
  • Added a changelog entry detailing the bug fix and related issue references.

• Chores

  • Bumped package version to 29.4.3.

[coderabbitai]

Walkthrough

Updates version to 29.4.3, adds a 29.4.3 changelog entry, and refines two message strings to include/adjust documentation links referencing the new transpilation option replacing isolatedModules. No runtime or API changes.

Changes

Cohort / File(s)	Summary
Versioning and metadata CHANGELOG.md, package.json	Added 29.4.3 changelog entry noting bug fix related to transpilation option; bumped package version from 29.4.2 to 29.4.3.
User-facing messages src/utils/messages.ts	Updated Helps.UsingModernNodeResolution and Deprecations.ReplaceIsolatedModulesWithTranspilation strings to point to updated docs URLs and include a link hint; no logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• kulshekhar

Poem

A nibble of version, a hop to .3,
I tightened our messages—linked docs with glee.
The burrow’s now tidy, the path clearly shown,
From isolatedModules to transpilation we’ve grown.
Thump-thump! says the rabbit, shipping bug-free. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "chore(release): 29.4.3" succinctly and accurately describes the main change—a release bump to version 29.4.3—which matches the changeset (package.json version update and new 29.4.3 changelog entry); it is concise and conventional for release PRs so teammates can quickly understand the intent.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/29.4.3

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/utils/messages.ts (1)

31-31: Fix minor grammar and clarify config location in user-facing help.

Current text has “in for” and is a bit unclear about where to set the option.

Apply:

-  UsingModernNodeResolution = 'Using hybrid module kind (Node16/18/Next) is only supported in "transpilation: true". Please set "transpilation: true" in for `ts-jest` config in your Jest config file, see https://kulshekhar.github.io/ts-jest/docs/getting-started/options/transpilation',
+  UsingModernNodeResolution = 'Using hybrid module kind (Node16/18/Next) is only supported when "transpilation" is set to true. Please set "transpilation: true" in the `ts-jest` transformer options in your Jest config file. See https://kulshekhar.github.io/ts-jest/docs/getting-started/options/transpilation',

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5868761 and 0bfb657.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• CHANGELOG.md (1 hunks)
• package.json (1 hunks)
• src/utils/messages.ts (2 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-08-05T08:03:52.583Z

Learnt from: ahnpnl
PR: kulshekhar/ts-jest#4976
File: examples/js-with-babel/package.json:14-19
Timestamp: 2025-08-05T08:03:52.583Z
Learning: ts-jest version 29 supports both Jest 29 and Jest 30, so having ts-jest 29.x with Jest 30.x is not a compatibility issue and should not be flagged as a version mismatch problem.

Applied to files:

• package.json
• CHANGELOG.md

🔇 Additional comments (3)

CHANGELOG.md (1)

1-8: Changelog entry reads well and is in the right place.

Header, date (2025-09-17), and compare link format look correct.

src/utils/messages.ts (1)

49-50: Approve — doc link resolves (HTTP 200). Non-blocking; no changes required.

package.json (1)

3-3: Approve version bump — changelog entry present.
package.json version 29.4.3 matches CHANGELOG.md entry "## [29.4.3] (2025-09-17)".