This repository has been archived by the owner on Jan 2, 2025. It is now read-only.
chore: update releases #171
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/releases
branch
from
6c0ebc6 to
3010c3f
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update Request | Renovate Bot
This PR contains the following updates:
v3->v4v3.1.0->v5.11.0v2.2.0->v3.3.0v4.6.0->v5.6.1v2.9.0->v3.8.0v2.2.0->v3.2.020.5.1-alpine->22.12.0-alpine1.32.6-alpine->1.32.7-alpineRelease Notes
actions/checkout (actions/checkout)
v4Compare Source
docker/bake-action (docker/bake-action)
v5.11.0Compare Source
list-targetssubaction changes:Full Changelog: docker/bake-action@v5.10.0...v5.11.0
v5.10.0Compare Source
allowinput by @crazy-max in https://github.com/docker/bake-action/pull/253Full Changelog: docker/bake-action@v5.9.0...v5.10.0
v5.9.0Compare Source
Full Changelog: docker/bake-action@v5.8.0...v5.9.0
v5.8.0Compare Source
Full Changelog: docker/bake-action@v5.7.0...v5.8.0
v5.7.0Compare Source
Full Changelog: docker/bake-action@v5.6.1...v5.7.0
v5.6.1Compare Source
Full Changelog: docker/bake-action@v5.6.0...v5.6.1
v5.6.0Compare Source
Full Changelog: docker/bake-action@v5.5.0...v5.6.0
v5.5.0Compare Source
Full Changelog: docker/bake-action@v5.4.0...v5.5.0
v5.4.0Compare Source
Full Changelog: docker/bake-action@v5.3.0...v5.4.0
v5.3.0Compare Source
DOCKER_BUILD_RECORD_UPLOADenvironment variable to enable/disable build record upload by @crazy-max in https://github.com/docker/bake-action/pull/230DOCKER_BUILD_NO_SUMMARYhas been deprecated. SetDOCKER_BUILD_SUMMARYtofalseinstead by @crazy-max in https://github.com/docker/bake-action/pull/227 https://github.com/docker/bake-action/pull/229Full Changelog: docker/bake-action@v5.2.0...v5.3.0
v5.2.0Compare Source
Full Changelog: docker/bake-action@v5.1.0...v5.2.0
v5.1.0Compare Source
Full Changelog: docker/bake-action@v5.0.2...v5.1.0
v5.0.2Compare Source
Full Changelog: docker/bake-action@v5.0.1...v5.0.2
v5.0.1Compare Source
Full Changelog: docker/bake-action@v5.0.0...v5.0.1
v5.0.0Compare Source
Full Changelog: docker/bake-action@v4.6.0...v5.0.0
v4.6.0Compare Source
Full Changelog: docker/bake-action@v4.5.0...v4.6.0
v4.5.0Compare Source
runs.postinaction.ymlby @crazy-max in https://github.com/docker/bake-action/pull/203Full Changelog: docker/bake-action@v4.4.0...v4.5.0
v4.4.0Compare Source
Full Changelog: docker/bake-action@v4.3.0...v4.4.0
v4.3.0Compare Source
Full Changelog: docker/bake-action@v4.2.0...v4.3.0
v4.2.0Compare Source
Full Changelog: docker/bake-action@v4.1.0...v4.2.0
v4.1.0Compare Source
list-targetssubaction by @crazy-max in https://github.com/docker/bake-action/pull/174filesinput not mandatory by @felipecrs in https://github.com/docker/bake-action/pull/170Full Changelog: docker/bake-action@v4.0.0...v4.1.0
v4.0.0Compare Source
Full Changelog: docker/bake-action@v3.1.0...v4.0.0
docker/login-action (docker/login-action)
v3.3.0Compare Source
Full Changelog: docker/login-action@v3.2.0...v3.3.0
v3.2.0Compare Source
Full Changelog: docker/login-action@v3.1.0...v3.2.0
v3.1.0Compare Source
Full Changelog: docker/login-action@v3.0.0...v3.1.0
v3.0.0Compare Source
Full Changelog: docker/login-action@v2.2.0...v3.0.0
docker/metadata-action (docker/metadata-action)
v5.6.1Compare Source
Full Changelog: docker/metadata-action@v5.6.0...v5.6.1
v5.6.0Compare Source
commit_dateglobal expression by @trim21 in https://github.com/docker/metadata-action/pull/471 https://github.com/docker/metadata-action/pull/475Full Changelog: docker/metadata-action@v5.5.1...v5.6.0
v5.5.1Compare Source
cwd://prefix for local bake files by @crazy-max in https://github.com/docker/metadata-action/pull/382Full Changelog: docker/metadata-action@v5.5.0...v5.5.1
v5.5.0Compare Source
cwd://prefix for bake files path by @crazy-max in https://github.com/docker/metadata-action/pull/370Full Changelog: docker/metadata-action@v5.4.0...v5.5.0
v5.4.0Compare Source
Full Changelog: docker/metadata-action@v5.3.0...v5.4.0
v5.3.0Compare Source
Full Changelog: docker/metadata-action@v5.2.0...v5.3.0
v5.2.0Compare Source
Full Changelog: docker/metadata-action@v5.1.0...v5.2.0
v5.1.0Compare Source
Full Changelog: docker/metadata-action@v5.0.0...v5.1.0
v5.0.0Compare Source
Full Changelog: docker/metadata-action@v4.6.0...v5.0.0
docker/setup-buildx-action (docker/setup-buildx-action)
v3.8.0Compare Source
v3.7.1Compare Source
uuidpackage by @crazy-max in https://github.com/docker/setup-buildx-action/pull/369Full Changelog: docker/setup-buildx-action@v3.7.0...v3.7.1
v3.7.0Compare Source
buildkitd-flagsif opt-in by @crazy-max in https://github.com/docker/setup-buildx-action/pull/363uuidpackage and switch tocryptoby @crazy-max in https://github.com/docker/setup-buildx-action/pull/366Full Changelog: docker/setup-buildx-action@v3.6.1...v3.7.0
v3.6.1Compare Source
Full Changelog: docker/setup-buildx-action@v3.6.0...v3.6.1
v3.6.0Compare Source
Full Changelog: docker/setup-buildx-action@v3.5.0...v3.6.0
v3.5.0Compare Source
v3.4.0Compare Source
Full Changelog: docker/setup-buildx-action@v3.3.0...v3.4.0
v3.3.0Compare Source
v3.2.0Compare Source
configtobuildkitd-configconfig-inlinetobuildkitd-config-inlineFull Changelog: docker/setup-buildx-action@v3.1.0...v3.2.0
v3.1.0Compare Source
v3.0.0Compare Source
Full Changelog: docker/setup-buildx-action@v2.10.0...v3.0.0
v2.10.0Compare Source
What's Changed
Full Changelog: docker/setup-buildx-action@v2.9.1...v2.10.0
v2.9.1Compare Source
Full Changelog: docker/setup-buildx-action@v2.9.0...v2.9.1
docker/setup-qemu-action (docker/setup-qemu-action)
v3.2.0Compare Source
Full Changelog: docker/setup-qemu-action@v3.1.0...v3.2.0
v3.1.0Compare Source
docker.iodomain for default binfmt image by @crazy-max in https://github.com/docker/setup-qemu-action/pull/151Full Changelog: docker/setup-qemu-action@v3.0.0...v3.1.0
v3.0.0Compare Source
Full Changelog: docker/setup-qemu-action@v2.2.0...v3.0.0
nodejs/node (node)
v22.12.0Compare Source
v22.11.0: 2024-10-29, Version 22.11.0 'Jod' (LTS), @richardlauCompare Source
Notable Changes
This release marks the transition of Node.js 22.x into Long Term Support (LTS)
with the codename 'Jod'. The 22.x release line now moves into "Active LTS"
and will remain so until October 2025. After that time, it will move into
"Maintenance" until end of life in April 2027.
Other than updating metadata, such as the
process.releaseobject, to reflectthat the release is LTS, no further changes from Node.js 22.10.0 are included.
OpenSSL 3.x
Official binaries for Node.js 22.x currently include OpenSSL 3.0.x (more
specifically, the quictls OpenSSL fork).
OpenSSL 3.0.x is the currently designated long term support version that is
scheduled to be supported until 7th September 2026, which is within the expected
lifetime of Node.js 22.x. We are expecting upstream OpenSSL to announce a
successor long term support version prior to that date and since OpenSSL now
follows a semantic versioning-like versioning scheme we expect to be able to
update to the next long term supported version of OpenSSL during the lifetime of
Node.js 22.x.
v22.10.0: 2024-10-16, Version 22.10.0 (Current), @aduh95Compare Source
Notable Changes
New
"module-sync"exports conditionThis release introduces a
"module-sync"exports condition that's enabled whenrequire(esm)is enabled, so packages can supply a synchronous ES module to theNode.js module loader, no matter if it's being required or imported. This is
similar to the
"module"condition that bundlers have been using to supportrequire(esm)in Node.js, and allows dual-package authors to opt into ESM-firstonly on newer versions of Node.js that supports
require(esm)to avoid thedual-package hazard.
{ "type": "module", "exports": { "node": { // On new version of Node.js, both require() and import get // the ESM version "module-sync": "./index.js", // On older version of Node.js, where "module-sync" and require(esm) are // not supported, use the CJS version to avoid dual-package hazard. // When package authors think it's time to drop support for older versions of // Node.js, they can remove the exports conditions and just use "main": "index.js". "default": "./dist/index.cjs" }, // On any other environment, use the ESM version. "default": "./index.js" } }Or if the package is only meant to be run on Node.js and wants to fallback to
CJS on older versions that don't have
require(esm):{ "type": "module", "exports": { // On new version of Node.js, both require() and import get the ESM version "module-sync": "./index.js", // On older version of Node.js, where "module-sync" and require(esm) are // not supported, use the CJS version to avoid dual-package hazard. // When package authors think it's time to drop support for older versions of // Node.js, they can remove the exports conditions and just use "main": "index.js". "default": "./dist/index.cjs" } }For package authors: this only serves as a feature-detection mechanism for
packages that wish to support both CJS and ESM users during the period when some
active Node.js LTS versions support
require(esm)while some older ones don't.When all active Node.js LTS lines support
require(esm), packages can simplifytheir distributions by bumping the major version, dropping their CJS exports,
and removing the
module-syncexports condition (with onlymainordefaulttargetting the ESM exports). If the package needs to support both bundlers and
being run unbundled on Node.js during the transition period, use both
module-syncandmoduleand point them to the same ESM file. If the packagealready doesn't want to support older versions of Node.js that doesn't support
require(esm), don't use this export condition.For bundlers/tools: they should avoid implementing this stop-gap condition.
Most existing bundlers implement the de-facto bundler standard
moduleexports condition, and that should be enough to support users who want to bundle
ESM from CJS consumers. Users who want both bundlers and Node.js to recognize
the ESM exports can use both
module/module-syncconditions during thetransition period, and can drop
module-sync+modulewhen they no longer needto support older versions of Node.js. If tools do want to support this
condition, it's recommended to make the resolution rules in the graph pointed by
this condition match the Node.js native ESM rules to avoid divergence.
We ended up implementing a condition with a different name instead of reusing
"module", because existing code in the ecosystem using the"module"condition sometimes also expect the module resolution for these ESM files to
work in CJS style, which is supported by bundlers, but the native Node.js loader
has intentionally made ESM resolution different from CJS resolution (e.g.
forbidding
import './noext'orimport './directory'), so it would bebreaking to implement a
"module"condition without implementing the forbiddenESM resolution rules. For now, this just implements a new condition as
semver-minor so it can be backported to older LTS.
Contributed by Joyee Cheung in #54648.
node --runis now stableThis CLI flag runs a specified command from a
package.json's"scripts"object.For the following
package.json:{ "scripts": { "test": "node --test-reporter junit --test ./test" } }You can run
node --run testand that would start the test suite.Contributed by Yagiz Nizipli in #53763.
Other notable changes
f0b441230a] - (SEMVER-MINOR) crypto: addKeyObject.prototype.toCryptoKey(Filip Skokan) #55262349d2ed07b] - (SEMVER-MINOR) crypto: add Date fields forvalidToandvalidFrom(Andrew Moon) #54159bebc95ed58] - doc: add abmusse to collaborators (Abdirahim Musse) #55086914db60159] - (SEMVER-MINOR) http2: exposenghttp2_option_set_stream_reset_rate_limitas an option (Maël Nison) #54875f7c3b03759] - (SEMVER-MINOR) lib: propagate aborted state to dependent signals before firing events (jazelly) #5482632261fc98a] - (SEMVER-MINOR) module: support loading entrypoint as url (RedYetiDev) #5493306957ff355] - (SEMVER-MINOR) module: implementflushCompileCache()(Joyee Cheung) #549712dcf70c347] - (SEMVER-MINOR) module: throw when invalid argument is passed toenableCompileCache()(Joyee Cheung) #54971f9b19d7c44] - (SEMVER-MINOR) module: write compile cache to temporary file and then rename it (Joyee Cheung) #54971e95163b170] - (SEMVER-MINOR) process: addprocess.features.require_module(Joyee Cheung) #552414050f68e5d] - (SEMVER-MINOR) process: addprocess.features.typescript(Aviv Keller) #5429586f7cb802d] - (SEMVER-MINOR) test_runner: support custom arguments inrun()(Aviv Keller) #55126b62f2f8259] - (SEMVER-MINOR) test_runner: add'test:summary'event (Colin Ihrig) #54851d7c708aec5] - (SEMVER-MINOR) test_runner: add support for coverage viarun()(Chemi Atlow) #539375fda4a1498] - (SEMVER-MINOR) worker: addmarkAsUncloneableapi (Jason Zhang) #55234Commits
e3619510c8] - assert: show the diff when deep comparing data with a custom message (Giovanni) #5475939c7a9e70c] - benchmark: adjust config for deepEqual object (Rafael Gonzaga) #55254263526d5d0] - benchmark: rewrite detect-esm-syntax benchmark (Joyee Cheung) #55238cd0795fb00] - benchmark: add no-warnings to process.has bench (Rafael Gonzaga) #551594352d9cc31] - benchmark: create benchmark for typescript (Marco Ippolito) #54904452bc9b48d] - benchmark: add webstorage benchmark (jakecastelli) #55040d4d5ba3a9b] - benchmark: include ascii to fs/readfile (Rafael Gonzaga) #5498823b628db65] - benchmark: add dotenvConfiguration
📅 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 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.