Dexus / pem

Create private keys and certificates with node.js
Other
570 stars 129 forks source link

chore(deps): update dependency jsdoc to v4 #355

Closed renovate[bot] closed 11 months ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jsdoc 3.6.10 -> 4.0.2 age adoption passing confidence

Release Notes

jsdoc/jsdoc (jsdoc) ### [`v4.0.2`](https://togithub.com/jsdoc/jsdoc/compare/4.0.1...4.0.2) [Compare Source](https://togithub.com/jsdoc/jsdoc/compare/4.0.1...4.0.2) ### [`v4.0.1`](https://togithub.com/jsdoc/jsdoc/compare/084218523a7d69fec14a852ce680f374f526af28...4.0.1) [Compare Source](https://togithub.com/jsdoc/jsdoc/compare/084218523a7d69fec14a852ce680f374f526af28...4.0.1) ### [`v4.0.0`](https://togithub.com/jsdoc/jsdoc/blob/HEAD/CHANGES.md#400-November-2022) [Compare Source](https://togithub.com/jsdoc/jsdoc/compare/3.6.11...084218523a7d69fec14a852ce680f374f526af28) - JSDoc releases now use [semantic versioning](https://semver.org/). If JSDoc makes backwards-incompatible changes in the future, the major version will be incremented. - JSDoc no longer uses the [`taffydb`](https://taffydb.com/) package. If your JSDoc template or plugin uses the `taffydb` package, see the [instructions for replacing `taffydb` with `@jsdoc/salty`](https://togithub.com/jsdoc/jsdoc/tree/main/packages/jsdoc-salty#use-salty-in-a-jsdoc-template). - JSDoc now supports Node.js 12.0.0 and later. ### [`v3.6.11`](https://togithub.com/jsdoc/jsdoc/blob/HEAD/CHANGES.md#3611-July-2022) [Compare Source](https://togithub.com/jsdoc/jsdoc/compare/3.6.10...3.6.11) Updates dependency versions to make JSDoc compatible with Node.js 12.0.0 and later.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 11 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.