chore(deps): bump linkify-it and @vscode/vsce in /extension - #103
chore(deps): bump linkify-it and @vscode/vsce in /extension#103dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [linkify-it](https://github.com/markdown-it/linkify-it) to 5.0.2 and updates ancestor dependency [@vscode/vsce](https://github.com/Microsoft/vsce). These dependencies need to be updated together. Updates `linkify-it` from 3.0.3 to 5.0.2 - [Changelog](https://github.com/markdown-it/linkify-it/blob/master/CHANGELOG.md) - [Commits](markdown-it/linkify-it@3.0.3...5.0.2) Updates `@vscode/vsce` from 2.32.0 to 3.9.2 - [Release notes](https://github.com/Microsoft/vsce/releases) - [Commits](microsoft/vscode-vsce@v2.32.0...v3.9.2) --- updated-dependencies: - dependency-name: linkify-it dependency-version: 5.0.2 dependency-type: indirect - dependency-name: "@vscode/vsce" dependency-version: 3.9.2 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
WalkthroughUpdates the extension's ChangesPackaging toolchain
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 `@extension/package.json`:
- Line 142: Update the extension manifest’s engines block to declare Node.js
compatibility as >=20 by adding the node engine entry alongside the existing
engine declarations. Leave the existing engine requirements unchanged.
🪄 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: CHILL
Plan: Pro
Run ID: fd6328cf-1a0c-41fd-9e3b-aa5026e568a1
⛔ Files ignored due to path filters (1)
extension/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
extension/package.json
| "typescript": "^5.3.0", | ||
| "esbuild": "^0.28.1", | ||
| "@vscode/vsce": "^2.22.0" | ||
| "@vscode/vsce": "^3.9.2" |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
rg -n '"node"|setup-node|node-version|NODE_VERSION|engines' \
extension .github Dockerfile* 2>/dev/null || trueRepository: ankittroy-21/Gitphone
Length of output: 22845
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
printf '\n== extension/package.json ==\n'
sed -n '1,40p' extension/package.json
printf '\n== .github/workflows/ci.yml ==\n'
sed -n '60,80p' .github/workflows/ci.ymlRepository: ankittroy-21/Gitphone
Length of output: 1621
Declare Node 20 in the extension manifest
CI already targets Node 20, but extension/package.json doesn’t declare a Node engine. Add "node": ">=20" to the engines block so older local environments fail fast instead of breaking when @vscode/vsce runs.
🤖 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 `@extension/package.json` at line 142, Update the extension manifest’s engines
block to declare Node.js compatibility as >=20 by adding the node engine entry
alongside the existing engine declarations. Leave the existing engine
requirements unchanged.
Bumps linkify-it to 5.0.2 and updates ancestor dependency @vscode/vsce. These dependencies need to be updated together.
Updates
linkify-itfrom 3.0.3 to 5.0.2Changelog
Sourced from linkify-it's changelog.
Commits
50a0c915.0.2 releasedde3b885Update package hooks13effaaAdd package lock39d748dBump c800ce877Drop tlds depsecde823Update benchmark to mitata23c62cdRefactor demo / doc build and publishfd63f3bCI config updatef4ea5afdemo: update bootstrap & layout1454fb6lint: dim warningsUpdates
@vscode/vscefrom 2.32.0 to 3.9.2Release notes
Sourced from @vscode/vsce's releases.
... (truncated)
Commits
f7501f2fix: skip APIScan (#1283)7cd3244chore: bump CI to Node 22 and fix build (#1282)df1a68eBump theuuidtest fixture version to100.0.0(#1279)3a5786eMerge pull request #1278 from microsoft/dependabot/npm_and_yarn/tmp-0.2.64954e08Bump tmp from 0.2.4 to 0.2.654dce87Bump qs from 6.14.2 to 6.15.2 (#1277)86fc2d6Bump uuid and@azure/msal-node(#1276)4699582Run npm audit fix and update lockfile (#1274)e003a0aMerge pull request #1272 from microsoft/dependabot/npm_and_yarn/fast-uri-3.1.274ab7a9Bump fast-uri from 3.0.6 to 3.1.2Maintainer changes
This version was pushed to npm by microsoft1es, a new releaser for
@vscode/vscesince your current version.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 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