Refresh merge reliability evidence#366
Merged
Merged
Conversation
Record the latest upload validator, branch-birth Git update guard, and v0.1.42 release gate evidence.
Merged
adamziel
added a commit
that referenced
this pull request
May 18, 2026
## Release `v0.1.43` Version bump and release metadata update for `v0.1.43`. **Changelog draft:** * Validate built-in attachment original image shape ([#364](#364)) * Reject Git branch updates without branch database ([#365](#365)) * Refresh merge reliability evidence ([#366](#366)) **Full changelog:** v0.1.42...release/v0.1.43 ## Next steps 1. **Review** the changes in this pull request. 2. **Push** any additional edits to this branch (`release/v0.1.43`). 3. **Merge** this pull request to publish `v0.1.43`. Merging will automatically build ForkPress binaries, create a GitHub release, and update the Homebrew formula. Co-authored-by: Codex <codex@openai.com>
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.
What it does
Refreshes
docs/merge-reliability.mdafter the latest reliability slices landed.Rationale
The roadmap should track actual trunk evidence, not stale release or branch-birth status.
v0.1.42is now the current release-gate proof, and the Git update path now rejects existing non-main branches with missing SQLite databases.Implementation
Adds evidence for:
_wp_attachment_metadata.original_imageinvalid-shape handlingv0.1.42release workflow and Apple Silicon artifactTesting instructions