felixfbecker / abortable-rx Goto Github PK

Because this package only publishes/distributes ES6 modules, tooling that expects all node_modules/**/*.js files to be CommonJS modules will break. There are simple workarounds for this issue (see sourcegraph/sourcegraph#1456 (comment)), so this is not high priority.

(Related issue for lodash-es: facebook/create-react-app#5241 (comment))

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 chai to v5
• chore(deps): update dependency sinon to v17 (sinon, @types/sinon)
• chore(deps): update dependency ts-node to v10
• chore(deps): update dependency typescript to v5
• fix(deps): update dependency rxjs to v7
• 🔐 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 v17 [security]
• chore(deps): update dependency abort-controller to v3
• chore(deps): update dependency nyc to v15
• chore(deps): lock file maintenance

Open

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

• chore(deps): update dependency typedoc to ^0.25.0
• chore(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency @semantic-release/exec to v6
• chore(deps): update dependency @types/node to v20
• chore(deps): update dependency mocha to v10 (mocha, @types/mocha)
• chore(deps): update dependency prettier to v3
• 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

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

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL https://[email protected]/felixfbecker/abortable-rx.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀