Commit Graph

10 Commits

Author SHA1 Message Date
omkarht
a28965064d chore: downgrade chokidar to 3.6.0 2025-07-14 19:34:02 +05:30
Sidharth Vinod
eb8e4da5f6 chore: Bump package.json versions with renovate 2025-02-21 22:50:01 +05:30
Sidharth Vinod
c24028f2a4 chore: Separate dompurify updates 2024-10-08 15:00:57 +05:30
Sidharth Vinod
9400e46827 Separate eslint packages from updates 2024-06-28 12:11:41 +05:30
Sidharth Vinod
16aa9a310c Update renovate json 2024-03-23 11:02:34 +05:30
Sidharth Vinod
6883a92672 Split renovate groups 2023-04-20 09:40:58 +05:30
Alois Klink
c2bd6a490f ci(renovate): disable pinning dependencies
We shouldn't pin dependencies unless we have to.

This is for two reasons:

- If a dependency has a security issue, users should be able to
  easily update the dependency, before `mermaid` makes a new release
- If using `mermaid.core.js` in an app, using a dependency range
  means that users can bundle less dependencies.
  E.g. they won't need to bundle `lodash@4.17.y` just becasue mermaid
  needs `lodash@4.17.x`.

For development/CI, our dependencies are pinned by pnpm-lock.yaml
file anyway.
2022-11-16 20:00:17 +00:00
Sidharth Vinod
f5692e742b chore: renovate lint 2022-10-10 20:39:25 +08:00
Matthieu MOREL
8ea1a1a077 Update renovate.json 2022-10-10 14:22:04 +02:00
renovate[bot]
800cb65706 chore(deps): add renovate.json 2022-10-10 11:27:41 +00:00