Skip to content

fix(release): restore automatic version increments - #60

Merged
johnnyhuy merged 1 commit into
mainfrom
agent/issue-59-automatic-release-versioning
Nov 13, 2026
Merged

johnnyhuy merged 1 commit into
mainfrom
agent/issue-59-automatic-release-versioning

Conversation

@johnnyhuy

@johnnyhuy johnnyhuy commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Remove the permanent release-as override 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 lint passed, with 491 existing warnings and zero serious violations.
  • mise run build passed.
  • mise run test passed, including 23 video pipeline smoke checks, 169 XCTest tests and 41 Swift Testing tests.
  • node .tmp/proof/release-preview.cjs passed. 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.

Release Please 17.1.3, matching the pinned CI action
Read-only preview using live main commits, releases and tags, with local config substituted
Before proposal: chore(main): release 1.0.0
Before prospective release tag: v1.0.0
After proposal: chore(main): release 1.1.0
After prospective release tag: v1.1.0
PASS: proposal, manifest update and prospective release agree on 1.1.0; tag is unused
PASS: no PR, release or tag was created by this preview

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.

$ mise run lint
Done linting! Found 491 violations, 0 serious in 139 files.
$ mise run build
Build complete! (36.48s)
$ mise run test
Executed 169 tests, with 0 failures (0 unexpected)
Test run with 41 tests in 5 suites passed after 0.010 seconds.

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.

Remove the permanent 1.0.0 release override so future proposals advance from the published version.

Co-authored-by: OpenAI Codex <noreply@openai.com>
@johnnyhuy
johnnyhuy merged commit 828b8b3 into main Nov 13, 2026
10 checks passed
@johnnyhuy
johnnyhuy deleted the agent/issue-59-automatic-release-versioning branch November 13, 2026 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Restore automatic release versioning after v1.0.0

1 participant