Extension Versioning

First release: Start at 0.1.0, not 1.0.0. Reserve 1.0.0 for "production stable".

Version Bump Workflow

# From extension folder

# Check current version
cat package.json | Select-String '"version"'

# Bump patch (0.1.0 → 0.1.1)
npm version patch --no-git-tag-version

# Bump minor (0.1.1 → 0.2.0)
npm version minor --no-git-tag-version

# Or manually edit package.json version field, then:
npm run compile

--no-git-tag-version: Prevents npm version from auto-creating a git tag. We create tags manually or via CI.

CHANGELOG.md Format

Follow Keep a Changelog strictly.

# Changelog

All notable changes to Hook Studio are documented here.
Format: [Keep a Changelog](https://keepachangelog.com)

## [Unreleased]

## [0.2.0] - 2026-03-01
### Added
- Runner tab: execute hooks directly from the GUI
- Log tab: real-time output streaming

### Fixed
- Panel did not restore after VS Code restart (#12)

### Changed
- Renamed command `hookStudio.show` to `hookStudio.open` for consistency

## [0.1.0] - 2026-02-20
### Added
- Initial release
- 3-tab webview: Editor, Runner, Log
- JSON schema validation for hooks.json
- Syntax highlighting in Editor tab

[Unreleased]: https://github.com/fabioc/vs-extensions/compare/v0.2.0...HEAD
[0.2.0]: https://github.com/fabioc/vs-extensions/compare/v0.1.0...v0.2.0
[0.1.0]: https://github.com/fabioc/vs-extensions/releases/tag/v0.1.0

Rules:

• [Unreleased] section always present at top
• Move unreleased entries to a versioned section on publish
• Subsections: Added, Changed, Deprecated, Removed, Fixed, Security
• Entries are user-facing (not commit messages)

Release Cadence Recommendation

Do not micro-release (0.1.0 → 0.1.1 → 0.1.2 in one day). Batch fixes into minor releases unless it's a critical bug.

Version Sync Script (All Extensions)

# Check all versions
Get-ChildItem -Path "extensions" -Recurse -Filter "package.json" |
    Where-Object { $_.DirectoryName -notmatch "node_modules" } |
    ForEach-Object {
        $pkg = Get-Content $_.FullName | ConvertFrom-Json
        Write-Host "$($pkg.name): $($pkg.version)"
    }

VS Code Engine Version Strategy

Lock engines.vscode to the minimum version that supports your features:

Rule: Use ^1.109.0 for all extensions in this repo, since we target first-mover window on 1.109 features.

Version in Code

Access your own version at runtime:

const ext = vscode.extensions.getExtension('fabioc-aloha.hook-studio');
const version = ext?.packageJSON.version as string ?? 'unknown';
outputChannel.appendLine(`Hook Studio v${version} activated`);

Git Tagging Convention

After publish:

git tag -a "hook-studio/v0.1.0" -m "Hook Studio v0.1.0 — initial release"
git push origin "hook-studio/v0.1.0"

Format: {extension-name}/v{version} — allows multiple extension tags in the same monorepo without collision.