Skip to content

Update GitHub Packages reserved names and versions section #122

Closed
@rachmari

Description

@rachmari

Content strategy plan

In https://help.github.com/packages/publishing-and-managing-packages/deleting-a-package#reserved-package-versions-and-names we say that:

To prevent confusion and build problems, GitHub permanently reserves a package's name and version number. Even if an entire package is deleted, you cannot reuse the deleted package name in any repository owned by the same account.

However, this behavior was modified recently. Now if all versions of a private package are deleted, the user can re-create the package with any version number they want. When all versions of a package have been deleted, republishing over those deleted versions (i.e. publishing a package with the same name and version) should be the same as publishing a new package for the first time.

Content plan

The existing docs are still true for public packages, but we'll want to update the content to note the new behavior for private packages.

Audience

Maintainers of GitHub Packages.

Content to update

We'll want to update https://help.github.com/packages/publishing-and-managing-packages/deleting-a-package#reserved-package-versions-and-names to note the new behavior for private packages.

Questions

If you have any questions after writing a plan, ask them here!

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamengineeringWill involve Docs EngineeringpackagesThis issue or pull request should be reviewed by the docs packages team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions