release
Release a new version of the couper-vscode extension to VS Code Marketplace and Open VSX Registry
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Release couper-vscode Extension
Release a new version of the Couper Configuration VS Code extension.
Context
- Current version: !
node -p "require('./package.json').version" - Recent tags: !
git tag --sort=-v:refname | head -5 - Unreleased changelog section: !
sed -n '/## \[Unreleased\]/,/^## \[v/p' CHANGELOG.md | head -30 - Git status: !
git status --short
Steps
-
Validate preconditions
- Ensure working tree is clean (no uncommitted changes)
- Ensure branch is
masterand up to date with remote (git pull --rebase) - Verify there are unreleased changes in CHANGELOG.md; abort if the Unreleased section is empty
-
Determine version
- If
$ARGUMENTSis provided, use that as the new version - Otherwise, show the unreleased changes and ask the user to choose: patch, minor, or major bump
- Validate the version is semver and greater than the current version
- If
-
Bump version in
package.json- Update the
"version"field to the new version
- Update the
-
Update
CHANGELOG.md- Replace the
[Unreleased]compare link to reference the new version tag - Add a new empty
[Unreleased]section above with compare link from new version to master - Move existing unreleased entries under the new version heading
- Follow the existing format in the file
- Replace the
-
Commit and push
- Stage
package.jsonandCHANGELOG.md - Commit with message:
release: <version> - Push to remote
- Stage
-
Tag and push tag
- Create annotated tag
v<version> - Push the tag to remote
- Create annotated tag
-
Create GitHub Release
- Use
gh release create v<version>with the changelog entries as release notes - Use the Added/Changed/Fixed/Removed sections from the changelog as the body
- Use
-
Verify
- Confirm the release workflow was triggered:
gh run list --limit 1 - Print the release URL and marketplace link for the user to monitor
- Confirm the release workflow was triggered:
Important
- Never force-push or amend commits
- If
git pushfails due to remote changes,git pull --rebasefirst - The CI workflow (
.github/workflows/release.yaml) handles publishing to both VS Code Marketplace and Open VSX Registry automatically on GitHub Release creation
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-03-11
- Index updated
- 2026-03-11
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!