Skip to content

Update adm-zip (main)#219491

Closed
elastic-renovate-prod[bot] wants to merge 2 commits intomainfrom
renovate/main-adm-zip
Closed

Update adm-zip (main)#219491
elastic-renovate-prod[bot] wants to merge 2 commits intomainfrom
renovate/main-adm-zip

Conversation

@elastic-renovate-prod
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
@types/adm-zip (source) devDependencies patch ^0.5.0 -> ^0.5.7
adm-zip dependencies patch ^0.5.9 -> ^0.5.16

Release Notes

cthackers/adm-zip (adm-zip)

v0.5.16

Compare Source

What's Changed

New Contributors

Full Changelog: cthackers/adm-zip@v0.5.15...v0.5.16

v0.5.15

Compare Source

What's Changed

New Contributors

Full Changelog: cthackers/adm-zip@v0.5.14...v0.5.15

v0.5.14

Compare Source

Fixed an issue introduced on version 0.5.13 requiring a new mandatory parameter on the inflater on nodejs version >= 15

v0.5.13

Compare Source

  • Fixed extractAllToAsync callback @​5saviahv
  • Fixed issue with "toAsyncBuffer" where after that command all entries are gone @​5saviahv
  • Minor fixes (tests, typos etc) @​5saviahv
  • Added a an option to specificy the maximum expectedLength of the file to protect against zip bombs or limit memory usage @​undefined-moe
  • Add check for invalid large disk entries @​criyle

v0.5.12

Compare Source

Fixed extraction error

v0.5.11

Compare Source

  • Add support for Info-Zip password check spec for ZipCrypto @​lukemalcolm
  • Extraction of password protected zip entries @​Santa77
  • Fixed unnecessary scanning a local file headers (except in the case of corrupted archives) @​likev
  • Added GitHub actions @​kibertoad
  • Fixed cases when extra data was lost @​yfdyh000
  • Fixed throw empty error in extractAllToAsync on operation done @​Autokaka

v0.5.10

Compare Source


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.


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

This PR has been generated by Renovate Bot.

@elastic-renovate-prod elastic-renovate-prod bot added backport:all-open Backport to all branches that could still receive a release release_note:skip Skip the PR/issue when compiling release notes Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Apr 29, 2025
@elastic-renovate-prod elastic-renovate-prod bot requested a review from a team as a code owner April 29, 2025 07:35
@elastic-renovate-prod elastic-renovate-prod bot requested a review from a team April 29, 2025 07:35
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elastic-renovate-prod
Copy link
Contributor Author

Edited/Blocked Notification

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.

@azasypkin
Copy link
Contributor

Same as in #205550 (comment)

@azasypkin azasypkin closed this Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:all-open Backport to all branches that could still receive a release release_note:skip Skip the PR/issue when compiling release notes Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants