Skip to content

chore(release): 29.4.1 #4973

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 3, 2025
Merged

chore(release): 29.4.1 #4973

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,12 @@
## [29.4.1](https://github.com/kulshekhar/ts-jest/compare/v29.4.0...v29.4.1) (2025-08-03)


## Bug Fixes

* fix: replace `ejs` with `handlebars` due to security issues ([899c9b7](https://github.com/kulshekhar/ts-jest/commit/899c9b7)), closes [#4969](https://github.com/kulshekhar/ts-jest/issues/4969)



## [29.4.0](https://github.com/kulshekhar/ts-jest/compare/v29.3.4...v29.4.0) (2025-06-11)


Expand Down
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "ts-jest",
"version": "29.4.0",
"version": "29.4.1",
Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Double-check downstream artefacts after the version bump

Updating the version field is necessary, but please verify that:

  1. A matching Git tag (v29.4.1) is pushed.
  2. The changelog was generated after the final commit so that the diff URL in CHANGELOG.md points to an existing tag.
  3. 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. run npm install or npm ci in 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.

"main": "dist/index.js",
"types": "dist/index.d.ts",
"type": "commonjs",
Expand Down
Loading