Skip to content

fix: gate BTST releases and repair npm consumers and static scaffolds - #274

Merged
olliethedev merged 12 commits into
mainfrom
fix/release-gate-repair
Sep 12, 2026
Merged

olliethedev merged 12 commits into
mainfrom
fix/release-gate-repair

Conversation

@olliethedev

@olliethedev olliethedev commented Sep 12, 2026 •

Copy link
Copy Markdown
Collaborator

Public Next.js Blog scaffolds now render anonymous server HTML and refresh browser identity after hydration. Protected CMS, Forms and Kanban example URLs redirect to their existing request-authorized pages instead of serializing trusted management data into shared static HTML. Regression coverage executes generated layouts, verifies public HTML and browser controls, checks redirect build metadata and exercises anonymous API denial and authenticated navigation. Addresses #272.

Strict auth consumers explicitly declare React Email’s matching renderer to avoid the reproduced npm peer-placement ERESOLVE; npm and pnpm installation, tree validation, typecheck and production bundles pass. The minimal published React Email combination also reproduces the issue, so this is a documented compatible consumer declaration, not a universal npm resolver fix. The separate Next.js Better Auth UI fixture pins ESLint9 for its React/import/a11y peer cohort; all three framework fixtures pass strict peers, dependency-cohort checks, build and typecheck. Closes #271.

The generator installs next-themes0.4.6 and the intended stack3.0.2; documentation uses codegen0.2.1. Product proof capture removes all exact owned fixtures before and after failures/success, paginates safely, continues independent cleanup after errors, and explicitly removes Kanban children on the memory adapter. Historical #266/#267/#268 and #272/#273 are included in review scope with evidenced dispositions.

Publication now requires green validation workflows, checks, completed Vercel deployments and bot finding dispositions for the exact release commit. Workflow inventory comes from the candidate Git tree; run lookup uses its SHA so future main workflow changes cannot break historical retries. Each newly included PR also requires a completed Codex review of its final head. All review sources are paginated, verified publication defines the baseline, two complete evidence snapshots must agree, and fresh receipts are retained before each npm publish. Registry CI rejects stale output rather than making skip-CI commits. Publication uses the existing trusted workflow for stack3.0.2 and codegen0.2.1 only after the gate passes.

Validation: framework build/typecheck/lint, 196 CLI tests,14 gate rejection tests, controlled cleanup tests plus a real memory-backend deletion regression, strict npm/pnpm auth consumers, all three companion framework fixtures, and registry Next.js consumer build passed locally. All 1,051 stack tests and five focused Next.js browser checks pass, including static public Blog content/identity refresh, protected management redirects, anonymous API denial and authenticated navigation. Safeguard re-review is clean. All final-head remote CI/CD and Codex review results remain required before merge/publication.

@vercel

vercel Bot commented Sep 12, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
better-stack-docs Ready Ready Preview Sep 12, 2026 7:24pm UTC
better-stack-playground Ready Ready Preview Sep 12, 2026 7:24pm UTC

Request Review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fdf810ce94

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread scripts/release-gate/gate.mjs Resolved
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 12, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-12T19:27:08.263816Z 10d1946 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@olliethedev

Copy link
Copy Markdown
Collaborator Author

@codex review

@olliethedev

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

Provided git ref 52218671fd631d76e7dd5bf8e3c15c51246c5675 does not exist
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@olliethedev

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bcddffb4ff

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/review-dispositions.json Resolved
@olliethedev

Copy link
Copy Markdown
Collaborator Author

@codex review

Please review the final PR head 1391923. The prior ancestry finding has an evidenced original-thread disposition: #274 (comment) . Both fix commits are ancestors in the actual GitHub graph; the cited 2dc4b575 checkout was a different commit. GitHub comparisons independently verify afadaa7c to the current candidate and 44abebe4 to the current candidate. The release workflow uses the actual tag with full history, and this PR will use a merge commit preserving fix ancestry. Validate release ancestry against that actual graph.

The earlier worker checkout failure was followed by a completed review on bcddffb; provider diagnostic notices never satisfy the separately required completed final-head review.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 13919233c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@olliethedev

Copy link
Copy Markdown
Collaborator Author

@codex review

Please review the current final head a2cdca2. The focused change recognizes the exact official-provider, SHA-normalized full-body clean-review notice. Completed final-head review and every separately collected finding remain mandatory; appended or substituted actionable text is rejected. All14 gate tests pass. The branch preserves the actual original fix commits in its GitHub ancestry; earlier synthetic checkout ancestry differs from the real branch.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a2cdca222d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/workflows/release.yml Resolved
@olliethedev

Copy link
Copy Markdown
Collaborator Author

@codex review

Please review final head de20623. The only implementation change since a2cdca2 is explicit statuses: read in both release token scopes; all13 REST endpoint templates and the sole GraphQL review-thread query were audited against both scopes. PR issue-comments accepts existing pull-requests: read. No new write permissions.14 gate tests/lint pass and independent security/API-scope review is clean. The documented capability is now explicit; no live403 was reproduced in this public repository. Original finding3997240216 has fixing commit9c54c9b6, evidence disposition and original-thread reply. All final-head CI/CD remains required.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. More of your lovely PRs please.

Reviewed commit: de206237ea

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@olliethedev

Copy link
Copy Markdown
Collaborator Author

@codex review

Please review final head10d19463597277162c6d1671959878858f339e47. Since de20623 (completed clean), only exact-body clean-notice fingerprints and their rejection coverage changed. Scanning the full788 repository issuecomment history found16 benign complete-body variants, with different fixed courtesy sentences. All16 full-body SHA256 hashes were independently verified; only Reviewed commit SHA is normalized. Provider identity, unknown-prose rejection, separate finding dispositions and final-head Completed review are unchanged.14 gate tests verify each variant and reject appended or substituted findings; lint/security review clean. Original source examples include PR274 issuecomment5648102908, PR240 issuecomments5462470685/5462163756; the gate still requires fresh final-head CI/CD.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. More of your lovely PRs please.

Reviewed commit: 10d1946359

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@olliethedev
olliethedev merged commit 71b2072 into main Sep 12, 2026
14 checks passed

This branch was successfully deployed

2 active deployments
Preview – better-stack-docs — 10d19463 Deployed Sep 12, 2026 by vercel[bot]
Preview – better-stack-playground — 10d19463 Deployed Sep 12, 2026 by vercel[bot]
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.

Investigate npm auth consumer React Email peer resolution failure

1 participant