Skip to content

History / Deleting Extensions

Revisions

  • Simplify the manual token INSERT now that version and type have defaults

    @netomi netomi committed Sep 4, 2026
  • 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>

    @netomi netomi committed Sep 3, 2026