wfcd / warframe-patchlogs Goto Github PK

build failed https://github.com/WFCD/warframe-patchlogs/actions/runs/7872437989/job/21477633331

🚨 The automated release from the master branch 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 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:

• Usage documentation
• Frequently Asked Questions
• Support channels

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.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

E.g. Update 25 does not have any images linked in the parsed data.

[Mirror on Nexus]

The devDependency eslint was updated from 6.7.0 to 6.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

It seems that some patch logs refer to a warframe's abilities rather than the name, so we should look for those too. Reference

some patches are duping, don't do that!

heyho,

I noticed that there was an error in the code with #129.
Since this update, only the baseUrl is queried, but not the individual pages.

This probably happened because the code line
const html = await (await fetch(baseUrl)).text();
was replaced everywhere by the #fetch function, which does not take any parameters but always retrieves the baseUrl.
const html = await this.#fetch();

build/scraper.js L21-L33

  async getPageNumbers() {
+   const html = await this.#fetch();
-   const html = await (await fetch(baseUrl)).text();
    const $ = cheerio.load(html);

build/scraper.js L48-L50

  async scrape(url, bar) {
+   const html = await this.#fetch();
-   const html = await (await fetch(baseUrl)).text();
    const $ = cheerio.load(html);

build/scraper.js L97-L99

  async scrapePost(url, data) {
+   const html = await this.#fetch();
-   const html = await (await fetch(baseUrl)).text();
    const $ = cheerio.load(html);

Pull request comes

🚨 The automated release from the master branch 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 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:

• Usage documentation
• Frequently Asked Questions
• Support channels

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.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀