Skip to content

feat: automate VS Code Marketplace release#7

Merged
Lefix2 merged 2 commits intomainfrom
feat/marketplace-release-automation
May 1, 2026
Merged

feat: automate VS Code Marketplace release#7
Lefix2 merged 2 commits intomainfrom
feat/marketplace-release-automation

Conversation

@Lefix2
Copy link
Copy Markdown
Owner

@Lefix2 Lefix2 commented Apr 30, 2026

Summary

  • Add workflow_dispatch trigger with a publish toggle (default: true)
  • Add Publish to VS Code Marketplace step using vsce publish + VSCE_PAT secret
  • Marketplace publish and GitHub Release creation are tag-only; manual dispatch can run without publishing

Setup required

Add a VSCE_PAT secret to the repo (Settings → Secrets → Actions) with a Personal Access Token from the VS Code Marketplace publisher portal.

Release flow

# Tag a version → triggers full pipeline automatically
git tag v0.1.1 && git push origin v0.1.1

# Manual run (e.g. dry-run without publish)
# → Actions tab → Release → Run workflow → publish=false

Test plan

  • VSCE_PAT secret set in repo settings
  • Push a test tag (e.g. v0.1.1) → verify CI passes, VSIX uploaded to GitHub Release, extension published to Marketplace
  • Trigger workflow_dispatch with publish=false → verify only package step runs, no publish

🤖 Generated with Claude Code

TREFOU Felix and others added 2 commits April 30, 2026 20:03
Add workflow_dispatch trigger with publish toggle, and a dedicated
"Publish to VS Code Marketplace" step (vsce publish via VSCE_PAT secret).
Marketplace publish and GitHub Release creation only fire on version tags;
manual dispatch can package without publishing by setting publish=false.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add semantic-release + plugins (commit-analyzer, release-notes-generator,
  npm, git, github) — bumps package.json version, commits, tags, and creates
  GitHub Release automatically on push to main
- Add semantic-release.yml workflow (triggers on main push)
- Update release.yml: sync version from git tag before packaging so VSIX
  name matches the release (e.g. codeclimate-visualiser-1.2.3.vsix);
  upload VSIX to existing GitHub Release via gh CLI; add manual version input
- Add .releaserc.json config (no npm publish, VSIX upload deferred to release.yml)

Commit message convention → version bump:
  fix:  → patch (1.0.x)
  feat: → minor (1.x.0)
  BREAKING CHANGE: → major (x.0.0)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Lefix2 Lefix2 merged commit f3857d6 into main May 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant