Version updated for bevry-actions/npm to version v1.1.7. This action is used across all versions by 117 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes We now scan npm’s stderr to identify error 409, as the status code is always 1. Workaround for https://github.com/npm/cli/issues/7109

Version updated for bevry-actions/npm to version v1.1.6. This action is used across all versions by 117 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes it’s 409 errors not 429 errors that are causing the problem, made the logic far more robust and helpful, in case more work needs to be done

Version updated for bevry-actions/npm to version v1.1.4. This action is used across all versions by 117 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes continue to try again after a random delay of up to 60 seconds when encountering 429 conflict errors

Version updated for bevry-actions/npm to version v1.1.3. This action is used across all versions by 115 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes prevent npm conflicts by random delay up to 60 secodns

Version updated for bevry-actions/surge to version v1.1.0. This action is used across all versions by 107 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes As the surge npm package has outdated dependencies, projects that depend on it, even as a devDependency are marked falsely as insecure. This change allows surge to be installed in and only in the GitHub Action, such that surge is not a direct dependency anymore, and thus dependers are not marked as insecure.

Version updated for bevry-actions/npm to version v1.1.2. This action is used across all versions by 108 repositories. Go to the GitHub Marketplace to find the latest changes. Release notes if publish fails, try again in 60s: this is now done if two publishes happen simultaneously (such as default branch and tag branch) then one will fail