Skip to content

[INFRA] Create a workflow to unpublish a version of a npm package #18

@tbouffard

Description

@tbouffard

Is your feature request related to a problem? Please describe.
Sometimes we publish package by mistake. For instance, if we publish a release notes in the bpmn-visualization-js repository by mistake, a git tag is created and this triggers a worklfow that publish an erroneous version of the package on npm.
The unpublish must be done manually from a developer environment. This is error prone.

Describe the solution you'd like
Create a worklfow to do the npm unpublish of a single version of a package that can be launched with workflow_dispatch
Inputs

  • package name: default bpmn-visualization
  • version: required, no default
  • dry-run: default to true. This will force collaborators to update the value manually and will prevent running extra unpublish

Describe alternatives you've considered
Continue doing it manually. This is error prone and require npm login setup on developer machine that may not have right to unpublish versions of the package. As we have only 72 hours to unpublish after the publishing date, we need to be reactive and we don't want to depend on people with access right who may not be available at this time.

Additional context

Note: this issue was initially available at https://github.com/process-analytics/github-actions-playground/issues/133

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreBuild, CI/CD or repository tasks (issues/PR maintenance, environments, ...)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions