Repository navigation
docs: add Marketplace status and release verification - #94
Merged
Merged
Conversation
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
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.
What changed
Adds a dated Marketplace status and release-verification page, linked from the installation guide. It distinguishes the four Open VSX 3.2.0 packages examined in the historical audit from unavailable Microsoft-served packages and from release 3.8.1. It links the public status update, audit finding, scans, rebuild comparison and release materials, and asks readers to keep security protections enabled.
The page uses the existing site layout, with a manifest declaration and regenerated sitemap. No deployment configuration changes.
How it is verified
git diff --checkpasses.mktemp --suffix, unavailable on the local Mac; GitHub CI will run that check on Linux.mainat/; no external repository webhooks or PR preview deployment workflow were found. This PR does not publish the page. No merge or manual deployment is requested.