pliancy / duo-sdk Goto Github PK

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

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Fallback to renovate.json file as a preset is deprecated, please use a default.json file instead.

Open

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

• chore(deps): update all non-major dependencies (@types/node, node, npm-run-all2, rimraf, ts-jest, tslib, typescript, yarn)
• fix(deps): update dependency axios to v1.7.2
• chore(deps): update dependency npm-run-all2 to v6
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/push.yml

• actions/checkout v4
• actions/setup-node v4

.github/workflows/release.yml

• actions/checkout v4
• actions/setup-node v4
• stefanzweifel/git-auto-commit-action v5

npm

package.json

• axios 1.6.7
• tslib 2.6.2
• @digitalroute/cz-conventional-changelog-for-jira 8.0.1
• @pliancy/eslint-config-ts 1.1.1
• @pliancy/semantic-release-config-npm 2.2.0
• @types/jest 29.5.12
• @types/node 20.11.25
• commitizen 4.3.0
• cz-conventional-changelog ^3.3.0
• husky 9.0.11
• jest 29.7.0
• jest-mock-axios 4.7.3
• npm-run-all2 5.0.0
• pinst 3.0.0
• rimraf 5.0.5
• ts-jest 29.1.2
• typescript 5.4.2
• node >=14
• node 20.11.1
• yarn 1.22.21

---

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

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

---

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://x-access-token:[secure]@github.com/pliancy/duo-sdk.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

---

Good luck with your project ✨

Your semantic-release bot 📦🚀