saltstack-formulas / bind-formula

http://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html
Other
29 stars 118 forks source link

The automated release is failing 🚨 #143

Closed saltstack-formulas-travis closed 4 years ago

saltstack-formulas-travis commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.


Good luck with your project ✨

Your semantic-release bot :package::rocket:

saltstack-formulas-travis commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.


Good luck with your project ✨

Your semantic-release bot :package::rocket:

myii commented 4 years ago

The last working deployment of semantic-release:

https://travis-ci.com/saltstack-formulas/apache-formula/jobs/269371354#L260

[5:46:21 PM] [semantic-release] › ℹ Running semantic-release version 15.13.31

The newest version was release a short time ago:

https://www.npmjs.com/package/semantic-release

15.14.0 ... 11 hours ago

The proposed workaround for the short-term is to restrict to the last working version before 15.14.0, either 15.13.31 or 15.13.32. Then to tackle the problem at hand, including submitting an upstream report.

myii commented 4 years ago

Confirmed, using 15.13 works fine:

https://travis-ci.org/myii/test-travis-ci/jobs/628111852#L242

[2:57:16 PM] [semantic-release] › ℹ Running semantic-release version 15.13.32

myii commented 4 years ago

Final update, 15.14 actually works fine if given specifically:

https://travis-ci.org/myii/test-travis-ci/jobs/628143100#L242

[5:11:54 PM] [semantic-release] › ℹ Running semantic-release version 15.14.0

From all of the failing runs, it's seen that it is pulling 15.4.0 instead of 15.14.0.

https://travis-ci.com/saltstack-formulas/bind-formula/jobs/269513751#L266-L267

Using possibly outdated prebuilt list from Sat Nov 02 2019 [Semantic release]: Running semantic-release version 15.4.0


Therefore, the new workaround plan is to specify 15.14 in .travis.yml.