Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneeskeeb

Relationships

#1269 Pushing an extension after creating a public git repo that is the same as other previously pushed extensions doesn't update the "Verified public repository"

Opened by svendowideit · 7/19/2026· Shipped 7/19/2026

Problem Statement

I pushed a number of extensions before creating the github repo for them (but i'd git inited out of habit.) All the extensions are in the same repo, and where identifed as coming from one github repo that didn't yet exist. 2 days later, i made the repo and pushed to it, and updated the one extension that needed fixing. all the other extensions continue to indicate that the repo is unverified - which is both true, and false.

Proposed Solution

I'm hoping that it's possible to update the ×Verified public repository for all extensions via some kind of ... triggered workflow that re-runs whatever is triggered when the publish actually took place.

Alternatives Considered

Na - but I'm happy to be told it's not urgent, or that it would require extensions to be re-published due to the data-model

Additional Context

none

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 1 MOREIMPLEMENTATION+ 1 MORECONTRIBUTOR_NOTIFIED

Shipped

7/19/2026, 4:22:23 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
keeb assigned keeb7/19/2026, 3:35:02 AM
Editable. Press Enter to edit.

keeb commented 7/19/2026, 4:22:42 AM

Thanks @svendowideit for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.