feat: automate app-modules release and app-monorepo sync - #123
Conversation
|
@codex review |
|
@codex security review |
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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cdd5bbbdba
ℹ️ 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".
|
Claude review session: https://claude.ai/code/session_01GN4VAXu1Jw39qQ51fL1Yrr |
Local Codex CLI reviewOpen the review session in Slack The review runs in a read-only local worktree and continues in this session when the PR receives a substantive commit. |
849537f to
42439d7
Compare
Problem
app-modules needs automatic preview packages for ordinary merged changes, while stable releases must use the version explicitly reviewed in source. npm acceptance alone is not enough to prove that a version is available to consumers.
Release policy
-alpha.<workflow run number>version across all publishable workspaces and exact internal dependencies, then publishes under npmnext. The preview version is not committed tomainand does not update app-monorepo.latest. The workflow does not bump versions or update CHANGELOG. Source PR approval is also release approval for a version-changing PR.Publishing and downstream sync
latestonly, update all app-modules pins on app-monorepox, including mobile npm aliases, components dependencies, and root dependency/resolution pins; refresh the lockfile, check the module-ID registry, and open an app-monorepo PR. Do not auto-merge it.Validation
queue: maxsetting.Required setup and boundaries