Skip to content

fix(release): publish VS Code extension as stable by default #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MelbourneDeveloper merged 1 commit into from
May 7, 2026
Merged

fix(release): publish VS Code extension as stable by default #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ jobs:
run: npm publish --workspace=packages/cli --tag ${{ steps.derive.outputs.npm_tag }} --provenance --access public

- name: Package VSIX
run: npm run -w typediagram-vscode package -- --pre-release
run: npm run -w typediagram-vscode package

- name: Pack npm tarballs for release assets
run: |
Expand All @@ -88,7 +88,7 @@ jobs:
run: |
TAG="${GITHUB_REF#refs/tags/}"
if ! gh release view "$TAG" >/dev/null 2>&1; then
gh release create "$TAG" --title "$TAG" --generate-notes --prerelease
gh release create "$TAG" --title "$TAG" --generate-notes
fi
# Collect unique assets — `typediagram-*.tgz` overlaps `typediagram-core-*.tgz`,
# so globbing both would make `gh release upload` race against itself with
Expand Down
Loading