-
Notifications
You must be signed in to change notification settings - Fork 3
chore: dependency dashboard #239
New issue
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
Conversation
WalkthroughThis update revises dependency versions across the project. It upgrades the Codecov GitHub Action in the CI workflow, the Changes
Possibly related issues
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Nitpick comments (1)
package.json (1)
72-76: Pin vitest major to avoid surprise 4.x when it shipsAll bumped deps use the caret (
^). For tools that cut majors often (Vitest) you might get an unexpected 4.x next week which can break the CI.
Consider pinning to3.0.x(tilde) or adding Renovate “group major” rules so you control the timing.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (3)
.github/workflows/validate-code.yml(1 hunks)docker-compose.yml(1 hunks)package.json(3 hunks)
🧰 Additional context used
🧠 Learnings (1)
docker-compose.yml (1)
Learnt from: epsjunior
PR: genlayerlabs/genlayer-cli#237
File: docker-compose.yml:50-54
Timestamp: 2025-07-09T23:53:58.855Z
Learning: The yeagerai/genlayer-genvm-webdriver:0.0.3 Docker image appears to have a built-in healthcheck that allows service_healthy conditions to work in Docker Compose without explicit healthcheck configuration in the compose file.
🔇 Additional comments (4)
.github/workflows/validate-code.yml (1)
37-41: Codecov patch-level bump looks safe, but please re-generate upload token if you recently rotated secretsThe step only moves from
v5.4.2→v5.4.3, which is patch-level and should be non-breaking.
Still, Codecov occasionally deprecates old tokens after security incidents. Make sureCODECOV_TOKENin repo secrets is still valid after the bump, otherwise the upload will silently no-op.package.json (2)
46-48: Vitest coverage plugin major bump – double-check config flags
@vitest/coverage-v8jumped from^2→^3. v3 dropped the legacy--reporter=lcovshorthand and renamed several CLI flags.
If you call Vitest directly in scripts/CI (e.g.npm run test:coverage) verify that the arguments you pass are still recognised, otherwise coverage will be empty and the Codecov upload will fail.
60-66: Commander 14 may alter.opts()parsing of boolean / negated flagsCommander 14 tightened option coercion and removed some deprecated behaviours.
Run a quick smoke test of your CLI (genlayer --help, a couple of core commands) to ensure no flags broke, especially those relying on defaultfalsebooleans or--no-xxxnegations.docker-compose.yml (1)
98-101: ollama 0.9.x introduces auth & model-cache location changes – verify startup0.6 → 0.9 is a big jump; the container now:
- Enables optional token-based auth.
- Stores models under
/root/.ollamaby default.If you mount volumes or script against the old
/ollamapath, update them; otherwise models will be re-downloaded every boot.
Also confirm that the healthcheck or thewebrequestservice still functions if auth is toggled on by default upstream.
Dependency Dashboard Updates
This PR consolidates multiple Renovate dependency updates that were previously created as separate PRs. All updates have been merged and tested together to ensure compatibility.
✅ Completed Updates
Major Updates:
fix(deps): update dependency commander to v14- Updated from v13.x to v14.xfix(deps): update dependency dotenv to v17- Updated from v16.x to v17.xfix(deps): update vitest monorepo to v3- Updated @vitest/coverage-v8 and vitest to v3.xNon-Major Updates:
chore: all non major updates- Batch update of all non-breaking dependency updates including:Fixes:
fix: package lock- Updated package-lock.json to resolve dependency conflicts🔄 Merged Branches
This PR consolidates the following Renovate branches:
renovate/major-vitest-monoreporenovate/dotenv-17.xrenovate/commander-14.x⚙️ Renovate Configuration Changes
Templates Exclusion: Aligned with @cristiam86 that packages inside the templates/ folder will not be updated via Renovate
New Config: Created new Renovate configuration to prevent future PRs for template dependencies, ensuring template stability and avoiding unnecessary updates to example/starter code
📋 Testing
All dependency updates have been tested together to ensure:
🚀 Impact
This update brings the project up to date with the latest stable versions of dependencies, including security updates and performance improvements. The major version updates (commander, dotenv, vitest) have been verified to maintain backward compatibility with the existing codebase.
Summary by CodeRabbit