This document outlines the automated release process for the Bruin VS Code extension.
The release process is now fully automated. Simply run one command based on the type of changes:
- Must be on
mainbranch - No uncommitted changes
- Git repository must have at least one existing tag
The CHANGELOG.md and README.md should be updated manually when significant changes are made. The release process doesn't automatically update the changelog and README to give maintainers full control over release notes.
npm run tag:patchnpm run tag:minornpm run tag:major- Version Calculation: Script automatically calculates the next version based on the latest git tag
- Confirmation: Shows current version → new version and asks for confirmation
- Tag Creation: Creates the new git tag locally
- Tag Push: Pushes the tag to GitHub
- GitHub Actions: Automatically triggers the release workflow which:
- Updates package.json version to match the tag
- Builds the extension
- Publishes to VS Code Marketplace and Open VSX
If you need to create tags manually:
# Get current version
git describe --tags --abbrev=0
# Create new tag
git tag v1.2.3
# Push tag
git push origin v1.2.3Use semantic versioning: v0.54.3 (major.minor.patch)
- "No tags found": If this is the first release, create an initial tag:
git tag v0.1.0 - Permission denied: Ensure you have push access to the repository
- GitHub Actions failing: Check that
VSCE_PATandOVSX_PATsecrets are configured
The following secrets must be configured in the GitHub repository:
VSCE_PAT: Personal Access Token for VS Code MarketplaceOVSX_PAT: Personal Access Token for Open VSX Registry