build(deps): bump adm-zip from 0.5.16 to 0.6.0#21419
Conversation
Bumps [adm-zip](https://github.com/cthackers/adm-zip) from 0.5.16 to 0.6.0. - [Release notes](https://github.com/cthackers/adm-zip/releases) - [Changelog](https://github.com/cthackers/adm-zip/blob/master/history.md) - [Commits](cthackers/adm-zip@v0.5.16...v0.6.0) --- updated-dependencies: - dependency-name: adm-zip dependency-version: 0.6.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified. |
|
Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:
|
📝 WalkthroughWalkthroughThe AWS component package manifest updates the ChangesAWS dependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@components/aws/package.json`:
- Line 35: Increase the version field in components/aws/package.json by at least
a minor semver segment to accompany the adm-zip dependency update, keeping the
AWS component’s package version on its independent release track.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 9b726150-dd51-4941-8574-908e481874be
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
components/aws/package.json
| "@pipedream/helper_functions": "^0.3.6", | ||
| "@pipedream/platform": "^3.2.5", | ||
| "adm-zip": "^0.5.10", | ||
| "adm-zip": "^0.6.0", |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Bump the AWS package version for this dependency change.
The adm-zip update is a minor-semver change, but the supplied diff does not show a corresponding version bump in components/aws/package.json. Increase it by at least a minor segment.
As per coding guidelines, **/package.json versions must be bumped by the same or greater semantic-version segment whenever an app component changes. Based on learnings, component package versions are independent tracks, but the relevant app package version still must be bumped.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/aws/package.json` at line 35, Increase the version field in
components/aws/package.json by at least a minor semver segment to accompany the
adm-zip dependency update, keeping the AWS component’s package version on its
independent release track.
Sources: Coding guidelines, Learnings
Bumps adm-zip from 0.5.16 to 0.6.0.
Release notes
Sourced from adm-zip's releases.
Changelog
Sourced from adm-zip's changelog.
... (truncated)
Commits
2b4d840updated minimum node engine version to >= 14dc57f0fHardened entry-name lookup, fixed test(), and sped up entry sortingf81806aMade utimes best-effort so it can't abort extraction (#379)ab04324Fixed extractEntryTo flattening subdirectories (#306)8a5d9baFixed empty name for directory entries (#466)3e72790Fixed uncaught crash in writeFileToAsync on write failure (#470, #459, #402)651ae4cAdded typescript typese72021dFixed infinite recursion on symlink loops in addLocalFolder (#541)8f3176bFixed directory permissions on linux4d2c8f9Fixed error introduced with zip descriptor checksDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Summary by CodeRabbit