chore: update node packages (major) #722
Closed
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}
renovate
bot
force-pushed
the
renovate/major-node-packages
branch
2 times, most recently
from
693c870 to
74470d9
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/major-node-packages
branch
from
74470d9 to
d54e848
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^20.17.6->^22.0.03.45.2->4.0.024.1.0->25.0.1^5.11.2->^6.0.07.12.0->8.13.0^10.0.0->^11.0.0Release Notes
apexcharts/apexcharts.js (apexcharts)
v4.0.0: 💎 Version 4.0.0Compare Source
What's Changed
Upgrade to Svgjs 3.2.
Svg.js, the main engine behind ApexCharts’ drawing mechanism, was long overdue for an upgrade. With apexcharts@4.0.0, both Svg.js and all related plugins have been upgraded to their latest versions. This ensures that ApexCharts stays up-to-date with its dependencies.
Other fixes
New Contributors
Full Changelog: apexcharts/apexcharts.js@v3.54.1...v4.0.0
v3.54.1: 💎 Version 3.54.1Compare Source
What's Changed
Full Changelog: apexcharts/apexcharts.js@v3.54.0...v3.54.1
v3.54.0: 💎 Version 3.54.0Compare Source
What's Changed
New Contributors
Full Changelog: apexcharts/apexcharts.js@v3.53.0...v3.54.0
v3.53.0: 💎 Version 3.53.0Compare Source
What's new
New Property
series.hiddento hide certain series on initial render A short guide on how to use itNew method
Enhancements
Bugfixes
Announcements
New Contributors
Full Changelog: apexcharts/apexcharts.js@v3.52.0...v3.53.0
v3.52.0: 💎 Version 3.52.0Compare Source
What's Changed
New Contributors
Full Changelog: apexcharts/apexcharts.js@v3.51.0...v3.52.0
v3.51.0Compare Source
What's Changed
✨ More marker shapes ✨
Full Changelog: apexcharts/apexcharts.js@v3.50.0...v3.51.0
v3.50.0: 💎 Version 3.50.0Compare Source
What's Changed
rollup-plugin-terserwith@rollup/plugin-terserby @poteboy in https://github.com/apexcharts/apexcharts.js/pull/4547New Contributors
Full Changelog: apexcharts/apexcharts.js@v3.49.2...v3.50.0
v3.49.2: 💎 Version 3.49.2Compare Source
What's Changed
New Contributors
Full Changelog: apexcharts/apexcharts.js@v3.49.1...v3.49.2
v3.49.1: 💎 Version 3.49.1Compare Source
🆕 Enhancements
🐞 Bug fixes
v3.49.0: 💎 Version 3.49.0Compare Source
🐞 Bug fixes
v3.48.0: 💎 Version 3.48.0Compare Source
🆕 Enhancements
🐞 Bug fixes
Thanks @rosco54 for multiple y-axis scale fixes
v3.47.0: 💎 Version 3.47.0Compare Source
🆕 Enhancements
🐞 Bug fixes
Thanks @rosco54 for y-axis scale improvements
v3.46.0: 💎 Version 3.46.0Compare Source
🆕 Enhancements
🐞 Bug fixes
jsdom/jsdom (jsdom)
v25.0.1Compare Source
tough-cookie, which no longer prints a deprecation warning.v25.0.0Compare Source
This major release changes the prototype of a jsdom's
EventTarget.prototypeto point to theObject.prototypeinside the jsdom, instead of pointing to the Node.jsObject.prototype. Thus, the prototype chain ofWindowstays entirely within the jsdom, never crossing over into the Node.js realm.This only occurs when
runScriptsis set to non-default values of"dangerously"or"outside-only", as with the default value, there is no separateObject.prototypeinside the jsdom.This will likely not impact many programs, but could cause some changes in
instanceofbehavior, and so out of an abundance of caution, we're releasing it as a new major version.v24.1.3Compare Source
postMessage()that were done as a bare property (i.e.,postMessage()instead ofwindow.postMessage()).v24.1.2Compare Source
inoperator applied toEventTargetmethods, e.g.'addEventListener' in window, which only appeared in Node.js ≥22.5.0. (legendecas)blur(): it no longer firesfocusandfocusinon theDocument, andblurandfocusoutno longer have theirrelatedTargetproperty set. (asamuzaK)v24.1.1Compare Source
selectionchangeevent on theDocumentobject. (piotr-oles)openpgpjs/openpgpjs (openpgp)
v6.0.0Compare Source
What's Changed
OpenPGP.js v6 adds support for the new version of the OpenPGP specification, RFC 9580. It also increases compliance with the specification, as demonstrated by the OpenPGP interoperability test suite.
OpenPGP.js v6 only makes minor API changes.
This is the first stable release of OpenPGP.js v6: no more breaking changes to the high-level API will be made until the next major release.
For the changes since the previous pre-release (v6.0.0-beta.3.patch.1), see the end of this message.
Here we list a summary of the main changes since v5:
Platform support changes
module(type: modulein package.json), and declares exports, alongside the legacy package.json entrypoints, which should ensure backwards compatibility. Still, bundlers might be affected by the package.json changes depending on how they load the library.SubtleCrypto(insecure contexts are no longer supported, asSubtleCryptois not available there)BigInts (not supported by e.g. Safari 13 and below, see full compatibility table)SymEncryptedSessionKeyPacket.s2k?.type === 'argon2'orSecretKeyPacket|SecretSubkeyPacket.keyPacket.s2k?.type === 'argon2'.Breaking API changes
read[Private]Key: support parsing key blocks (return first parsable key); previously, parsing would fail if a block with more than one key was given in input (#1755)PrivateKey.getDecryptionKeyswill now throw if no decryption key is found (#1789). Previously, an empty array was returned. As a consequence of this change, someopenpgp.decrypterrors will be more specific.config.allowMissingKeyFlagsbelow)config.nonDeterministicSignaturesViaNotation(defaulting to true) has been added to turn off the feature..v5Keysflag and encrypted withconfig.aeadProtect = true) cannot be decrypted by OpenPGP.js v6 (viadecryptKey) out-of-the-box (seeconfig.parseAEADEncryptedV4KeysAsLegacybelow) (#1672)config.enableParsingV5Entitiesbelow). The affected entities are non-standard, and in the RFC 9580 they have been superseded by v6 keys, v6 signatures and SEIPDv2 encrypted data, respectively. However, generation of v5 entities was supported behind config flags in OpenPGP.js v5, and some other libraries, hence parsing them might be necessary in some cases. (#1774 , #1779)Configuration changes
config.v5Keysflag and corresponding key generation. The flag is replaced by.v6Keys, and results in a different key format.config.aeadProtectflag has a different effect than in v5:config.parseAEADEncryptedV4KeysAsLegacyto allow decrypting AEAD-encrypted v4 keys from OpenPGP.js v5 or older (namely keys generated without.v5Keysflag and encrypted withconfig.aeadProtect = true) (#1672).config.enableParsingV5Entitiesto enable parsing support for v5 entities (https://github.com/openpgpjs/openpgpjs/pull/1774 , #1779)config.allowMissingKeyFlagsto bypass the missing key flag check (see https://github.com/openpgpjs/openpgpjs/pull/1677)config.minBytesForWebCrypto, and always use WebCrypto if available, since there is no longer a performance overhead for small messages.enums.publicKey.eddsain favour ofenums.publicKey.eddsaLegacyenums.curve.ed25519Legacyto'ed25519Legacy'(was:'ed25519')enums.curve.curve25519Legacyto'curve25519Legacy'(was:'curve25519')config.useIndutnyEllipticto.useEllipticFallback, to reflect the change of underlying library.enums.symmetric.plaintext(internally unused)enums.curve.p256,.p384,.p521are now marked as@deprecated(to be dropped in the main release)enums.curve.nistP256,.nistP384,.nistP521.'p256','p384','p521'to'nistP256','nistP384','nistP521'(these new values are expected bygenerateKey, for theoptions.curveargument).config.deflateLevel(#1717)config.revocationsExpire, always honor revocation expiration (#1736): the option used to default to false, and ignore revocation expirations. We now honor those expirations, namely match the behavior resulting from setting the option to true.config.preferredHashAlgorithm) to SHA512 (#1801)New API options
openpgp.sign,recipientKeysandrecipientUserIDsoptions have been added. These can be used to influence the selection of the hash algorithm via the algorithm preferences of the recipient keys, to ensure that the recipients will support the selected hash algorithm.Similarly, when signing+encrypting using
openpgp.encrypt, theencryptionKeysare now used to determine the preferred hash algorithms, instead of thesigningKeys. (https://github.com/openpgpjs/openpgpjs/pull/1802)Full Changelog: openpgpjs/openpgpjs@v5.11.0...v6.0.0.
For additional context about the changes introduced by OpenPGP.js v6, you can also refer to the changelog of the various prereleases, starting from v6.0.0-alpha.0.
Changes since v6.0.0-beta.3.patch.1: the main changes since the previous pre-release are the changes to the handling of preferred hash algorithms mentioned above (#1801 and #1802). For the full changelog, see openpgpjs/openpgpjs@v6.0.0-beta.3.patch.1...v6.0.0.
v5.11.2Compare Source
What's Changed
openpgp.verify: fix bug preventing verification of detached signatures over streamed data (#1762)Full Changelog: openpgpjs/openpgpjs@v5.11.1...v5.11.2
typescript-eslint/typescript-eslint (typescript-eslint)
v8.13.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.12.2Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.12.1Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.12.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.11.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.10.0Compare Source
🩹 Fixes
namefield to extended configs inconfighelper (#10094)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.9.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.8.1Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.8.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.7.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.6.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.5.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.4.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.3.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.2.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.1.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.0.1Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.0.0Compare Source
🚀 Features
eslint-plugin: deprecate no-loss-of-precision extension rule
utils: allow specifying additional rule meta.docs in RuleCreator
eslint-plugin: split no-empty-object-type out from ban-types and no-empty-interfaces
typescript-estree: stabilize EXPERIMENTAL_useProjectService as projectService
eslint-plugin: remove deprecated no-throw-literal rule
eslint-plugin: apply initial config changes for v8
eslint-plugin: remove no-useless-template-literals
eslint-plugin: replace ban-types with no-restricted-types, no-unsafe-function-type, no-wrapper-object-types
eslint-plugin: [no-unnecessary-type-parameters] promote to strict
🩹 Fixes
disable
projectServiceindisabled-type-checkedshared configeslint-plugin: correct rules.d.ts types to not rely on non-existent imports
❤️ Thank You
You can read about our versioning strategy and releases on our website.
7.18.0 (2024-07-29)
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
7.17.0 (2024-07-22)
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
7.16.1 (2024-07-15)
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
7.16.0 (2024-07-08)
🚀 Features
🩹 Fixes
deps: update dependency @eslint-community/regexpp to v4.11.0
website: react key error on internal pages of website
❤️ Thank You
You can read about our versioning strategy and releases on our website.
7.15.0 (2024-07-01)
🚀 Features
🩹 Fixes
EXPERIMENTAL_useProjectServiceindisabled-type-checkedshared config❤️ Thank You
You can read about our versioning strategy and releases on our website.
7.14.1 (2024-06-24)
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
7.14.0 (2024-06-24)
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
7.13.1 (2024-06-17)
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
7.13.0 (2024-06-10)
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
7.12.0 (2024-06-03)
🚀 Features
no-useless-template-expression(deprecateno-useless-template-literals)🩹 Fixes
❤️ Thank You
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.