We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey there 👋Our bot, Adaptly, found that 5 out of 10 currently open dependency update PRs can be merged.That's 50% right there:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hey there 👋
Our bot, Adaptly, found that 5 out of 10 currently open dependency update PRs can be merged.
That's 50% right there:
View Safe to Merge PRs
1. chore(deps): update dependency @4c/rollout to v42. chore(deps): update dependency @4c/build to v4
3. chore(deps): replace dependency babel-eslint with @babel/eslint-parser ^7.11.0
4. chore(deps): update dependency karma to v6.3.16 [security]
5. chore(deps): update dependency karma-webpack to v5
🔎 How does Adaptly know this?
It analyses changelogs of dependencies updated in a PR.If no breaking changes are found in the changelogs, PR is marked as good to merge.
✨ Try Adaptly yourself
Feel free to try Adaptly on your repositories and finallymerge dependency update PRs. Let us know if you have any questions.
Best of luck with your projects,
Lauris
[email protected]
The text was updated successfully, but these errors were encountered: