angular / angular/dev-infra

Document unpublish options for a botched release

Offen
#746 0 Kommentare 0 Reaktionen 1 zugewiesene Person Beansprucht von @josephperrott Auf GitHub ansehen
domain: release automation
Vorherrschende Sprache
JavaScript
Sterne
77
Forks
83
Ø Merge
2 T. 5 Std.
Gemergte PRs (30 T.)
37

Beschreibung

Action item from [requiem/doc/postmortem475066](http://requiem/doc/postmortem475066).

In the `14.1.0-rc.0` tooling release, the process failed part way through leaving it in an inconsistent state. We considered unpublishing the packages on NPM that were released, but weren't fully sure of the implications and restrictions to doing so and decided to abandon the release instead and push new `14.1.0-rc.x` versions instead.

We should figure out what options are actually available for unpublishing, their implications and restrictions, and have a playbook entry in a caretaker doc about when and where unpublishing can be the right solution to a given problem. Alternatively we can decide that unpublishing is never a good idea and we should always just abandon a release and bump a patch, but that should be documented as well.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.