Skip to content

chore(vscode): prep extension for Marketplace publish#28

Merged
SingleSourceStudios merged 1 commit intomainfrom
chore/vscode-publish-setup
Apr 18, 2026
Merged

chore(vscode): prep extension for Marketplace publish#28
SingleSourceStudios merged 1 commit intomainfrom
chore/vscode-publish-setup

Conversation

@SingleSourceStudios
Copy link
Copy Markdown
Collaborator

@SingleSourceStudios SingleSourceStudios commented Apr 18, 2026

Bumped @vscode/vsce to v3, added esbuild to deps, aligned publisher ID with Marketplace publisher 'singlesourceai'. First publish of v0.1.0 shipped.


Summary by cubic

Prepared the VS Code extension for Marketplace publish by setting the publisher to singlesourceai, adding an MIT LICENSE, and updating packaging to @vscode/vsce v3 with esbuild prepublish bundling.

  • Dependencies

    • Replaced vsce with @vscode/vsce ^3.2.0.
    • Added esbuild ^0.24.0 for prepublish bundling.
    • Bumped @types/node to ^22.0.0.
  • Refactors

    • Aligned metadata: set publisher to singlesourceai, updated repository.url, and added MIT LICENSE.
    • Bumped extension version to 0.1.1.

Written for commit 4c51991. Summary will update on new commits.

Summary by CodeRabbit

  • Chores
    • Updated VS Code extension publisher name for marketplace identification
    • Upgraded development dependencies to enhance build tooling and compatibility

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 18, 2026

📝 Walkthrough

Walkthrough

The VS Code extension's package.json was updated to reflect a publisher rebrand from singlesourcestudios to singlesourceai. Development dependencies were also updated: @types/node bumped to v22, vsce replaced with the scoped @vscode/vsce v3, and esbuild v0.24 was added.

Changes

Cohort / File(s) Summary
VS Code Extension Configuration
editors/vscode/package.json
Publisher rebrand to singlesourceai, updated @types/node to ^22.0.0, replaced vsce with @vscode/vsce ^3.2.0, and added esbuild ^0.24.0 as a new dependency.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 With paws that hop and edits swift,
A publisher's name we gently shift,
From studios old to sources bright,
Dependencies dance to latest flight,
New esbuild joins the toolchain's song! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description is detailed and informative, but significantly diverges from the required template structure with missing key sections. Reformat the description to follow the template: add a concise Summary section, include Linked issue, specify Spec impact checkboxes, and complete the Checklist section with test pass statuses.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the main purpose of the changes: preparing the VS Code extension for publishing to the Marketplace.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/vscode-publish-setup

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

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

@SingleSourceStudios SingleSourceStudios force-pushed the chore/vscode-publish-setup branch from f2d335d to e0d65fb Compare April 18, 2026 18:10
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
editors/vscode/package.json (1)

8-11: ⚠️ Potential issue | 🟠 Major

repository.url is stale and inconsistent with the rebrand.

The publisher was updated to singlesourceai, but repository.url still points to github.com/singlesourcestudios/logic-md. Per the PR metadata, the actual repo is SingularityAI-Dev/logic-md. The Marketplace listing surfaces this URL, so shipping v0.1.0 with a stale/incorrect repo link sends users to the wrong (or non-existent) repo. Worth correcting before the next publish — and double-check PUBLISH.md (line 93 references "publisher": "singlesourcestudios") for the same drift.

Proposed fix
 	"repository": {
 		"type": "git",
-		"url": "https://github.com/singlesourcestudios/logic-md"
+		"url": "https://github.com/SingularityAI-Dev/logic-md"
 	},
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@editors/vscode/package.json` around lines 8 - 11, Update the stale
repository.url value in package.json to the correct repository
"https://github.com/SingularityAI-Dev/logic-md" (replace the existing
singlesourcestudios URL) and ensure the package.json "publisher" field matches
the new publisher "singlesourceai"; also audit PUBLISH.md for the incorrect
publisher string ("singlesourcestudios") and update it to "singlesourceai" so
marketplace links and publish metadata are consistent.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@editors/vscode/package.json`:
- Line 62: The dependency version for "@types/node" in package.json is too new
for the extension host Node runtime declared by engines.vscode; either change
the "@types/node" entry from "^22.0.0" to a version that matches Node 16 (e.g.,
"^16") or update the engines.vscode field to a VS Code minimum that includes a
newer Node runtime (so types v22 are safe); adjust the "@types/node" value or
bump engines.vscode accordingly and run install to update lockfiles.

---

Outside diff comments:
In `@editors/vscode/package.json`:
- Around line 8-11: Update the stale repository.url value in package.json to the
correct repository "https://github.com/SingularityAI-Dev/logic-md" (replace the
existing singlesourcestudios URL) and ensure the package.json "publisher" field
matches the new publisher "singlesourceai"; also audit PUBLISH.md for the
incorrect publisher string ("singlesourcestudios") and update it to
"singlesourceai" so marketplace links and publish metadata are consistent.
🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: a37cf635-abc3-4bf9-b35d-2582d818354f

📥 Commits

Reviewing files that changed from the base of the PR and between c1422c7 and f2d335d.

⛔ Files ignored due to path filters (1)
  • editors/vscode/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • editors/vscode/package.json

Comment thread editors/vscode/package.json
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

@SingleSourceStudios SingleSourceStudios force-pushed the chore/vscode-publish-setup branch from e0d65fb to 39d9f2f Compare April 18, 2026 18:12
@SingleSourceStudios
Copy link
Copy Markdown
Collaborator Author

@types/node - Extension source uses no Node stdlib APIs, declarative language support only. Tracking type/engine alignment for v0.1.2.

@SingleSourceStudios SingleSourceStudios merged commit 8c83e18 into main Apr 18, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant