Skip to content

Packages should not be published if any of their dependencies fail to publish #3045

@hbmartin

Description

@hbmartin

What versions are you using? (if relevant)

No response

Describe the Bug

Currently the build system allows packages to be published even when their dependencies fail to publish. This leads to breaking issues such as #3041
The release script and CI workflow should prevent this from occurring by:

  1. Publishing packages in topological order and
  2. "failing fast" and aborting publishing at the first failure.

What is affected (leave empty if unsure)

@react-email/components package

Link to the code that reproduces this issue

https://github.com/resend/react-email/actions/runs/22954267200/job/66626623383

To Reproduce

https://github.com/resend/react-email/actions/runs/22954267200/job/66626623383

Expected Behavior

release script and CI workflow prevents broken npm published state

What's your node version? (if relevant)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions