Skip to content

Why are packages not available for use for a couple of minutes after publishing? #8909

@rrousselGit

Description

@rrousselGit

Hello!

This is related to pub publish. When we publish a package, the published version is seemingly unusable for somewhere between 5-10 minutes.

While not a huge inconvenience, this is quite the hassle for maintainers of multiple packages who depend on each-other. It's quite common that publishing a package involves updating another package. And having to wait at random a couple of minutes is a little bit frustrating.

Nothing that can't be solved with a tea break. But I'm pretty sure that this issue didn't exist a couple of years ago.

So: Could packages be accessible right after publish? Or is there a reason behind not allowing it quite yet?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions