chore: Configure Renovate

[renovate]

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.

---

Detected Package Files

• docker-compose.yaml (docker-compose)
• .github/workflows/dx-test.yaml (github-actions)
• .github/workflows/go-build.yaml (github-actions)
• .github/workflows/go-lint.yaml (github-actions)
• .github/workflows/go-test.yaml (github-actions)
• .github/workflows/nix-flake-update.yaml (github-actions)
• .github/workflows/prune-workflows.yaml (github-actions)
• .github/workflows/release.yaml (github-actions)
• .github/workflows/webapp-deploy.yaml (github-actions)
• .github/workflows/webapp-lint.yaml (github-actions)
• factcheck/go.mod (gomod)
• foo/go.mod (gomod)
• pillars/go.mod (gomod)
• backoffice-webapp/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
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• 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.

🔡 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.

---

What to Expect

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

fix(deps): update github.com/kaogeek/line-fact-check/pillars digest to fc29df2

• Schedule: ["at any time"]
• Branch name: renovate/github.com-kaogeek-line-fact-check-pillars-digest
• Merge into: main
• Upgrade github.com/kaogeek/line-fact-check/pillars to fc29df27e39a

chore(deps): update dependency tw-animate-css to v1.3.6

• Schedule: ["at any time"]
• Branch name: renovate/tw-animate-css-1.x-lockfile
• Merge into: main
• Upgrade tw-animate-css to 1.3.6

fix(deps): update dependency react-i18next to v15.6.1

• Schedule: ["at any time"]
• Branch name: renovate/react-i18next-15.x-lockfile
• Merge into: main
• Upgrade react-i18next to 15.6.1

fix(deps): update dependency recharts to v3.1.2

• Schedule: ["at any time"]
• Branch name: renovate/recharts-3.x-lockfile
• Merge into: main
• Upgrade recharts to 3.1.2

fix(deps): update dependency sonner to v2.0.7

• Schedule: ["at any time"]
• Branch name: renovate/sonner-2.x-lockfile
• Merge into: main
• Upgrade sonner to 2.0.7

fix(deps): update dependency zod to v3.25.76

• Schedule: ["at any time"]
• Branch name: renovate/zod-3.x-lockfile
• Merge into: main
• Upgrade zod to 3.25.76

fix(deps): update radix-ui-primitives monorepo

• Schedule: ["at any time"]
• Branch name: renovate/radix-ui-primitives-monorepo
• Merge into: main
• Upgrade @radix-ui/react-alert-dialog to 1.1.15
• Upgrade @radix-ui/react-dialog to 1.1.15
• Upgrade @radix-ui/react-dropdown-menu to 2.1.16
• Upgrade @radix-ui/react-radio-group to 1.3.8
• Upgrade @radix-ui/react-scroll-area to 1.2.10
• Upgrade @radix-ui/react-tabs to 1.1.13

fix(deps): update react monorepo

• Schedule: ["at any time"]
• Branch name: renovate/react-monorepo
• Merge into: main
• Upgrade @types/react to 19.1.10
• Upgrade @types/react-dom to 19.1.7
• Upgrade react to 19.1.1
• Upgrade react-dom to 19.1.1

fix(deps): update tailwindcss monorepo to v4.1.12

• Schedule: ["at any time"]
• Branch name: renovate/tailwindcss-monorepo
• Merge into: main
• Upgrade @tailwindcss/vite to 4.1.12
• Upgrade tailwindcss to 4.1.12

chore(deps): update dependency @​types/node to v24.2.1

• Schedule: ["at any time"]
• Branch name: renovate/node-24.x-lockfile
• Merge into: main
• Upgrade @types/node to 24.2.1

chore(deps): update dependency @​vitejs/plugin-react-swc to v3.11.0

• Schedule: ["at any time"]
• Branch name: renovate/vitejs-plugin-react-swc-3.x-lockfile
• Merge into: main
• Upgrade @vitejs/plugin-react-swc to 3.11.0

chore(deps): update dependency globals to v16.3.0

• Schedule: ["at any time"]
• Branch name: renovate/globals-16.x-lockfile
• Merge into: main
• Upgrade globals to 16.3.0

chore(deps): update dependency lefthook to v1.12.3

• Schedule: ["at any time"]
• Branch name: renovate/lefthook-1.x-lockfile
• Merge into: main
• Upgrade lefthook to 1.12.3

chore(deps): update dependency prettier to v3.6.2

• Schedule: ["at any time"]
• Branch name: renovate/prettier-3.x-lockfile
• Merge into: main
• Upgrade prettier to 3.6.2

chore(deps): update dependency typescript to ~5.9.0

• Schedule: ["at any time"]
• Branch name: renovate/typescript-5.x
• Merge into: main
• Upgrade typescript to ~5.9.0

chore(deps): update dependency typescript-eslint to v8.39.1

• Schedule: ["at any time"]
• Branch name: renovate/typescript-eslint-monorepo
• Merge into: main
• Upgrade typescript-eslint to 8.39.1

chore(deps): update eslint monorepo to v9.33.0

• Schedule: ["at any time"]
• Branch name: renovate/eslint-monorepo
• Merge into: main
• Upgrade @eslint/js to 9.33.0
• Upgrade eslint to 9.33.0

fix(deps): update dependency @​hookform/resolvers to v5.2.1

• Schedule: ["at any time"]
• Branch name: renovate/hookform-resolvers-5.x-lockfile
• Merge into: main
• Upgrade @hookform/resolvers to 5.2.1

fix(deps): update dependency lucide-react to ^0.539.0

• Schedule: ["at any time"]
• Branch name: renovate/lucide-monorepo
• Merge into: main
• Upgrade lucide-react to ^0.539.0

fix(deps): update dependency react-hook-form to v7.62.0

• Schedule: ["at any time"]
• Branch name: renovate/react-hook-form-7.x-lockfile
• Merge into: main
• Upgrade react-hook-form to 7.62.0

fix(deps): update dependency react-router to v7.8.0

• Schedule: ["at any time"]
• Branch name: renovate/react-router-monorepo
• Merge into: main
• Upgrade react-router to 7.8.0

fix(deps): update tanstack-query monorepo

• Schedule: ["at any time"]
• Branch name: renovate/tanstack-query-monorepo
• Merge into: main
• Upgrade @tanstack/eslint-plugin-query to 5.83.1
• Upgrade @tanstack/react-query to 5.85.3

chore(deps): update actions/checkout action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: main
• Upgrade actions/checkout to v5

chore(deps): update actions/download-artifact action to v5

• Schedule: ["at any time"]
• Branch name: renovate/major-github-artifact-actions
• Merge into: main
• Upgrade actions/download-artifact to v5

chore(deps): update cachix/install-nix-action action to v31

• Schedule: ["at any time"]
• Branch name: renovate/cachix-install-nix-action-31.x
• Merge into: main
• Upgrade cachix/install-nix-action to v31

chore(deps): update dependency @​vitejs/plugin-react-swc to v4

• Schedule: ["at any time"]
• Branch name: renovate/vitejs-plugin-react-swc-4.x
• Merge into: main
• Upgrade @vitejs/plugin-react-swc to ^4.0.0

chore(deps): update dependency vite to v7

• Schedule: ["at any time"]
• Branch name: renovate/vite-7.x
• Merge into: main
• Upgrade vite to ^7.0.0

fix(deps): update dependency zod to v4

• Schedule: ["at any time"]
• Branch name: renovate/zod-4.x
• Merge into: main
• Upgrade zod to ^4.0.0

🚸 Branch 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 was generated by Mend Renovate. View the repository job log.

[soyart]

Are we sure Renovate works properly with Nix pinned versions? Especially with Go modules? Because if it updates go.mod and go.sum without consulting flake.nix we're screwed.

You should configure it to only work on JS/TS directories instead, and leave Go out of this for now.

Our monorepo (Go side) is experiencing a weird dependency cycle where we cannot properly pin pillars because the hash is content-addressed, i.e. the hash changes if we change our content. We, from within ourselves, cannot possibly point to "self".

A workaround for this is to use relative semver, but it's not the most elegant.

Another workaround is to put all Go code under factcheck, or have a shared package hosted somewhere else and let factcheck and foo point to it. But this will also cause problem with our unborn Line bot needs something from factcheck 🫠

[soyart]

@larb26656 maybe u forgot to merge this pr?