skrtheboss / ts-async-semaphore Goto Github PK

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

Describe the bug
Installing ts-async-semaphore fails on the husky post-install step with husky 7.0.4 where there is a .git folder in the main project directory.

See issue for husky: typicode/husky#851

To Reproduce
Attempt to install ts-async-sempahore using

'npm install ts-async-semaphore'

when there is a .git folder in the main project directory. Husky appears to get tripped up looking from the primary .git folder.

Expected behavior
Successful install

Additional context
Perhaps I am missing something but I have been using ts-async-semaphore without an associated git repo for my project (yet). When I went to add some automated testing with jest and tried to use the jest watch capability, it complained about there not being a .git folder - so I used 'git init' to create a git context. I ran into a different problem, so I blew away the node_modules folder and did a full install and that is when this problem bubbled up. I am working around it for now by having no .git folder in my project and using the --watchAll option with jest. I believe the moment I put my project into git, this issue will re-appear.

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 jest monorepo (@types/jest, jest)
• chore(deps): update dependency eslint to ^8.56.0
• chore(deps): update dependency eslint-config-prettier to ^8.10.0
• chore(deps): update commitlint monorepo to v18 (major) (@commitlint/cli, @commitlint/config-conventional)
• 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 node.js to v20 (node, @types/node)
• chore(deps): update typescript-eslint monorepo to v6 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• 🔐 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 ts-jest to ^29.1.1
• chore(deps): update commitlint monorepo to ^17.8.1 (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency typedoc to ^0.25.7
• chore(deps): update dependency typescript to ~4.9.5
• chore(deps): update node.js to >=14.21.3 (node, @types/node)
• chore(deps): update semantic-release monorepo (@semantic-release/github, @semantic-release/npm)
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency typescript to v5
• chore(deps): update node.js to v17
• chore(deps): update semantic-release monorepo (major) (@semantic-release/commit-analyzer, @semantic-release/github, @semantic-release/npm, @semantic-release/release-notes-generator, semantic-release)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

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