Skip to content

chore(renovate): use shared wolfstar-project preset - #33

Open
RedStar071 wants to merge 1 commit into
mainfrom
chore/shared-renovate-preset
Open

chore(renovate): use shared wolfstar-project preset#33
RedStar071 wants to merge 1 commit into
mainfrom
chore/shared-renovate-preset

Conversation

@RedStar071

@RedStar071 RedStar071 commented Aug 14, 2026

Copy link
Copy Markdown
Member

Summary

  • Switches this repo's Renovate config from the external sapphiredev/.github:sapphire-renovate preset to wolfstar-project's own shared preset, github>wolfstar-project/.github:wolfstar-renovate.
  • Keeps this repo's local override (disabling @types/node matches under npm.packageRules) unchanged.

Notes

  • Dependency: wolfstar-project/.github#45 (which adds the wolfstar-renovate.json preset) should be merged first, otherwise this repo's extends reference will fail to resolve.

Test plan


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with 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.json line 3 needs an accessible Wolfstar preset path, or the referenced wolfstar-renovate.json must be published at the expected repository root.

T-Rex T-Rex Logs

What T-Rex did

  • T-Rex ran a dry-run validation harness against the P1 finding and captured the baseline setup.
  • T-Rex confirmed that the baseline Sapphire preset resolves and recognizes the @types/node disable rule.
  • T-Rex observed that the Wolfstar preset fails Renovate resolution and that the GitHub contents API returns a 404 for wolfstar-renovate.json.
  • T-Rex completed validation artifact hashes check and verified that the tracked configuration remained unchanged.
  • General contract validation shows that after attempting the Wolfstar reference, the config-presets-invalid state appears due to the 404, and Renovate dependency updates are disabled until the preset becomes accessible.

View all artifacts

T-Rex Ran code and verified through T-Rex

Fix all with Greploop

Fix All in Claude Code Fix All in Cursor Fix All in Cursor Cloud Agents

Prompt To Fix All With AI
### Issue 1
.github/renovate.json:3
**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.

Reviews (1): Last reviewed commit: "chore(renovate): extend shared wolfstar-..." | Re-trigger Greptile

Greptile also left 1 inline comment on this PR.

Comment thread .github/renovate.json
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": ["github>sapphiredev/.github:sapphire-renovate"],
"extends": ["github>wolfstar-project/.github:wolfstar-renovate"],

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

View artifacts

T-Rex 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.

Fix in Claude Code Fix in Cursor Fix in Cursor Cloud Agents

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant