Update @elastic/fleet dependencies (main) #201196
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
![elastic-renovate-prod[bot]](https://avatars.githubusercontent.com/in/937301?s=60&v=4){kind=small}
elastic-renovate-prod
bot
added
backport:all-open
|
Pinging @elastic/fleet (Team:Fleet) |
elastic-renovate-prod
bot
force-pushed
the
renovate/main-@elasticfleet-dependencies
branch
from
0ab934c to
29913a3
Compare
elastic-renovate-prod
bot
force-pushed
the
renovate/main-@elasticfleet-dependencies
branch
from
29913a3 to
43fb1b7
Compare
|
/ci |
|
The integrations page doesn't seem to load: |
|
Seeing an error like this in local kibana logs: |
|
/ci |
1 similar comment
|
/ci |
Edited/Blocked NotificationRenovate 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. |
juliaElastic
reviewed
Dec 4, 2024
package.json
Outdated
| @@ -1207,7 +1207,7 @@ | |||
| "object-hash": "^1.3.1", | |||
| "object-path-immutable": "^3.1.1", | |||
| "openai": "^4.72.0", | |||
| "openpgp": "5.10.1", | |||
There was a problem hiding this comment.
it seems the licence check failed for this one
❌ /.buildkite/scripts/steps/checks/licenses.sh: 27s | 0s
| warn [quick-checks] --- Check Licenses
| (node:5147) [DEP0170] DeprecationWarning: The URL https://github.com:crypto-browserify/browserify-rsa.git is invalid. Future versions of Node.js will throw an error.
| (Use `node --trace-deprecation ...` to show where the warning was created)
| ERROR Non-conforming licenses:
| openpgp
| version: 6.0.1
| all licenses: LGPL-3.0+
| invalid licenses: LGPL-3.0+
| path: node_modules/openpgp
<br class="Apple-interchange-newline">
juliaElastic
force-pushed
the
renovate/main-@elasticfleet-dependencies
branch
from
1036d0d to
0985762
Compare
|
/ci |
💔 Build Failed
Failed CI StepsHistory
|
|
@juliaElastic I think the build issues are due to some of these packages being changed to ESM only, but I only quickly skimmed. Possibly need to restrict the version in |
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.
This PR contains the following updates:
^1.4.0->^1.4.44.0.2->5.0.4^1.4.3->^2.0.15.10.1->6.0.11.0.0->4.0.0Release Notes
gjtorikian/isBinaryFile (isbinaryfile)
v5.0.4Compare Source
v5.0.3Compare Source
v5.0.2Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
v4.0.10Compare Source
v4.0.9Compare Source
v4.0.8Compare Source
v4.0.6Compare Source
v4.0.5Compare Source
v4.0.4Compare Source
v4.0.3Compare Source
bvaughn/js-search (js-search)
v2.0.1Compare Source
README update. (No code changes.)
v2.0.0Compare Source
Added es modules support for bundlers via "module" field and for node via "exports" field.
Commonjs output is no longer provided. Entry point is UMD now.
UMD/ESM are bundled with rollup which reduced minified bundle size twice from 17432 to 7759 bytes!
Flow types are distributed with sources.
openpgpjs/openpgpjs (openpgp)
v6.0.1Compare Source
What's Changed
exports.browserentrypoint as higher priority thanimportopenpgp.verify/decryptwithexpectSigned: trueandformat: 'binary'(#1805)generateKey(options.type) andPrivateKey.getDecryptionKeys()type declarations (#1807)Full Changelog: openpgpjs/openpgpjs@v6.0.0...v6.0.1
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
v5.11.1Compare Source
What's Changed
Full Changelog: openpgpjs/openpgpjs@v5.11.0...v5.11.1
v5.11.0Compare Source
What's Changed
crypto-refresh: minor fixes and updates for X25519/Ed25519 (new format) (https://github.com/openpgpjs/openpgpjs/pull/1687)enums.publicKey.eddsaLegacy, set to replaceenums.publicKey.eddsain v6enums.curve.ed25519Legacyand.curve25519Legacy, set to replaceenums.curve.ed25519and.curve25519in v6VerifyOptions(https://github.com/openpgpjs/openpgpjs/pull/1644)Full Changelog: openpgpjs/openpgpjs@v5.10.2...v5.11.0
v5.10.2Compare Source
What's Changed
Full Changelog: openpgpjs/openpgpjs@v5.10.1...v5.10.2
remarkjs/remark-gfm (remark-gfm)
v4.0.0Compare Source
Change
b8cc334Update@types/mdast,unified, utilitiesmigrate: update too
9eb0f54Change to useexportsmigrate: don’t use private APIs
5715c93Change to require Node.js 16migrate: update too
Full Changelog: remarkjs/remark-gfm@3.0.1...4.0.0
v3.0.1Compare Source
97437dcAdd improved docsby @wooorm in https://github.com/remarkjs/remark-gfm/pull/25
Full Changelog: remarkjs/remark-gfm@3.0.0...3.0.1
v3.0.0Compare Source
890005eAdd support for GFM footnotes ✨(if you were using
remark-footnotesbefore, you should remove it!)(how footnotes are turned to HTML is done in
remark-rehype, please update that too)Full Changelog: remarkjs/remark-gfm@2.0.0...3.0.0
v2.0.0Compare Source
6c518d8Use ESM37d92acAdd JSDoc based types0846014Remove warning for remark 12Full Changelog: remarkjs/remark-gfm@1.0.0...2.0.0
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.
This PR has been generated by Renovate Bot.