chore(renovate): use shared wolfstar-project preset - #33
Conversation
| { | ||
| "$schema": "https://docs.renovatebot.com/renovate-schema.json", | ||
| "extends": ["github>sapphiredev/.github:sapphire-renovate"], | ||
| "extends": ["github>wolfstar-project/.github:wolfstar-renovate"], |
There was a problem hiding this comment.
Renovate preset cannot be resolved
The new github>wolfstar-project/.github:wolfstar-renovate reference resolves to wolfstar-renovate.json at the root of wolfstar-project/.github, but that GitHub contents endpoint currently returns 404. Renovate stops with Cannot find preset's package, so dependency update processing cannot start. Publish the preset at the configured location or update this reference to its accessible path before merging.
Artifacts
Renovate dry-run validation harness
- Authored shell harness invokes Renovate in local dry-run mode against a supplied configuration, providing the executable validation path used for both captures.
Baseline Renovate configuration using the prior Sapphire preset
- Authored baseline configuration preserves the same local @types/node disable rule while using the parent preset for side-by-side execution.
Baseline Sapphire preset resolves and recognizes the @types/node disable rule
- Executed Renovate baseline capture shows successful Sapphire preset retrieval and the migrated enabled-false @types/node package rule in resolved configuration.
Changed Wolfstar preset fails Renovate resolution
- Executed Renovate capture against the changed configuration shows the exact GitHub API request returns 404 and causes config-presets-invalid.
GitHub contents API returns 404 for wolfstar-renovate.json
- Direct executed GitHub API request returns HTTP 404 and a Not Found payload for the preset path Renovate attempted to load.
Validation artifact hashes and unchanged tracked configuration check
- Executed integrity check confirms no diff exists for the tracked Renovate configuration and records hashes of the validation evidence.
Ran code and verified through T-Rex
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/renovate.json
Line: 3
Comment:
**Renovate preset cannot be resolved**
The new `github>wolfstar-project/.github:wolfstar-renovate` reference resolves to `wolfstar-renovate.json` at the root of `wolfstar-project/.github`, but that GitHub contents endpoint currently returns 404. Renovate stops with `Cannot find preset's package`, so dependency update processing cannot start. Publish the preset at the configured location or update this reference to its accessible path before merging.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Summary
sapphiredev/.github:sapphire-renovatepreset to wolfstar-project's own shared preset,github>wolfstar-project/.github:wolfstar-renovate.@types/nodematches undernpm.packageRules) unchanged.Notes
wolfstar-renovate.jsonpreset) should be merged first, otherwise this repo'sextendsreference will fail to resolve.Test plan
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Confidence Score: 4/5
Not safe to merge until the shared Renovate preset reference resolves successfully.
A real Renovate dry run and a direct request to the exact GitHub contents endpoint both reproduced the unavailable preset path. A comparison run confirmed the prior preset and local package rule work.
Files Needing Attention:
.github/renovate.jsonline 3 needs an accessible Wolfstar preset path, or the referencedwolfstar-renovate.jsonmust be published at the expected repository root.What T-Rex did
Prompt To Fix All With AI
Reviews (1): Last reviewed commit: "chore(renovate): extend shared wolfstar-..." | Re-trigger Greptile