chore(vscode): esbuild ^0.25.0 + dependabot @types/node guard

[SingleSourceStudios]

What

• Bump esbuild ^0.24.0 → ^0.25.0 in editors/vscode (resolves GHSA-67mh-4wv8-2f99 dev-server CORS bypass). Not exploitable in our usage — we only run esbuild as a bundler, never esbuild serve — but bump hygiene.
• Add dependabot.yml ignore rules for @types/node version-update:semver-major in both / and /editors/vscode. Per Align @types/node with VS Code extension host Node runtime #29, @types/node must trail engines.node, never lead it.
• Add /editors/vscode to Dependabot scan scope (previously unscanned — explains why PR chore(deps-dev): bump @types/node from 22.19.17 to 24.12.2 in the dev-dependencies group #30 surfaced from the root scan).
• VSCode extension → v0.1.3, published to Marketplace.

Why

Closes the remaining action items from the dependabot audit:

• PR chore(deps-dev): bump @types/node from 22.19.17 to 24.12.2 in the dev-dependencies group #30 (bumped @types/node to 24) is being closed — it's exactly the anti-pattern Align @types/node with VS Code extension host Node runtime #29 warns against.
• Going forward, dependabot will respect engines.node alignment automatically.

Test

• npm install in editors/vscode resolves esbuild 0.25.x
• npm run esbuild-base -- --minify bundles cleanly (1.9kb minified)
• vsce publish ships v0.1.3 with icon intact

Refs #29. Unblocks closing #30.

---

Summary by cubic

Bumped esbuild in editors/vscode to ^0.25.0 to address GHSA-67mh-4wv8-2f99 (we only use bundling, not esbuild serve). Published the VS Code extension as v0.1.3.

• Dependencies
  • Dependabot: ignore semver-major @types/node in / and /editors/vscode so types trail engines.node/VS Code host.
  • Dependabot: add /editors/vscode to weekly scans.

^{Written for commit d9afd25. Summary will update on new commits.}

[coderabbitai]

Warning

Rate limit exceeded

@SingleSourceStudios has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 21 minutes and 23 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 21 minutes and 23 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7ebbafc7-2c74-4e47-ba73-59acfe0dd8f7

📥 Commits

Reviewing files that changed from the base of the PR and between 6abf9a7 and d9afd25.

⛔ Files ignored due to path filters (1)

• editors/vscode/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• .github/dependabot.yml
• editors/vscode/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/vscode-v0.1.3-esbuild-bump

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 3 files