Republish extension as universal

[thinksyncs]

Summary

• remove preview Marketplace metadata and publish as a normal universal extension
• add Marketplace release verification script for stable and daily workflows
• bump extension version to 0.1.12

Verification

• npm test
• npm run build
• npm run package:extension -- --out /tmp/workspace-guard.vsix
• npm run verify:marketplace-release -- --publisher ToppyMicroServices --name workspace-guard --version 0.1.11 --mode universal --timeout-seconds 5 --poll-seconds 1

[Copilot]

Pull request overview

This PR repackages the extension as a standard (non-preview) universal Marketplace extension and adds an automated Marketplace release verification step to the stable and daily publishing workflows.

Changes:

• Removed preview Marketplace metadata and bumped extension version to 0.1.12.
• Added a scripts/verify-marketplace-release.mjs script to poll Marketplace until a given version is visible and downloadable.
• Updated the release.yml and daily-release.yml workflows to run the new verification script after publishing.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
scripts/verify-marketplace-release.mjs	New CLI script that checks Marketplace version/targets and verifies the vspackage endpoint is reachable.
package.json	Removes preview metadata, bumps version, and wires the verification script into npm scripts.
package-lock.json	Updates lockfile version fields to match the new extension version.
.github/workflows/release.yml	Replaces inline Marketplace polling with the new verification script for stable releases.
.github/workflows/daily-release.yml	Adds Marketplace verification after publishing the daily pre-release.

Comments suppressed due to low confidence (1)

package.json:13

• verify-marketplace-release.mjs relies on the global fetch API, which requires Node 18+ (and some environments still default to older Node). Since package.json doesn’t currently declare a Node engine, consider adding an engines.node constraint (e.g., ">=18") or switching the script to an explicitly imported fetch implementation so local/CI runs fail fast with a clear requirement.

  "engines": {
    "vscode": "^1.110.0"
  },

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.