Skip to content
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

Jump to bottom

chore: update node packages (major) #828

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: update node packages (major) #828

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 13, 2025 •
edited
Loading

Update Request | Renovate Bot

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@kubernetes/client-node ^0.22.2 -> ^1.0.0 age adoption passing confidence
@types/node (source) ^20.17.6 -> ^22.0.0 age adoption passing confidence
apexcharts (source) 3.45.2 -> 4.3.0 age adoption passing confidence
jsdom ^25.0.1 -> ^26.0.0 age adoption passing confidence
openpgp (source) ^5.11.2 -> ^6.0.0 age adoption passing confidence
typescript-eslint (source) 7.12.0 -> 8.19.1 age adoption passing confidence
uuid ^10.0.0 -> ^11.0.0 age adoption passing confidence
vite (source) ^5.4.10 -> ^6.0.0 age adoption passing confidence

Release Notes

kubernetes-client/javascript (@​kubernetes/client-node)

v1.0.0

Compare Source

Release 1.0.0 with node-fetch instead of the long deprecated request-library.

There is no migration guide (yet?). Have a look at the examples to see how to use it.

v0.22.3

Compare Source

v0.22.2

Compare Source

v0.22.1

Compare Source

What's Changed
New Contributors

Full Changelog: kubernetes-client/javascript@0.22.0...0.22.1

v0.22.0

Compare Source

What's Changed

New Contributors

Full Changelog: kubernetes-client/javascript@0.21.0...0.22.0

apexcharts/apexcharts.js (apexcharts)

v4.3.0: 💎 Version 4.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: apexcharts/apexcharts.js@v4.2.0...v4.3.0

v4.2.0: 💎 Version 4.2.0

Compare Source

What's Changed

Documentation update
  • Migrated all react samples from class components to functional components

New Contributors

Full Changelog: apexcharts/apexcharts.js@v4.1.0...v4.2.0

v4.1.0: 💎 Version 4.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: apexcharts/apexcharts.js@v4.0.0...v4.1.0

v4.0.0: 💎 Version 4.0.0

Compare 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 [email protected], 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.1

Compare Source

What's Changed

Full Changelog: apexcharts/apexcharts.js@v3.54.0...v3.54.1

v3.54.0: 💎 Version 3.54.0

Compare Source

What's Changed

New Contributors

Full Changelog: apexcharts/apexcharts.js@v3.53.0...v3.54.0

v3.53.0: 💎 Version 3.53.0

Compare Source

What's new

New Property

New method

  • highlightSeries; In a multi-series chart, call this method to reduce opacity of all other series and only highlight a particular one.

Enhancements

  • Mousewheel support for zooming; references #​960

Bugfixes

Announcements

  • End support for IE11.

New Contributors

Full Changelog: apexcharts/apexcharts.js@v3.52.0...v3.53.0

v3.52.0: 💎 Version 3.52.0

Compare Source

What's Changed

New Contributors

Full Changelog: apexcharts/apexcharts.js@v3.51.0...v3.52.0

v3.51.0

Compare Source

What's Changed
✨ More marker shapes ✨

hswil69ah

Full Changelog: apexcharts/apexcharts.js@v3.50.0...v3.51.0

v3.50.0: 💎 Version 3.50.0

Compare Source

What's Changed

  • Refactor markers code for generating new markers shapes (plus, cross, line)
Screenshot 2024-07-05 at 11 27 12 PM

New Contributors

Full Changelog: apexcharts/apexcharts.js@v3.49.2...v3.50.0

v3.49.2: 💎 Version 3.49.2

Compare Source

What's Changed

New Contributors

Full Changelog: apexcharts/apexcharts.js@v3.49.1...v3.49.2

v3.49.1: 💎 Version 3.49.1

Compare Source

🆕 Enhancements

basic-slope-chart

🐞 Bug fixes

  • Fix issue #​4216: grid padding calculation to support array of stroke widths, thanks @​veryinsanee
  • Fix heatmap yaxis offset #​2033, thanks @​cart-before-horse
  • FIx types (yaxis.seriesName as an Array), thanks @​j2ghz
  • Remove redundant graphics.move() from end of lower rangeArea paths. - thanks @​rosco54
  • Fix #​4386; pie chart size issue when given in percentage
  • Fix #​3827 - y-axis tooltip value in reversed
  • Fix #​4348 - dumbbell chart fix for timescale xaxis
  • Fix #​2251 - pie chart dataPointIndex when clicked
  • Fix #​4206 - datalabels in timeline chart
  • Revert PR #​4240

v3.49.0: 💎 Version 3.49.0

Compare Source

🐞 Bug fixes

v3.48.0: 💎 Version 3.48.0

Compare Source

🆕 Enhancements

  • Provide a "step before" version of the current "step after" line chart; Fixes #​4313
  • Use ShadowRoot getElementById() when in ShadowDOM; Thanks @​cyraid

🐞 Bug fixes

Thanks @​rosco54 for multiple y-axis scale fixes

v3.47.0: 💎 Version 3.47.0

Compare Source

🆕 Enhancements

  • Map multiple series to the same y-axis scales (in a multi-axes chart) - fixes #​4237

🐞 Bug fixes

  • Area chart gradient drawing glitch; fixes #​4271
  • Point annotation fix when y-axis is not present (in case of sparkline or hidden y-axis)
  • When chart is type 'bar', ensure reference to zero is maintained

Thanks @​rosco54 for y-axis scale improvements

v3.46.0: 💎 Version 3.46.0

Compare Source

🆕 Enhancements

🐞 Bug fixes

  • Fix #​4167 - shadow bug in multi-series chart
  • Fix #​4242 - allow labels with Invalid text
jsdom/jsdom (jsdom)

v26.0.0

Compare Source

Breaking change: canvas peer dependency requirement has been upgraded from v2 to v3. (sebastianwachter)

Other changes:

  • Added AbortSignal.any(). (jdbevan)
  • Added initial support for form-associated custom elements, in particular making them labelable and supporting the ElementInternals labels property. The form-associated callbacks are not yet supported. (hesxenon)
  • Updated whatwg-url, adding support for URL.parse().
  • Updated cssstyle and rrweb-cssom, to improve CSS parsing capabilities.
  • Updated nwsapi, improving CSS selector matching.
  • Updated parse5, fixing a bug around <noframes> elements and HTML entity decoding.
  • Fixed JSDOM.fromURL() to properly reject the returned promise if the server redirects to an invalid URL, instead of causing an uncaught exception.

v25.0.1

Compare Source

  • Updated dependencies, notably tough-cookie, which no longer prints a deprecation warning.

v25.0.0

Compare Source

This major release changes the prototype of a jsdom's EventTarget.prototype to point to the Object.prototype inside the jsdom, instead of pointing to the Node.js Object.prototype. Thus, the prototype chain of Window stays entirely within the jsdom, never crossing over into the Node.js realm.

This only occurs when runScripts is set to non-default values of "dangerously" or "outside-only", as with the default value, there is no separate Object.prototype inside the jsdom.

This will likely not impact many programs, but could cause some changes in instanceof behavior, and so out of an abundance of caution, we're releasing it as a new major version.

v24.1.3

Compare Source

  • Fixed calls to postMessage() that were done as a bare property (i.e., postMessage() instead of window.postMessage()).

v24.1.2

Compare Source

  • Fixed an issue with the in operator applied to EventTarget methods, e.g. 'addEventListener' in window, which only appeared in Node.js ≥22.5.0. (legendecas)
  • Fixed the events fired by blur(): it no longer fires focus and focusin on the Document, and blur and focusout no longer have their relatedTarget property set. (asamuzaK)

v24.1.1

Compare Source

  • Fixed selection methods to trigger the selectionchange event on the Document object. (piotr-oles)
openpgpjs/openpgpjs (openpgp)

v6.0.1

Compare Source

What's Changed

  • Fix ES imports for webpack: declare exports.browser entrypoint as higher priority than import
  • Fix openpgp.verify/decrypt with expectSigned: true and format: 'binary' (#​1805)
  • TS: fix generateKey (options.type) and PrivateKey.getDecryptionKeys() type declarations (#​1807)
  • Update hash algorithm preferences order by (#​1804)

Full Changelog: openpgpjs/openpgpjs@v6.0.0...v6.0.1

v6.0.0

Compare 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
  • The library is now declared as a module (type: module in 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.
  • Node.js:
    • Drop support for Node.js versions below 18 (OpenPGP.js v5 supported Node.js v14 and above).
    • Streaming: drop support for native Node Readable stream: require passing Node Web Streams (#​1716)
  • Web:
    • Require availability of the Web Crypto API's SubtleCrypto (insecure contexts are no longer supported, as SubtleCrypto is not available there)
    • Require availability of the Web Streams API, since it's now supported in all browsers (applications can load a polyfill if they need to support older browser versions: see README)
    • Require availability of native BigInts (not supported by e.g. Safari 13 and below, see full compatibility table)
    • Argon2 has been added as S2K algorithm (on all platforms). For performance reasons, the implementation relies on a WASM module, thus web apps might need to make changes to their CSP policy in order to use the feature. Alternatively, since the Argon2 WASM module is only loaded if needed, apps can manually reject password-encrypted messages and private keys which use Argon2 by checking e.g. SymEncryptedSessionKeyPacket.s2k?.type === 'argon2' or SecretKeyPacket|SecretSubkeyPacket.keyPacket.s2k?.type === 'argon2'.
Breaking API changes
  • Ensure primary key meets strength and algo requirements when encrypting/verifying/signing using subkeys (#​1719)
  • 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.getDecryptionKeys will now throw if no decryption key is found (#​1789). Previously, an empty array was returned. As a consequence of this change, some openpgp.decrypt errors will be more specific.
  • Refuse to use keys without key flags (see config.allowMissingKeyFlags below)
  • Randomize v4 and v5 signatures via custom notation (#​1737): while this notation solution is interoperable, it will reveal that the signature has been generated using OpenPGP.js, which may not be desirable in some cases. For this reason, the option config.nonDeterministicSignaturesViaNotation (defaulting to true) has been added to turn off the feature.
  • AEAD-encrypted v4 keys from OpenPGP.js v5 or older (namely keys generated without .v5Keys flag and encrypted with config.aeadProtect = true) cannot be decrypted by OpenPGP.js v6 (via decryptKey) out-of-the-box (see config.parseAEADEncryptedV4KeysAsLegacy below) (#​1672)
  • Parsing of v5 keys and v5 signatures now requires turning on the corresponding config flag (see config.enableParsingV5Entities below). 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
  • RFC 9580 has updated parts of the draft RFC 4880bis as implemented by OpenPGP.js v4 and v5. Related changes in v6 are:
    • Drop the config.v5Keys flag and corresponding key generation. The flag is replaced by .v6Keys, and results in a different key format.
    • The config.aeadProtect flag has a different effect than in v5:
    • Add config.parseAEADEncryptedV4KeysAsLegacy to allow decrypting AEAD-encrypted v4 keys from OpenPGP.js v5 or older (namely keys generated without .v5Keys flag and encrypted with config.aeadProtect = true) (#​1672).
    • Add config.enableParsingV5Entities to enable parsing support for v5 entities (https://github.com/openpgpjs/openpgpjs/pull/1774 , #​1779)
  • Add config.allowMissingKeyFlags to bypass the missing key flag check (see https://github.com/openpgpjs/openpgpjs/pull/1677)
  • Drop config.minBytesForWebCrypto, and always use WebCrypto if available, since there is no longer a performance overhead for small messages.
  • Rename EdDSA-related enums following the standardization of new key formats:
    • Drop enums.publicKey.eddsa in favour of enums.publicKey.eddsaLegacy
    • Rename string value of enums.curve.ed25519Legacy to 'ed25519Legacy' (was: 'ed25519')
    • Rename string value of enums.curve.curve25519Legacy to 'curve25519Legacy' (was: 'curve25519')
  • Rename config.useIndutnyElliptic to .useEllipticFallback, to reflect the change of underlying library.
  • Remove enums.symmetric.plaintext (internally unused)
  • Rename NIST curves to disambiguate the names with the Brainpool curves (#​1721).:
    • the identifiers enums.curve.p256, .p384, .p521 are now marked as @deprecated (to be dropped in the main release)
    • the new identifiers are, respectively: enums.curve.nistP256, .nistP384, .nistP521.
    • the corresponding values have been changed from 'p256','p384','p521' to 'nistP256', 'nistP384', 'nistP521' (these new values are expected by generateKey, for the options.curve argument).
  • Remove config.deflateLevel (#​1717)
  • Drop 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

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (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.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Author

renovate bot commented Jan 13, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"^6.0.0" from the root project
npm error   peer vite@"^5.0.0 || ^6.0.0" from @vitejs/[email protected]
npm error   node_modules/@vitejs/plugin-vue
npm error     dev @vitejs/plugin-vue@"^5.1.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from [email protected]
npm error node_modules/vite-plugin-node-polyfills
npm error   dev vite-plugin-node-polyfills@"^0.22.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vite
npm error   peer vite@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from [email protected]
npm error   node_modules/vite-plugin-node-polyfills
npm error     dev vite-plugin-node-polyfills@"^0.22.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-13T13_21_42_216Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-13T13_21_42_216Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-node-packages branch from 9987ae8 to c09819c Compare January 13, 2025 11:32
@renovate
chore: update node packages
dc053ee 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/major-node-packages branch from c09819c to dc053ee Compare January 13, 2025 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants