angular / angular/dev-infra

Document unpublish options for a botched release

Ouverte
#746 0 commentaires 0 réactions 1 personne assignée Réclamée par @josephperrott Voir sur GitHub
domain: release automation
Langage dominant
JavaScript
Étoiles
77
Forks
83
Merge moyen
2 j 5 h
PR mergées (30 j)
37

Description

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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.