rmcampos/medminder
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: Configure Renovate #1

Merged
rmcampos merged 1 commits from renovate/configure into main 2026-07-05 21:11:56 +00:00
Conversation 0 Commits 1 Files Changed 1
+6
renovate-bot commented 2026-07-05 21:00:27 +00:00
Contributor
Copy Link
Copy Source

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

Detected Package Files

  • functions/copy-medications/package.json (npm)
  • functions/send-reminders/package.json (npm)
  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

What to Expect

With your current configuration, Renovate will create 16 Pull Requests:

chore(deps): update dependency @​vitejs/plugin-react to v6.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/vitejs-plugin-react-6.x-lockfile
  • Merge into: main
  • Upgrade @vitejs/plugin-react to 6.0.3
chore(deps): update dependency eslint-plugin-react-refresh to v0.5.3
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-react-refresh-0.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-react-refresh to 0.5.3
chore(deps): update react monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/react-monorepo
  • Merge into: main
  • Upgrade @types/react to 19.2.17
  • Upgrade react to 19.2.7
  • Upgrade react-dom to 19.2.7
chore(deps): update tailwindcss monorepo to v4.3.2
  • Schedule: ["at any time"]
  • Branch name: renovate/tailwindcss-monorepo
  • Merge into: main
  • Upgrade @tailwindcss/vite to 4.3.2
  • Upgrade tailwindcss to 4.3.2
chore(deps): update dependency @base-ui/react to v1.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/base-ui-react-1.x-lockfile
  • Merge into: main
  • Upgrade @base-ui/react to 1.6.0
chore(deps): update dependency @​types/node to v24.13.2
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 24.13.2
chore(deps): update dependency eslint to v10.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade eslint to 10.6.0
chore(deps): update dependency firebase to v12.15.0
  • Schedule: ["at any time"]
  • Branch name: renovate/firebase-12.x-lockfile
  • Merge into: main
  • Upgrade firebase to 12.15.0
chore(deps): update dependency globals to v17.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/globals-17.x-lockfile
  • Merge into: main
  • Upgrade globals to 17.7.0
chore(deps): update dependency lucide-react to v1.23.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lucide-monorepo
  • Merge into: main
  • Upgrade lucide-react to 1.23.0
chore(deps): update dependency react-router-dom to v7.18.1
  • Schedule: ["at any time"]
  • Branch name: renovate/react-router-monorepo
  • Merge into: main
  • Upgrade react-router-dom to 7.18.1
chore(deps): update dependency shadcn to v4.13.0
  • Schedule: ["at any time"]
  • Branch name: renovate/shadcn-4.x-lockfile
  • Merge into: main
  • Upgrade shadcn to 4.13.0
chore(deps): update dependency typescript-eslint to v8.62.1
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-eslint-monorepo
  • Merge into: main
  • Upgrade typescript-eslint to 8.62.1
chore(deps): update dependency vite to v8.1.3
  • Schedule: ["at any time"]
  • Branch name: renovate/vite-8.x-lockfile
  • Merge into: main
  • Upgrade vite to 8.1.3
fix(deps): update dependency appwrite to v26
  • Schedule: ["at any time"]
  • Branch name: renovate/appwrite-26.x
  • Merge into: main
  • Upgrade appwrite to ^26.0.0
fix(deps): update dependency node-appwrite to v26
  • Schedule: ["at any time"]
  • Branch name: renovate/node-appwrite-26.x
  • Merge into: main
  • Upgrade node-appwrite to ^26.0.0

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Mend Renovate.

Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. 📚 See our [Reading List](https://docs.renovatebot.com/reading-list/) for relevant documentation you may be interested in reading. 🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs. --- ### Detected Package Files * `functions/copy-medications/package.json` (npm) * `functions/send-reminders/package.json` (npm) * `package.json` (npm) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - Enable Renovate Dependency Dashboard creation. - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use. - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests (except for nuget) directories. - Group known monorepo packages together. - Use curated list of recommended non-monorepo package groupings. - Show only the Age and Confidence Merge Confidence badges for pull requests. - Apply crowd-sourced package replacement rules. - Apply crowd-sourced workarounds for known problems with packages. - Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff - Correctly link to the source code for golang.org/x packages - Link to pkg.go.dev/... for golang.org/x packages' title - Provide a link to octochangelog's improved breakdown for Renovate's changelogs --- ### What to Expect With your current configuration, Renovate will create 16 Pull Requests: <details> <summary>chore(deps): update dependency @&#8203;vitejs/plugin-react to v6.0.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/vitejs-plugin-react-6.x-lockfile` - Merge into: `main` - Upgrade [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react) to `6.0.3` </details> <details> <summary>chore(deps): update dependency eslint-plugin-react-refresh to v0.5.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/eslint-plugin-react-refresh-0.x-lockfile` - Merge into: `main` - Upgrade [eslint-plugin-react-refresh](https://github.com/ArnaudBarre/eslint-plugin-react-refresh) to `0.5.3` </details> <details> <summary>chore(deps): update react monorepo</summary> - Schedule: ["at any time"] - Branch name: `renovate/react-monorepo` - Merge into: `main` - Upgrade [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped) to `19.2.17` - Upgrade [react](https://github.com/facebook/react) to `19.2.7` - Upgrade [react-dom](https://github.com/facebook/react) to `19.2.7` </details> <details> <summary>chore(deps): update tailwindcss monorepo to v4.3.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/tailwindcss-monorepo` - Merge into: `main` - Upgrade [@tailwindcss/vite](https://github.com/tailwindlabs/tailwindcss) to `4.3.2` - Upgrade [tailwindcss](https://github.com/tailwindlabs/tailwindcss) to `4.3.2` </details> <details> <summary>chore(deps): update dependency @base-ui/react to v1.6.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/base-ui-react-1.x-lockfile` - Merge into: `main` - Upgrade [@base-ui/react](https://github.com/mui/base-ui) to `1.6.0` </details> <details> <summary>chore(deps): update dependency @&#8203;types/node to v24.13.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-24.x-lockfile` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `24.13.2` </details> <details> <summary>chore(deps): update dependency eslint to v10.6.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/eslint-monorepo` - Merge into: `main` - Upgrade [eslint](https://github.com/eslint/eslint) to `10.6.0` </details> <details> <summary>chore(deps): update dependency firebase to v12.15.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/firebase-12.x-lockfile` - Merge into: `main` - Upgrade [firebase](https://github.com/firebase/firebase-js-sdk) to `12.15.0` </details> <details> <summary>chore(deps): update dependency globals to v17.7.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/globals-17.x-lockfile` - Merge into: `main` - Upgrade [globals](https://github.com/sindresorhus/globals) to `17.7.0` </details> <details> <summary>chore(deps): update dependency lucide-react to v1.23.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/lucide-monorepo` - Merge into: `main` - Upgrade [lucide-react](https://github.com/lucide-icons/lucide) to `1.23.0` </details> <details> <summary>chore(deps): update dependency react-router-dom to v7.18.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/react-router-monorepo` - Merge into: `main` - Upgrade [react-router-dom](https://github.com/remix-run/react-router) to `7.18.1` </details> <details> <summary>chore(deps): update dependency shadcn to v4.13.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/shadcn-4.x-lockfile` - Merge into: `main` - Upgrade [shadcn](https://github.com/shadcn-ui/ui) to `4.13.0` </details> <details> <summary>chore(deps): update dependency typescript-eslint to v8.62.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/typescript-eslint-monorepo` - Merge into: `main` - Upgrade [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint) to `8.62.1` </details> <details> <summary>chore(deps): update dependency vite to v8.1.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/vite-8.x-lockfile` - Merge into: `main` - Upgrade [vite](https://github.com/vitejs/vite) to `8.1.3` </details> <details> <summary>fix(deps): update dependency appwrite to v26</summary> - Schedule: ["at any time"] - Branch name: `renovate/appwrite-26.x` - Merge into: `main` - Upgrade [appwrite](https://github.com/appwrite/sdk-for-web) to `^26.0.0` </details> <details> <summary>fix(deps): update dependency node-appwrite to v26</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-appwrite-26.x` - Merge into: `main` - Upgrade [node-appwrite](https://github.com/appwrite/sdk-for-node) to `^26.0.0` </details> 🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See [docs for `prHourlyLimit`](https://docs.renovatebot.com/configuration-options/#prhourlylimit) for details. --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
renovate-bot added 1 commit 2026-07-05 21:00:28 +00:00
Add renovate.json fcf8278963
rmcampos merged commit f951fee824 into main 2026-07-05 21:11:56 +00:00
rmcampos deleted branch renovate/configure 2026-07-05 21:23:56 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
rmcampos (Ricardo Campos)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rmcampos/medminder#1