Repository navigation
Conversation
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: ca6065fe31
ℹ️ 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".
| { | ||
| "name": "subboost", | ||
| "version": "2.8.1", | ||
| "version": "2.9.0", |
There was a problem hiding this comment.
Synchronize the remaining v2.9.0 version markers
When this commit is tagged as v2.9.0, local/package.json:3 and its package-lock.json workspace entry still report 2.8.1, while both README badges also advertise 2.8.1. Besides leaving the public release metadata inconsistent, a local/standalone deployment without the root manifest or injected APP_RELEASE_VERSION falls back to the local package version in resolveAppVersionInfo and therefore identifies the new build as 2.8.1. Update the local manifest, lock entry, and README badges together with the root version, as was done for prior releases.
Useful? React with 👍 / 👎.
Prepare SubBoost v2.9.0 with bilingual release notes for light and dark themes, subscription QR codes, expanded rule configuration, and subscription and session fixes. Update the package version and lockfile to 2.9.0.
Validation:
npm ci,npm run lint,npm run test:coverage, andnpm run check:local-apppassed. All four coverage metrics exceed 97%.