gbicou/nuxt-image-directus

Directus provider for NuxtImage

nuxt-image-directus's Issues

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

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

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 fix 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 main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are 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.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency defu to v6.1.3
• chore(deps): update dependency vue to v3.3.9
• chore(deps): update dependency @nuxtjs/eslint-config-typescript to v12.1.0
• chore(deps): update dependency @types/node to v18.18.13
• chore(deps): update dependency eslint to v8.54.0
• chore(deps): update dependency eslint-config-prettier to v8.10.0
• chore(deps): update dependency semantic-release to v21.1.2
• chore(deps): update dependency typescript to v5.3.2
• chore(deps): update dependency ufo to v1.3.2
• fix(deps): update nuxtjs monorepo to v3.8.2 (@nuxt/kit, @nuxt/schema, @nuxt/test-utils, nuxt)
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @nuxt/image-edge to v1.0.0-testing
• chore(deps): update dependency @nuxt/module-builder to ^0.5.0
• chore(deps): update dependency vitest to ^0.34.0
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency @types/node to v20
• chore(deps): update dependency eslint-config-prettier to v9
• chore(deps): update dependency eslint-plugin-prettier to v5
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency semantic-release to v22
• chore(deps): update dependency unbuild to v2
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/release.yml

• actions/checkout v4
• pnpm/action-setup v2
• actions/setup-node v3

npm

package.json

• @nuxt/kit ^3.5.1
• @bicou/semantic-release ^1.0.1
• @nuxt/image-edge 1.0.0-28059208.2abef1b
• @nuxt/module-builder ^0.3.1
• @nuxt/schema ^3.5.1
• @nuxt/test-utils ^3.5.1
• @nuxtjs/eslint-config-typescript ^12.0.0
• @types/node ^18.16.14
• defu ^6.1.2
• eslint ^8.41.0
• eslint-config-prettier ^8.8.0
• eslint-plugin-prettier ^4.2.1
• nuxt ^3.5.1
• prettier ^2.8.8
• semantic-release ^21.0.2
• typescript ^5.0.4
• ufo ^1.1.2
• unbuild ^1.2.1
• vitest ^0.31.1
• vue ^3.3.4
• @nuxt/image-edge 1.0.0-28059208.2abef1b
• defu ^6.1.2
• ufo ^1.1.1
• vue ^3.3.4
• pnpm 8.11.0

playground/package.json

---

• Check this box to trigger a request for Renovate to run again on this repository

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

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

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 fix 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 main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are 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 for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization 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 📦🚀