Skip to content

ci: publish only to Open VSX and fix production docs deploy - #382

Merged
hongjr03 merged 1 commit into
masterfrom
ci/openvsx-and-docs-deploy
Nov 17, 2026
Merged

hongjr03 merged 1 commit into
masterfrom
ci/openvsx-and-docs-deploy

Conversation

@hongjr03

Copy link
Copy Markdown
Member

Problem

The 1.3.0 release could not finish its post-publish jobs:

  1. VS Code Marketplace publish failed with Access Denied: The Personal Access Token used has expired. (the VSCE_PAT secret expired), which also
    skipped Open VSX because it runs after the Marketplace step.
  2. Production docs deploy failed with
    Error: --include or --exclude does not support format containing dir info,
    so vide.pascal-lab.net still serves the previous docs.
  3. Both workflows are only reachable from the release workflow, so the failed
    steps cannot be retried for an already published tag.

Changes

  • VS Code Marketplace is manual from now on. Removed the vsce publish
    step, the VSCE_PAT requirement and the now-unused npm ci. Open VSX stays
    automated. Maintainers publish the Marketplace build with
    vsce publish --packagePath <vsix>.
  • Republish support. publish-vsix.yml now has a workflow_dispatch entry
    taking source-ref and run-id, so artifacts from an existing run can be
    published without cutting a new release.
  • Docs deploy fixed. ossutil 1.7 matches --include/--exclude against
    file names only: getFilter splits the pattern and rejects anything with a
    directory separator, which is why --exclude 'preview/*' failed outright.
    The step now syncs every production top-level entry of the build output
    individually, so --delete stays scoped to production paths and the
    preview/ and staging/ prefixes are never touched.
  • Docs redeploy entry point. publish-docs.yml now also accepts
    workflow_dispatch with a tag input, so docs for an already published
    release can be redeployed on their own.

Trade-off

With per-entry sync, a removed top-level build output would linger in the
bucket (nested paths are still deleted by --delete). This is called out in a
comment next to the step.

Verification

  • All edited workflows parse as YAML.
  • Reproduced the ossutil failure locally with the pinned 1.7.18 binary, and
    verified that the new per-entry sync/cp commands pass argument parsing
    (they only fail later at the dummy endpoint, as expected).
  • 1.3.0 can be completed after merge:
    • docs: dispatch Publish production docs with tag: v1.3.0;
    • Open VSX: dispatch Publish VSIX to Open VSX with source-ref: v1.3.0
      and run-id: 44035663359 (the 1.3.0 release run).

VS Code Marketplace publication is now manual: drop the vsce step and the
VSCE_PAT requirement, and keep Open VSX automated. Add a workflow_dispatch
entry point that republishes artifacts from an existing run so a failed
publish can be retried without cutting a new release.

Production docs could not deploy: ossutil 1.7 rejects --include/--exclude
patterns containing directory separators (getFilter splits the pattern and
fails), so 'preview/*' and 'staging/*' were invalid and the whole step errored
out. Sync every production top-level entry instead: --delete then stays scoped
to production paths and the preview/staging prefixes survive. Also expose the
docs deploy as workflow_dispatch(tag) to redeploy an existing tag.
@hongjr03
hongjr03 merged commit 9592808 into master Nov 17, 2026
9 checks passed
@hongjr03
hongjr03 deleted the ci/openvsx-and-docs-deploy branch November 17, 2026 07:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant