Bump @xterm/addon-progress from 0.2.0-beta.24 to 0.2.0-beta.46 #3992
Conversation
dependabot
bot
added
dependencies
|
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/xterm/addon-progress-0.2.0-beta.46
branch
2 times, most recently
from
7dda91b to
9bc91f6
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/xterm/addon-progress-0.2.0-beta.46
branch
from
9bc91f6 to
978d653
Compare
![kiloconnect[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ No Issues Found
2 files reviewed | Confidence: 95% | Recommendation: Merge
Review Details
Files:
jetbrains/host/package.json- Dependency version bumppnpm-lock.yaml- Auto-generated lockfile updates
Summary:
This is a standard Dependabot dependency update bumping @xterm/addon-progress from 0.2.0-beta.24 to 0.2.0-beta.46. The lockfile changes are auto-generated and include:
- Updated peer dependency for
@xterm/xterm(beta.137 → beta.140) - Addition of
@swc/[email protected]to dependency chains - Various transitive dependency updates
Checked: Security, dependency compatibility, breaking changes
Note: The peer dependency change for @xterm/xterm should be verified to ensure compatibility with the existing @xterm/[email protected] in the project.
Bumps [@xterm/addon-progress](https://github.com/xtermjs/xterm.js) from 0.2.0-beta.24 to 0.2.0-beta.46. - [Release notes](https://github.com/xtermjs/xterm.js/releases) - [Commits](https://github.com/xtermjs/xterm.js/commits) --- updated-dependencies: - dependency-name: "@xterm/addon-progress" dependency-version: 0.2.0-beta.46 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/xterm/addon-progress-0.2.0-beta.46
branch
from
978d653 to
dbfd077
Compare
catrielmuller
deleted the
dependabot/npm_and_yarn/xterm/addon-progress-0.2.0-beta.46
branch
Bumps @xterm/addon-progress from 0.2.0-beta.24 to 0.2.0-beta.46.
Commits
Dependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)