Skip to content

Conversation

@amvanbaren
Copy link
Contributor

@amvanbaren amvanbaren commented Oct 16, 2025

@amvanbaren amvanbaren self-assigned this Oct 16, 2025
@amvanbaren amvanbaren force-pushed the publisher-remove-extension branch 2 times, most recently from ad9d120 to 6be48b3 Compare October 29, 2025 11:27
@amvanbaren amvanbaren marked this pull request as ready for review October 29, 2025 11:35
@netomi
Copy link
Contributor

netomi commented Nov 5, 2025

might also fix #58.

@kineticsquid
Copy link
Contributor

@chrisguindon @netomi FYI, here is the PR to allow a publisher to remove their own extensions.

@kineticsquid
Copy link
Contributor

@amvanbaren I'm good with this. @netomi @chrisguindon ?

@netomi
Copy link
Contributor

netomi commented Nov 17, 2025

I did test the PR locally, and I could successfully delete an extension.

The extension / versions is / are deleted from the database instead of marking them as inactive. I wonder if we want to allow users to explicitly remove entries from the db as this would make tracing of potentially malicious extension very hard.

Reviews for the deleted extensions are not touched, thus they still are marked as active in the database, though there is no corresponding extension anymore, violating referential integrity.

Other than that, the PR looks good to me.

@amvanbaren amvanbaren force-pushed the publisher-remove-extension branch from 6be48b3 to 3a6cc5e Compare November 19, 2025 15:20
@amvanbaren amvanbaren force-pushed the publisher-remove-extension branch from 3a6cc5e to a84764e Compare November 20, 2025 20:43
@amvanbaren amvanbaren merged commit 96245d3 into eclipse:master Nov 20, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ability for a publisher to remove an extension and/or extension versions Allow to unpublish extensions

3 participants