Release Codex Usage Dock 0.7.0 - #25
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
https://github.com/TheBeems/CodexUsageDock/blob/4eea4557f887111e81b89f11f32d7137c5ac2b56/CodexUsageDock.csproj#L6
Update the hard-coded release-version test
When the Store workflow reaches its x64 test step, the project reference now emits CodexUsageDockMetadata.Version as 0.7.0, but UsageDataTests.DetailsPageUsesTheProjectReleaseVersion still asserts 0.6.1 at line 206. This makes the release commit's required test job fail before either architecture is built or the Store package is produced; update that assertion alongside the project version.
AGENTS.md reference: AGENTS.md:L81-L84
ℹ️ 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".
Release the accumulated quota, history, diagnostics, and Dock improvements as 0.7.0. Bump the project version and its details-page assertion, and move the linked Unreleased changelog entries into the dated release section. The Store builder derives MSIX version 0.7.0.0 without changing the tracked manifest or Store identity.
Validation: 353 native ARM64 tests passed. GitHub run 34744294278 passed x64 tests, Debug builds for x64 and ARM64, Store upload validation, and source-manifest integrity. git diff --check passed.
The ARM64 integration preflight passed source/generated manifest, self-contained runtime, assets, CLSID and AppExtension discovery checks. Live registration/process checks do not match the selected Release output because the current user is running a separate Debug development registration. Clean Store-signed installation and interactive x64/ARM64 verification remain unperformed.