Enable Dependabot for each sub-projects #44
Labels
Comments
|
@julien-deramond any reason why we don't use workspaces in this repo? npm supports it natively nowadays and should help with maintenance. As for dependabot feel free to proceed, but keep in mind it can get too noisy. Maybe renovate bot is better but I haven't used it in any of our projects yet. |
Nope, I haven't checked anything around it. We can try.
I don't have the rights, that's why I've created this issue initially. And because I'm updating "vite" deps because I follow this project but the other deps aren't really updated so far. |
|
You should have the rights sincerity have push rights already. Seems like a
misconfiguration issue, we'll sort it out tomorrow!
…On Mon, Mar 20, 2023, 21:28 Julien Déramond ***@***.***> wrote:
any reason why we don't use workspaces in this repo? npm supports it
natively nowadays and should help with maintenance.
Nope, I haven't checked anything around it. We can try.
As for dependabot feel free to proceed, but keep in mind it can get too
noisy.
I don't have the rights, that's why I've created this issue initially. And
because I'm updating "vite" deps because I follow this project but the
other deps aren't really updated so far.
—
Reply to this email directly, view it on GitHub
<#44 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACVLNNLT3QNNSXVRM2YDGTW5CVXHANCNFSM6AAAAAAVJO5J3U>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our examples are technically sub-projects that have their own dependencies in their
package.json.We should enable Dependabot for each sub-dir:
ATM I only update "vite" deps because I think of it thanks to the notification I receive of their new releases.
The text was updated successfully, but these errors were encountered: