michaelhettmer / latex-toolkit Goto Github PK

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): replace dependency npm-run-all with npm-run-all2 5.0.0
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency eslint-config-prettier to v9
• chore(deps): update dependency eslint-plugin-prettier to v5
• chore(deps): update dependency husky to v9
• chore(deps): update dependency jest-junit to v16
• chore(deps): update dependency jest-mock-console to v2
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency nodemon to v3
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency typescript to v5
• chore(deps): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency semantic-release to v19 [security]

Open

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

• chore(deps): update dependency nodemon to v2.0.22
• chore(deps): update dependency eslint to v8.57.0
• chore(deps): update dependency jest-mock-console to v1.3.0
• chore(deps): update dependency lint-staged to v12.5.0
• chore(deps): update dependency prettier to v2.8.8
• chore(deps): update dependency typescript to v4.9.5
• chore(deps): update typescript-eslint monorepo to v5.62.0 (minor) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• chore(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update semantic-release monorepo (major) (@semantic-release/changelog, @semantic-release/git)
• 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 ts-jest to v27.1.5
• chore(deps): update dependency typescript to v4.6.4
• chore(deps): update dependency @commitlint/cli to v16.3.0
• chore(deps): update dependency @types/jest to v27.5.2
• chore(deps): update dependency eslint-plugin-prettier to v4.2.1
• chore(deps): update dependency jest-junit to v13.2.0

Detected dependencies

circleci

.circleci/config.yml

• circleci/node 17.2.0

gitlabci

templates/.gitlab-ci.yml

npm

package.json

• @commitlint/cli 16.2.4
• @commitlint/config-conventional 16.2.4
• @semantic-release/changelog 5.0.1
• @semantic-release/git 9.0.1
• @types/jest 27.4.1
• @typescript-eslint/eslint-plugin 5.15.0
• @typescript-eslint/parser 5.15.0
• commitlint-circle 1.0.0
• eslint 8.11.0
• eslint-config-prettier 7.2.0
• eslint-plugin-json 3.1.0
• eslint-plugin-prettier 4.0.0
• husky 7.0.4
• jest 27.5.1
• jest-junit 13.0.0
• jest-mock-console 1.2.3
• lint-staged 12.3.8
• nodemon 2.0.15
• npm-run-all 4.1.5
• prettier 2.5.1
• rimraf 3.0.2
• semantic-release 17.4.7
• ts-jest 27.1.3
• typescript 4.6.2

---

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

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

🚨 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.

---

No name for the package defined.

A name for the package must be created. Run through npm (npm run to use npm package name or define SEMANTIC_RELEASE_PACKAGE in the environment

---

Good luck with your project ✨

Your semantic-release bot 📦🚀