Repository navigation
fix(release): restore automatic version increments - #60
Merged
Merged
Conversation
Remove the permanent 1.0.0 release override so future proposals advance from the published version. Co-authored-by: OpenAI Codex <noreply@openai.com>
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove the permanent
release-asoverride so Release Please calculates the next version from conventional commits and the published release. The existing v1.0.0 release and tag are preserved.Completes the automatic versioning slice of #56. Part of #56. Closes #59.
Verification
mise run lintpassed, with 491 existing warnings and zero serious violations.mise run buildpassed.mise run testpassed, including 23 video pipeline smoke checks, 169 XCTest tests and 41 Swift Testing tests.node .tmp/proof/release-preview.cjspassed. The read-only preview used Release Please 17.1.3, matching the pinned CI action, live main commits, release and tag data, and each local config. It built the proposed PR and manifest update, then parsed the proposal into a prospective release. It created no PR, tag or release.The CI run passes all checks, including SwiftPM build and tests, iOS build and lint, UI tests with coverage, mobile e2e, CodeQL and Socket security checks.
Proof
The Release Please transcript demonstrates the duplicate before the fix and a consistent, unused version after it.
The repository gates also passed. CI additionally ran 27 UI tests with zero failures and mobile e2e finished with 3 passed and 1 flaky test that passed on retry. The flaky test was
start workout, log a set, rest timer appears, tracked separately in #62 after an initial app foreground timeout.Review notes
No user-facing behaviour or app UI changed, so screenshots and simulator capture are not applicable. No new tests were added for this configuration-only fix; the actual release engine preview supplies behavioural evidence.
Duplicate release PR #58 was closed and its branch deleted because it repeated the existing v1.0.0 release. The training epics remain open. After merge, the main Release Please run passed and generated release PR #61 for v1.1.0, matching the preview. Release PR #61 was merged after its checks passed. The publication workflow passed and published v1.1.0 at commit
3e4384ee3e94d24b923fd9dbb61572bfc1d66eec. The original v1.0.0 release ID, publication time and target commit were compared before and after and remain unchanged. All child work for #56 is merged and live publication is verified.Release Please documents the manifest as the current version baseline in its manifest guide.