crishellco / vue-hubble Goto Github PK

🚨 The automated release from the 3.x 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 3.x 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.

---

The release 3.5.5 on branch 3.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=3.5.4 <3.5.4 can be published from branch 3.x.

The following commits are responsible for the invalid release:

• Merge pull request #663 from crishellco/cm/3x (66114c7)
• fix: github url (17d83b9)
• Merge pull request #662 from crishellco/cm/3x (0ff2e0a)
• fix(docs): github url (3139883)
• fix(docs): 3x (78f58f9)
• Revert "Merge pull request #660 from crishellco/cm/fix-master" (b27c3d5)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 3.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

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

Datasource	Name	Replacement PR?
npm	eslint-loader

Open

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

• chore(deps): update dependency @crishellco/eslint-plugin to v1.3.1
• chore(deps): update dependency @form8ion/remark-lint-preset to v5.0.9
• chore(deps): update dependency vite to v5.3.3
• chore(deps): update dependency vue to v3.4.31
• chore(deps): update dependency eslint-plugin-vue to v9.27.0
• chore(deps): update codecov/codecov-action action to v4
• chore(deps): update dependency semantic-release to v24
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency @form8ion/remark-lint-preset to v6
• chore(deps): update dependency eslint-plugin-prettier-vue to v5
• chore(deps): update dependency jest to v29
• chore(deps): update dependency node to v20
• chore(deps): update dependency remark-cli to v12

Detected dependencies

github-actions

.github/workflows/node-ci.yml

• actions/checkout v4
• actions/setup-node v4
• codecov/codecov-action v3

npm

demo/package.json

• vue ^3
• @vue/cli-service 5.0.8

docs/package.json

• vuepress-plugin-dehydrate ^1.1.5
• cross-env ^7.0.3
• vuepress 1.9.10

package.json

• @babel/eslint-parser 7.24.7
• @commitlint/cli 19.3.0
• @crishellco/eslint-plugin ^1.3.0
• @form8ion/commitlint-config 1.0.76
• @form8ion/remark-lint-preset 5.0.1
• @vue/eslint-config-prettier 9.0.0
• @vue/test-utils ^2.0.0
• babel-core 6.26.3
• babel-jest 29.7.0
• core-js 3.37.1
• cross-env 7.0.3
• cz-conventional-changelog 3.3.0
• eslint 9.6.0
• eslint-config-prettier 9.1.0
• eslint-loader 4.0.2
• eslint-plugin-jest 28.6.0
• eslint-plugin-jest-formatting ^3.1.0
• eslint-plugin-nuxt ^4.0.0
• eslint-plugin-prettier 5.1.3
• eslint-plugin-prettier-vue 4.2.0
• eslint-plugin-sort-keys-fix ^1.1.2
• eslint-plugin-unused-imports ^4.0.0
• eslint-plugin-vue 9.26.0
• husky 9.0.11
• jest 27.5.1
• npm-run-all2 6.2.0
• poi 12.10.3
• prettier 3.3.2
• regenerator-runtime 0.14.1
• remark-cli 11.0.0
• remark-toc 9.0.0
• rimraf 5.0.7
• semantic-release 22.0.12
• vite 5.3.2
• vue ^3.0.0
• vue-html-loader 1.2.4
• vue-jest 5.0.0-alpha.10
• vue-loader 17.4.2
• vue-style-loader 4.1.3

nvm

.nvmrc

• node 18

demo/.nvmrc

• node 18

docs/.nvmrc

• node 18

---

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

🚨 The automated release from the 3.x 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 3.x 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.

---

The release 3.5.3 on branch 3.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=3.5.2 <3.5.3 can be published from branch 3.x.

The following commits are responsible for the invalid release:

• Merge pull request #659 from crishellco/cm/maint-test (f259e6f)
• fix(docs): urls (7f00c14)
• fix(docs): github link (6e07637)
• fix(docs): 3.x maintenance branch (458c871)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 3.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀