pliancy/guru-cli

A NodeJS based CLI tool for doing useful things against Guru KB

guru-cli's Issues

Dependency Dashboard

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.

Warning

These dependencies are deprecated:

Datasource	Name	Replacement PR?
npm	npm-run-all

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• fix(deps): update dependency axios to v0.28.1
• chore(deps): update dependency husky to v9
• chore(deps): update dependency rimraf to v6
• chore(deps): update node.js to v20 (node, @types/node)
• chore(deps): update semantic-release monorepo (major) (@semantic-release/github, @semantic-release/npm, semantic-release)
• chore(deps): update stefanzweifel/git-auto-commit-action action to v5
• fix(deps): update dependency @oclif/core to v4
• fix(deps): update dependency conf to v13
• 🔐 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): replace dependency npm-run-all with npm-run-all2 5.0.0
• chore(deps): update all non-major dependencies (@digitalroute/cz-conventional-changelog-for-jira, @oclif/core, @semantic-release/github, @semantic-release/npm, @types/cli-progress, @types/jest, @types/node, cac, cli-progress, commitizen, husky, jest, lint-staged, node, search-query-parser, ts-jest, ts-node, tslib, typescript)
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency @digitalroute/cz-conventional-changelog-for-jira to v8
• chore(deps): update dependency @pliancy/eslint-config-ts to v1
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency typescript to v5
• fix(deps): update dependency axios to v1
• fix(deps): update dependency chalk to v5
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/push.yml

• actions/checkout v2
• actions/setup-node v2

.github/workflows/release.yml

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

npm

package.json

• @oclif/core 1.16.4
• axios 0.27.2
• cac 6.7.2
• chalk 4.1.2
• cli-progress 3.9.0
• conf 10.2.0
• search-query-parser 1.5.5
• tslib 2.4.0
• @digitalroute/cz-conventional-changelog-for-jira 7.4.0
• @pliancy/eslint-config-ts 0.1.0
• @pliancy/semantic-release-config-npm 2.2.0
• @semantic-release/git 10.0.1
• @semantic-release/github 8.0.6
• @semantic-release/npm 9.0.1
• @types/cli-progress 3.9.0
• @types/jest 29.1.0
• @types/node 17.0.21
• commitizen 4.2.5
• cz-conventional-changelog 3.3.0
• husky 8.0.1
• jest 29.1.1
• lint-staged 13.0.3
• npm-run-all 4.1.5
• rimraf 3.0.2
• semantic-release 19.0.5
• ts-jest 29.0.3
• ts-node 10.9.1
• typescript 4.8.4
• node >=12
• node 14.20.1

---

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

---

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Quotation marks in title cause verify-by-title to fail

This is due to the way the string parsing works for the title argument.

Some characters in a title (+ for example) cause verify-by-title to fail to locate the card

verify-by-title doesn't support the case insensitive flag (-i)

verify expired should offer expiration option / set a longer default expiration interval

Verify-by-title fails if there is a group assigned as verifier

This is due to the expectation that the guru api returns an email associated with a single user.

Removing a user from guru that's assigned as an author or verifier of any article breaks features