Skip to content
This repository was archived by the owner on Sep 24, 2026. It is now read-only.

fix: audit script expects 0 routes, matching the bare starter - #23

Closed
jimhoyd wants to merge 1 commit into
mainfrom
fix-audit-expect-routes-bare-starter
Closed

jimhoyd wants to merge 1 commit into
mainfrom
fix-audit-expect-routes-bare-starter

Conversation

@jimhoyd

@jimhoyd jimhoyd commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The default starter shipped by @jimhoyd/urlcode (see urlcode#503 "simplify init to one bare starter") now scaffolds with zero example routes by design — its urlcode.yaml reads "Start with no routes. Add only the files and routes your application needs."
  • This repo's own audit script still hardcoded --expect-routes 2, left over from before that change.
  • Since urlcode#502 "generate the public template from the initializer", the release pipeline regenerates this template's starter files from the initializer on every core release, so this mismatch fails every future release's "pin starter to new version" step.

Change

"audit": "urlcode audit --expect-routes 2" → "audit": "urlcode audit --expect-routes 0", matching the bare starter's actual route count.

Note

This alone isn't sufficient to unblock the release pipeline — urlcode audit also refuses "ready" status for any project with zero active routes (notReadyReasons: ["no-active-routes"]), independent of --expect-routes matching. That's being addressed separately by removing audit from the release-gate script list in urlcode's scripts/release-template.ts (this fix still matters for anyone running npm run audit manually/standalone). See urlcode#512.

The default starter (urlcode-core#503, "simplify init to one bare
starter") now scaffolds with zero example routes by design
(urlcode.yaml: "Start with no routes."). This repo's audit script
still hardcoded --expect-routes 2 from before that change, so every
release-pipeline pin of this template to a new core version failed
its route-count check.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@jimhoyd

jimhoyd commented Sep 23, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #24, which folds this same fix in alongside the actual bare-starter content regeneration (both are needed together for CI to pass).

@jimhoyd jimhoyd closed this Sep 23, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants