Fix template sync after release - #5109
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: adf263d5a5
ℹ️ 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".
| "lucide-react": "1.34.0", | ||
| "next": "16.3.2", |
There was a problem hiding this comment.
Regenerate both templates after fixing the sync failure
In the recorded scenario, pnpm templates:update --local failed and template CI was skipped; because tooling/scripts/update-templates.sh uses set -e and updates the basic template before the AI template, these version bumps are partial working-tree output while plate-playground-template remains stale. Fix the source registry/workflow failure, rerun the complete two-template generation, and commit only CI-verified generated output.
AGENTS.md reference: AGENTS.md:L29-L29
Useful? React with 👍 / 👎.
adf263d to
5353d20
Compare
Template sync after release produced changes but did not pass automation.
pnpm templates:update --local:failureskipped