ts-strict/eslint-config

This package provides sharable ESLint config with set of strict rules for TypeScript

eslint-config

This package provides sharable ESLint config with set of strict rules for TypeScript

Contributors ✨

Thanks goes to these wonderful people (emoji key):

Piotr Stępniewski 🚧 👀 💻 ⚠️

This project follows the all-contributors specification. Contributions of any kind welcome!

eslint-config's Issues

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 @types/tape to v5
• chore(deps): update dependency husky to v9
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency prettier-plugin-organize-imports to v3
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency typescript to v5
• chore(deps): update dependency ubuntu to v22
• fix(deps): update dependency eslint to v9
• 🔐 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 ts-node to v10
• chore(deps): update semantic-release monorepo (major) (@semantic-release/changelog, @semantic-release/git)
• fix(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)

Open

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

• chore(deps): update dependency snyk to v1.1064.0 [security]
• chore(deps): update dependency semantic-release to v19 [security]
• chore(deps): update actions/cache action to v4
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency @types/node to v20
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/release.yml

• actions/checkout v2
• actions/setup-node v1
• actions/cache v2
• ubuntu 20.04

npm

package.json

• @typescript-eslint/eslint-plugin ^3.1.0
• @typescript-eslint/parser ^3.1.0
• eslint ^7.2.0
• eslint-plugin-import ^2.21.1
• @commitlint/cli ^9.0.0
• @commitlint/config-conventional ^9.0.0
• @semantic-release/changelog ^5.0.1
• @semantic-release/git ^9.0.0
• @types/node ^14.0.11
• @types/tape ^4.13.0
• all-contributors-cli ^6.16.0
• husky ^4.2.5
• lint-staged ^10.2.9
• prettier ^2.0.5
• prettier-plugin-organize-imports ^1.0.4
• prettier-plugin-packagejson ^2.2.5
• rimraf ^3.0.2
• semantic-release ^17.0.8
• snyk ^1.339.2
• tape ^5.0.1
• ts-node ^8.10.2
• typescript ^3.9.5

---

• 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 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 📦🚀