Dependency Dashboard

[renovate]

This issue provides visibility into Renovate updates and their statuses. Learn more

Rate Limited

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

• chore(deps): update dependency @types/jest to v27
• chore(deps): update dependency husky to v7
• chore(deps): update dependency jest-junit to v13
• chore(deps): update dependency semantic-release to v18

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• chore(deps): update dependency axios to 0.21.2 [security]
• chore(deps): update dependency glob-parent to 5.1.2 [security]
• chore(deps): update dependency handlebars to 4.7.7 [security]
• chore(deps): update dependency lodash to 4.17.21 [security]
• chore(deps): update dependency normalize-url to 4.5.1 [security]
• chore(deps): update dependency set-value to 4.0.1 [security]
• chore(deps): update dependency trim-newlines to 3.0.1 [security]

Open

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

• chore(deps): update dependency hosted-git-info to 2.8.9 [security]
• chore(deps): update dependency path-parse to 1.0.7 [security]
• chore(deps): update dependency semver-regex to 3.1.3 [security]
• chore(deps): update dependency tmpl to 1.0.5 [security]
• chore(deps): update commitlint monorepo (major) (@commitlint/cli, @commitlint/config-angular, @commitlint/config-conventional, @commitlint/prompt-cli)
• chore(deps): update dependency fixpack to v4
• chore(deps): update jest monorepo (major) (babel-jest, jest, ts-jest)
• chore(deps): update node.js to v16
• Click on this checkbox to rebase all open PRs at once

---

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

[calebcartwright]

@beverts312 - realize you're not exactly active around here anymore but you have expressed some strong preferences on dependency management in the past so I wanted to double check with you first.

At the Org level, I've started the process of removing Renovate and converting everything over to Dependabot for consistency. My preference would be to do this consistently across the board, including for this repo and the ado-aws-widgets repo. As such, two questions for you:

• Thoughts on archiving this project? I've been periodically updating the deps, especially when there's major/breaking version updates, but it's been a long time since there's been any substantive development activity (~3 years since last publish, likely just as long since the last non-dependency related commit), and the download/install counts are pretty low as well. I'm using this same criteria to justify archiving several other of our projects
• If you do want to keep it unarchived/active, thoughts/preferences on Dependabot vs. Renovate? Dependabot is lacking a couple features, like update groups, but I also think it has other features that could make dependency management a bit easier here given the nature of activity