There was an error while loading. Please reload this page.
Add Deleting Extensions page Requested in eclipse-openvsx/openvsx#1620: there was no documentation for removing extensions or individual versions, so it meant reading the codebase. The recipe shared on that issue predates 'ovsx unpublish' and the token-hashing rework and no longer works as written. Covers the routes in order of effort - the web UI, 'ovsx unpublish', the plain delete endpoint the CLI calls, and the admin API for extensions you do not own - plus delete vs. purge, which was undocumented: delete keeps the version number permanently reserved so content can never be republished under a version somebody already installed, purge frees it. For a private registry deployed without a login provider, the manual SQL to bootstrap the first user and token is corrected: version and type are NOT NULL with no default since V1_72, version = 0 means the value is still plaintext and is hashed in place on first use (so no restart is needed), and ids should come from the sequences. Verified against a schema migrated to v1.73. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Rename the token lifetime setting to ovsx.trusted-publishing.token-expiration It moved out of the access-token namespace, and it must now be positive: issued publishing tokens always expire. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Document the active-version requirement and automatic deletion Trusted publishing needs the extension to have an active version, not only at registration: every token exchange looks it up among the active ones, so deleting all versions makes a registration stop working while still being listed. Also record the two cases where the registry deletes a registration by itself - its author losing namespace ownership, and the extension being purged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Add Trusted Publishing page Covers registering a trusted publisher, publishing from GitHub Actions and GitLab CI, what the registry verifies and matches, the properties of the issued token, the security model, and the server configuration for operators. Linked from Home. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Add Registry Changes Feed page documenting /api/-/version-changes
add new caching properties for 0.34.2
Updated Deploying Open VSX (markdown)
Add configuration options for access token expiry
Updated Publishing Extensions (markdown)
Created Extension Scanning (markdown)
Updated Home (markdown)
Updated Using Open VSX in VS Code (markdown)
Add configuration options for resourceUrlTemplate and extensionUrlTemplate
Add configuration options for logs download jobs
Add configuration options for AWS logs
Add configuration option ovsx.publishing.max-content-size
Document extensionquery caching config properties
Document `ovsx.storage.aws.*` configuration properties
Document `ovsx.storage.migration.enabled`
Document `ovsx.mail.*` properties
Document additional `ovsx.caching` properties
Document `ovsx.eclipse.publisher-agreement.allowed-versions`
Document `ovsx.token-prefix` application property
Document `ovsx.caching.*` application properties
Document `ovsx.migrations.once-per-version`
Document valid namespace name