Can't claim package - bb551bbb-3cb6-49ac-b703-6f204073ad15 - multionlabs/caddy-rolling-deployment - Site Feedback - Caddy Community = 40rem)" rel="stylesheet" data-target="chat_desktop" /> = 40rem)" rel="stylesheet" data-target="discourse-reactions_desktop" /> = 40rem)" rel="stylesheet" data-target="poll_desktop" /> = 40rem)" rel="stylesheet" data-target="desktop_theme" data-theme-id="1" data-theme-name="caddy custom"/> Can't claim package - bb551bbb-3cb6-49ac-b703-6f204073ad15 - multionlabs/caddy-rolling-deployment Site Feedback maxskorr (Max) July 25, 2026, 10:37pm 1 Hi — I’m having trouble claiming a package. About 40 minutes earlier I successfully claimed the same Caddy module ID under a different import path (monorepo layout). I’ve since moved the plugin to its own repository and I’m trying to claim: GitHub - MultionLabs/caddy-rolling-deployment: Caddy module to trigger rolling deployments of your workloads (e.g., from CI/CD). Minimal downtime, automatic rollbacks on failure · GitHub (version v0.9.0) That fails with: Sorry, something went wrong: unable to scan modules in package GitHub - MultionLabs/caddy-rolling-deployment: Caddy module to trigger rolling deployments of your workloads (e.g., from CI/CD). Minimal downtime, automatic rollbacks on failure · GitHub Please include this error ID if reporting: bb551bbb-3cb6-49ac-b703-6f204073ad15 Yet another Caddy WAF released :) matt (Matt Holt) August 5, 2026, 2:12pm 2 Ah, it’s because the same module ID is already registered. You’ll just have to delete it from your account and then you can register it at the new path. maxskorr (Max) August 6, 2026, 12:40pm 3 @matt thanks for your reply! I removed it from the account before trying to claim this module ID under a different path & since then I was unable to register this module ID under the new package import path, e.g. image2256×1176 143 KB (I’ve got no registered modules at all under my acc). There seems to be some mechanism that prevents freshly-freed module IDs from being registered again under a different package import path (to prevent module ID squatting?) Now wondering if I can do anything about it without having to change the module ID (e.g., if it’s a temporary restriction, I am ok to wait) matt (Matt Holt) August 6, 2026, 3:37pm 4 Hmm, might be a bug. I have started a rewrite of our plugin database and backend, so I am hoping to address it with that… I don’t think you should have to change your module ID. I’ll try to accelerate the backend rewrite. I might employ some LLM assistance to make it go faster.