Repository navigation
chore: release VS Code preview 0.1.4 through verified CI - #990
Merged
Merged
Conversation
Refs #3488
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepare a new immutable 0.1.4 prerelease to deliver the reviewed catalog-verification documentation and exercise the corrected tag-driven CD pipeline from PR #989.
Only the package version, matching lockfile root versions and changelog change. Runtime code, dependencies, editor assets, native test assertions and publishing readiness stay unchanged. The new release must qualify one frozen VSIX on Linux, macOS and Windows before Microsoft OIDC publication and indexed-package readback.
Validation: 67 local Python tests and
git diff --checkpass. The read-only CI workflow from merged PR #989 ran against existing 0.1.3: Microsoft catalog/payload passed; Open VSX, Cursor and Windsurf correctly failed because 0.1.3 is absent. Their ownership/trusted-publisher gate remains unresolved and disabled; this release does not claim those catalogs have updated.Refs #3488 (publication tracking on Gitea).