Skip to content

fix: validate Swift undo boundaries and exact release artifact - #44

Merged
lodystage[bot] merged 1 commit into
mainfrom
fix/1171-release-validation
Oct 22, 2026
Merged

lodystage[bot] merged 1 commit into
mainfrom
fix/1171-release-validation

Conversation

@lodystage

@lodystage lodystage Bot commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Update Swift undo tests to the Loro 1.17 one-item-per-call history behavior. Remote-deleted edits consume a no-op item and return false; older edits remain available for later calls. The previous release gate correctly caught two stale expectations. Keep the full Swift test gate enabled.

Record the exact XCFramework workflow run, source SHA, and checksum in the generated release commit. Verify that metadata against Package.swift and the downloaded artifact before tagging or publishing, so retried builds cannot select an unrelated ZIP. Allow distinct build retry tags while preserving the package version; never move a published version tag.

Validation: actionlint and git diff --check passed. Full Swift execution runs in the macOS CI and pre-release gate.

@lodystage
lodystage Bot merged commit e222b3e into main Oct 22, 2026
1 check passed
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.

1 participant