Repository navigation
Fix public blog date hydration across timezones - #273
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5721183be5
ℹ️ 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".
Public blog cards rendered April 28 on the server and April 29 in an Auckland browser for the same publication timestamp, causing React hydration recovery. The shared card and article-header formatter now explicitly uses UTC while preserving the existing English date style; card
dateTimeattributes retain the serialized ISO timestamp.Bumps
@btst/stackto 3.0.1 for a compatible patch release. No API, schema, codegen version, or dependency changes.Validation: timezone SSR/hydration regressions failed on the original code and now pass; all 84 focused blog and static-identity tests pass; package build, monorepo lint and type checks pass. Bio Mogging with the packed patch passes six real browser probes across New York, London and Auckland against an isolated local production-data snapshot (Auckland failed twice before the fix). Independent Safeguard review is clean.
CI: main checks passed (1,049 stack tests and 195 codegen tests). Core packed consumers pass with npm and pnpm; auth/account passes with pnpm. The auth npm fixture retains the same September 10
ERESOLVEconflict: React 19.2.8 versus react-dom 19.3.0 pulled through@react-email/render@2.0.6. Compared the current failed job with the saved pre-change log; this patch changes none of those dependencies. All three framework E2E suites passed. Registry build and consumer E2E passed; its final wait gate failed solely on the known auth npm fixture, so the exact regenerated blog registry is committed using the workflow's standard[skip ci]convention. Final registry-only commit changes no runtime source or dependencies. Docs/playground Vercel checks were skipped by their ignored-build rules.