chore(deps): bump tar from 7.5.13 to 7.5.19#4314
Conversation
|
@trigger.dev/build
trigger.dev
@trigger.dev/core
@trigger.dev/python
@trigger.dev/react-hooks
@trigger.dev/redis-worker
@trigger.dev/rsc
@trigger.dev/schema-to-json
@trigger.dev/sdk
commit: |
f46c777 to
87c8cc0
Compare
Bumps [tar](https://github.com/isaacs/node-tar) from 7.5.13 to 7.5.19. - [Release notes](https://github.com/isaacs/node-tar/releases) - [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v7.5.13...v7.5.19) --- updated-dependencies: - dependency-name: tar dependency-version: 7.5.19 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
87c8cc0 to
c7a4039
Compare
| "strip-ansi": "^7.1.0", | ||
| "supports-color": "^10.0.0", | ||
| "tar": "^7.5.13", | ||
| "tar": "^7.5.19", |
There was a problem hiding this comment.
🟡 Dependency update to a published package ships without a release note
The published CLI package's dependency is updated (tar bumped to ^7.5.19 at packages/cli-v3/package.json:143) without adding the required changeset, so this change to a public package will not appear in the user-facing release notes.
Impact: The version bump merges without generating a changelog entry, breaking the repository's release-notes process for public package changes.
Missing changeset for public package change
Both CONTRIBUTING.md and AGENTS.md state that any change to a package under packages/* requires a changeset (pnpm run changeset:add). packages/cli-v3 is the published trigger.dev package. The PR only touches packages/cli-v3/package.json and pnpm-lock.yaml; no file was added under .changeset/ for this change.
Was this helpful? React with 👍 or 👎 to provide feedback.
Bumps tar from 7.5.13 to 7.5.19.
Commits
be440da7.5.192812e93add maxDecompressionRatio guard against explosive decompression9ecd4d27.5.189e78bf0refuse to let header size be less than 0e02a4e9pax: parse values according to known types9cbdb317.5.177a635c2terminate pax strings on nul bytescf213387.5.1621a8220do not apply PAX header fields to meta entries52632cfupdate project deps