t.behrendt/conventional-semantic-git-tag-increment
1
0
Fork 0
Code Issues 1 Pull Requests 3 Actions Releases Activity

chore(deps): update dependencies (non-major) #16

Merged
t.behrendt merged 1 commits from renovate/dependencies-(non-major) into main 2025-10-02 08:02:24 +02:00
Conversation 1 Commits 1 Files Changed 1 +148 -117
renovate-bot commented 2025-09-12 23:01:45 +02:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change Pending
@types/node (source) devDependencies minor 24.3.1 -> 24.5.2 24.6.2 (+2)
esbuild devDependencies patch 0.25.9 -> 0.25.10
ts-jest (source) devDependencies patch 29.4.1 -> 29.4.2 29.4.4 (+1)

Release Notes

evanw/esbuild (esbuild)

v0.25.10

Compare Source

  • Fix a panic in a minification edge case (#​4287)

    This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

    function identity(x) { return x }
identity({ y: identity(123) })

  • Fix @supports nested inside pseudo-element (#​4265)

    When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

    The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

    However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:

    /* Original code */
::placeholder {
  color: red;
  body & { color: green }
  @​supports (color: blue) { color: blue }
}

/* Old output (with --supported:nesting=false) */
::placeholder {
  color: red;
}
body :is() {
  color: green;
}
@​supports (color: blue) {
   {
    color: blue;
  }
}

/* New output (with --supported:nesting=false) */
::placeholder {
  color: red;
}
body :is() {
  color: green;
}
@​supports (color: blue) {
  ::placeholder {
    color: blue;
  }
}
kulshekhar/ts-jest (ts-jest)

v29.4.2

Compare Source

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | devDependencies | minor | [`24.3.1` -> `24.5.2`](https://renovatebot.com/diffs/npm/@types%2fnode/24.3.1/24.5.2) | `24.6.2` (+2) | | [esbuild](https://github.com/evanw/esbuild) | devDependencies | patch | [`0.25.9` -> `0.25.10`](https://renovatebot.com/diffs/npm/esbuild/0.25.9/0.25.10) | | | [ts-jest](https://kulshekhar.github.io/ts-jest) ([source](https://github.com/kulshekhar/ts-jest)) | devDependencies | patch | [`29.4.1` -> `29.4.2`](https://renovatebot.com/diffs/npm/ts-jest/29.4.1/29.4.2) | `29.4.4` (+1) | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.25.10`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#02510) [Compare Source](https://github.com/evanw/esbuild/compare/v0.25.9...v0.25.10) - Fix a panic in a minification edge case ([#&#8203;4287](https://github.com/evanw/esbuild/issues/4287)) This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value `undefined` in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying): ```js function identity(x) { return x } identity({ y: identity(123) }) ``` - Fix `@supports` nested inside pseudo-element ([#&#8203;4265](https://github.com/evanw/esbuild/issues/4265)) When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as `::placeholder` for correctness. The [CSS nesting specification](https://www.w3.org/TR/css-nesting-1/) says the following: > The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms. However, it seems like this behavior is different for nested at-rules such as `@supports`, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account: ```css /* Original code */ ::placeholder { color: red; body & { color: green } @&#8203;supports (color: blue) { color: blue } } /* Old output (with --supported:nesting=false) */ ::placeholder { color: red; } body :is() { color: green; } @&#8203;supports (color: blue) { { color: blue; } } /* New output (with --supported:nesting=false) */ ::placeholder { color: red; } body :is() { color: green; } @&#8203;supports (color: blue) { ::placeholder { color: blue; } } ``` </details> <details> <summary>kulshekhar/ts-jest (ts-jest)</summary> ### [`v29.4.2`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2942-2025-09-15) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.1...v29.4.2) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjQxLjEyNC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate-bot changed title from chore(deps): update dependency @types/node to v24.3.2 to chore(deps): update dependency @types/node to v24.3.3 2025-09-13 07:01:00 +02:00
renovate-bot changed title from chore(deps): update dependency @types/node to v24.3.3 to chore(deps): update dependency @types/node to v24.4.0 2025-09-14 13:01:15 +02:00
renovate-bot changed title from chore(deps): update dependency @types/node to v24.4.0 to chore(deps): update dependencies (non-major) 2025-09-15 21:02:11 +02:00
renovate-bot changed title from chore(deps): update dependencies (non-major) to chore(deps): update dependency @types/node to v24.3.2 2025-09-26 22:06:54 +02:00
renovate-bot changed title from chore(deps): update dependency @types/node to v24.3.2 to chore(deps): update dependency @types/node to v24.3.3 2025-09-27 06:04:28 +02:00
renovate-bot changed title from chore(deps): update dependency @types/node to v24.3.3 to chore(deps): update dependency @types/node to v24.4.0 2025-09-28 13:02:09 +02:00
renovate-bot changed title from chore(deps): update dependency @types/node to v24.4.0 to chore(deps): update dependencies (non-major) 2025-09-29 21:02:28 +02:00
renovate-bot added 1 commit 2025-10-02 06:07:00 +02:00
chore(deps): update dependencies (non-major)
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
CI / Check Dist (pull_request) Successful in 12s
Details
CI / Dry-Run Prerelease (pull_request) Successful in 12s
Details
CI / Dry-Run (pull_request) Successful in 44s
Details
CI / Test (pull_request) Successful in 56s
Details
a83624e070
t.behrendt approved these changes 2025-10-02 08:02:18 +02:00
t.behrendt merged commit d3f0376d67 into main 2025-10-02 08:02:24 +02:00
t.behrendt deleted branch renovate/dependencies-(non-major) 2025-10-02 08:02:25 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
t.behrendt
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
renovate-bot t.behrendt
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t.behrendt/conventional-semantic-git-tag-increment#16
Delete Branch "renovate/dependencies-(non-major)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?