The automated release is failing 🚨 #143
Comments
🚨 The automated release from the
|
|
The last working deployment of https://travis-ci.com/saltstack-formulas/apache-formula/jobs/269371354#L260
The newest version was release a short time ago: https://www.npmjs.com/package/semantic-release
The proposed workaround for the short-term is to restrict to the last working version before |
|
Confirmed, using https://travis-ci.org/myii/test-travis-ci/jobs/628111852#L242
|
|
Final update, https://travis-ci.org/myii/test-travis-ci/jobs/628143100#L242
From all of the failing runs, it's seen that it is pulling https://travis-ci.com/saltstack-formulas/bind-formula/jobs/269513751#L266-L267
Therefore, the new workaround plan is to specify |
# [0.19.0](v0.18.4...v0.19.0) (2019-12-21) ### Bug Fixes * **release.config.js:** use full commit hash in commit link [skip ci] ([adcdbb1](adcdbb1)) ### Continuous Integration * **gemfile:** restrict `train` gem version until upstream fix [skip ci] ([b7b0d65](b7b0d65)) * **kitchen:** use `debian-10-master-py3` instead of `develop` [skip ci] ([c91fe2a](c91fe2a)) * **kitchen:** use `develop` image until `master` is ready (`amazonlinux`) [skip ci] ([5afc27e](5afc27e)) * **kitchen+travis:** upgrade matrix after `2019.2.2` release [skip ci] ([6ba1dd5](6ba1dd5)) * **travis:** apply changes from build config validation [skip ci] ([1838174](1838174)) * **travis:** opt-in to `dpl v2` to complete build config validation [skip ci] ([577ad6d](577ad6d)) * **travis:** quote pathspecs used with `git ls-files` [skip ci] ([88f9ff1](88f9ff1)) * **travis:** restrict `semantic-release` version until upstream fix ([5989bb9](5989bb9)) * **travis:** run `shellcheck` during lint job [skip ci] ([37c65de](37c65de)) * **travis:** update `salt-lint` config for `v0.0.10` [skip ci] ([4c6a882](4c6a882)) * **travis:** use `major.minor` for `semantic-release` version ([66c4d9f](66c4d9f)), closes [/github.com//issues/143#issuecomment-568197176](https://github.com//github.com/saltstack-formulas/bind-formula/issues/143/issues/issuecomment-568197176) * **travis:** use build config validation (beta) [skip ci] ([681c345](681c345)) * merge travis matrix, add `salt-lint` & `rubocop` to `lint` job ([7b23dbb](7b23dbb)) ### Documentation * **contributing:** remove to use org-level file instead [skip ci] ([9c11845](9c11845)) * **readme:** update link to `CONTRIBUTING` [skip ci] ([ab6ea39](ab6ea39)) ### Features * **map.jinja:** add Gentoo support ([7415a9b](7415a9b)) ### Performance Improvements * **travis:** improve `salt-lint` invocation [skip ci] ([b63490c](b63490c))
* saltstack-formulas/bind-formula#143 (comment) * https://travis-ci.com/saltstack-formulas/bind-formula/jobs/269513751#L266-L267 - `15.4.0` being used instead of newly release `15.14.0`
* saltstack-formulas/bind-formula#143 (comment) * https://travis-ci.com/saltstack-formulas/bind-formula/jobs/269513751#L266-L267 - `15.4.0` being used instead of newly released `15.14.0`
# [1.69.0](v1.68.0...v1.69.0) (2019-12-22) ### Features * **travis:** use `major.minor` for `semantic-release` version ([0f2c9d2](0f2c9d2)), closes [/github.com/saltstack-formulas/bind-formula/issues/143#issuecomment-568197176](https://github.com//github.com/saltstack-formulas/bind-formula/issues/143/issues/issuecomment-568197176) [/travis-ci.com/saltstack-formulas/bind-formula/jobs/269513751#L266-L267](https://github.com//travis-ci.com/saltstack-formulas/bind-formula/jobs/269513751/issues/L266-L267)
🚨 The automated release from the
masterbranch failed. 🚨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
masterbranch. 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.jsonfile.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.jsonfile.Good luck with your project ✨
Your semantic-release bot 📦🚀
The text was updated successfully, but these errors were encountered: