Skip to content

Don't publish boa_wasm to npm if version exists #4065

@jasonwilliams

Description

@jasonwilliams

We sometimes need to re-publish the same release which means publishing the same version. Cargo will ignore publishing a crate if it already exists but npm still fails.

It would be nice to have npm not fail if the version was already uploaded to the registry

our workflow lives here:
https://github.com/boa-dev/boa/blob/main/.github/workflows/release.yml#L39-L70

I guess we would want a step that runs npm view @boa-dev/boa_wasm version then checks the value against the current version (from Cargo.toml) if they match exit the workflow without any errors

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-InternalChanges that don't modify execution behaviourE-EasyEasy difficulty problem

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions