A green CI pipeline hid a broken package publish for three weeks

A developer discovered that a GitHub Actions workflow was reporting successful publishes for three weeks, even though the package was never actually available to users. The issue came to light only when a user flagged that the listed version appeared outdated. The root cause was that marketplaces can accept an upload and still delay or reject it after the CI job has already exited with a success code. The proposed fix involves adding a verification step at the end of the publish job that queries the public registry API and fails if the visible version does not match the intended release. This approach shifts validation from trusting the pipeline's own exit code to independently confirming what external users can actually see and install.