Skip to content

chore: sync main ancestry before v0.5.8 promotion - #355

Closed
mohanagy wants to merge 1 commit into
developmentfrom
main
Closed

chore: sync main ancestry before v0.5.8 promotion#355
mohanagy wants to merge 1 commit into
developmentfrom
main

Conversation

@mohanagy

@mohanagy mohanagy commented Aug 9, 2026

Copy link
Copy Markdown
Owner

Refs #350.

Synchronizes the prior v0.5.7 promotion merge from main back into development before the v0.5.8 promotion.

This is an ancestry-only maintenance sync: main contributes its prior promotion merge commit, while development retains the already-reviewed v0.5.8 tree. It is required because strict branch protection will not update the protected development branch directly while required checks are expected.

After this merges with current-head checks, #354 can be re-evaluated as an up-to-date development to main promotion.

release: promote v0.5.7 to main
@mohanagy

mohanagy commented Aug 9, 2026

Copy link
Copy Markdown
Owner Author

Superseded by #356. Using main directly as the head remained behind protected development, so strict branch protection could not merge it. #356 starts from current development and adds current main as a second parent with an identical tree, enabling the ancestry sync through normal protected checks.

@mohanagy mohanagy closed this Aug 9, 2026
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