Skip to content

fix: verify the release README with portable repository paths - #69

Merged
logohere merged 1 commit into
docs/landingfrom
fix/portable-release-readme-check
Nov 1, 2026
Merged

logohere merged 1 commit into
docs/landingfrom
fix/portable-release-readme-check

Conversation

@logohere

@logohere logohere commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Fixes #68. Two-file follow-up to the 1.0 website release.

  • Replace hard-coded machine checkout paths with this repository's README and its release/migration/npm/Bun entries.
  • Resolve manifest paths against the checker root and fail on external paths instead of silently skipping them.
  • Keep the existing drift workflow; no new dependency or cross-repository machinery.

Verification: normal README check passes without skips. Isolated actual-checker regression cases reject a missing Bun command and a parent-directory escape. Diff check passes; current tracked-text scan found no remaining user-home paths. Website HTML/assets are unchanged from the reviewed and live-tested #66 release.

logohere commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

Reviewed 9cf4570: exactly the manifest and README checker change; public HTML/assets are unchanged. Current-head drift and site checks pass. Actual checker regression cases pass for repository-relative success, missing release command failure and external-path rejection. No external entries are skipped. Proceeding with the requested merge using the existing per-PR admin path; branch protections remain unchanged.

@logohere
logohere merged commit 2ed8434 into docs/landing Nov 1, 2026
3 checks passed
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.

fix: make release README verification portable

1 participant