Skip to content

fix(vscode-release): create Open VSX namespace before first publish #13

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
morrieinmaas merged 1 commit into from
May 19, 2026
Merged

fix(vscode-release): create Open VSX namespace before first publish #13

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
8 changes: 8 additions & 0 deletions .github/workflows/vscode-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,14 @@ jobs:
echo "::error::VSX_TOKEN secret is not set"
exit 1
fi
# First-time-publish handling: ovsx requires the publisher
# namespace to exist before any publish. `create-namespace` is
# idempotent — exits non-zero if the namespace already exists
# (`409 Conflict`), which is fine for re-runs. We swallow that
# specific failure with `|| true` so subsequent releases keep
# working. Any other failure (auth, network) surfaces via the
# publish step that follows.
npx --yes ovsx create-namespace morriearty-zg -p "$OVSX_PAT" || true
npx --yes ovsx publish "zettelgeist-${{ steps.ver.outputs.version }}.vsix" -p "$OVSX_PAT"

- name: Publish to VS Code Marketplace (optional)
Expand Down
Loading