Guidelines on Revoking Publisher Contributions

Revoking the Publisher Agreement

The Eclipse Foundation requires all extension publishers to sign the Publisher Agreement. When publishers request to revoke their agreements, they will no longer be able to publish extension, but this step also affects their previous contributions:

• The Publisher Agreement is marked as inactive in the Eclipse Foundation database. An inactive agreement does not grant any authority to publish extensions.
• The publisher's personal access tokens are marked as inactive in the open-vsx.org database.
• All extension versions published by the requesting publisher are marked as inactive. Inactive versions are neither accessible from the user interface nor through the API or CLI. If all versions of an extension are inactive, the whole extension is marked inactive and it becomes inaccessible.

Publishers who express the wish to revoke the Publisher Agreement can be pointed to this page to understand the consequences.

Signing a New Agreement

Publishers who revoked their agreements may choose to sign the Publisher Agreement again. When that happens, the previously inactivated extension versions are reactivated so they become accessible again. However, it is not possible to reactivate the personal access tokens, so the publisher will need to create new tokens in order to publish.

Deleting Inactive Extensions

It is not possible for anyone to publish an already published version of an extension, even if that version is currently inactive. An administrator can delete the inactive version to enable others to republish it.