Closed renovate[bot] closed 2 months ago
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.
This PR contains the following updates:
22.7.0-slim
->22.8.0-slim
15.5.27
->15.5.29
Release Notes
nodejs/node (node)
### [`v22.8.0`](https://redirect.github.com/nodejs/node/releases/tag/v22.8.0): 2024-09-03, Version 22.8.0 (Current), @RafaelGSS [Compare Source](https://redirect.github.com/nodejs/node/compare/v22.7.0...v22.8.0) ##### New JS API for compile cache This release adds a new API `module.enableCompileCache()` that can be used to enable on-disk code caching of all modules loaded after this API is called. Previously this could only be enabled by the `NODE_COMPILE_CACHE` environment variable, so it could only set by end-users. This API allows tooling and library authors to enable caching of their own code. This is a built-in alternative to the [v8-compile-cache](https://www.npmjs.com/package/v8-compile-cache)/[v8-compile-cache-lib ](https://www.npmjs.com/package/v8-compile-cache-lib) packages, but have [better performance](https://redirect.github.com/nodejs/node/issues/47472#issuecomment-1970331362) and supports ESM. Thanks to Joyee Cheung for working on this. ##### New option for vm.createContext() to create a context with a freezable globalThis Node.js implements a flavor of `vm.createContext()` and friends that creates a context without contextifying its global object when vm.constants.DONT_CONTEXTIFY is used. This is suitable when users want to freeze the context (impossible when the global is contextified i.e. has interceptors installed) or speed up the global access if they don't need the interceptor behavior. Thanks to Joyee Cheung for working on this. ##### Support for coverage thresholds Node.js now supports requiring code coverage to meet a specific threshold before the process exits successfully. To use this feature, you need to enable the `--experimental-test-coverage` flag. You can set thresholds for the following types of coverage: - **Branch coverage**: Use `--test-coverage-branches=bitnami/charts (postgresql)
### [`v15.5.29`](https://redirect.github.com/bitnami/charts/blob/HEAD/bitnami/postgresql/CHANGELOG.md#15529-2024-09-10) - \[bitnami/postgresql] Release 15.5.29 ([#29330](https://redirect.github.com/bitnami/charts/pull/29330)) ### [`v15.5.28`](https://redirect.github.com/bitnami/charts/blob/HEAD/bitnami/postgresql/CHANGELOG.md#15528-2024-09-05) - \[bitnami/postgresql] Release 15.5.28 ([#29206](https://redirect.github.com/bitnami/charts/pull/29206))Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: