Repository navigation
chore: prepare v1.0.0-beta.6 - #216
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ZingerLittleBee
marked this pull request as ready for review
October 6, 2026 04:29
railway-app
Bot
temporarily deployed
to
ServerBee Server / production
October 6, 2026 04:30
Inactive
This branch was successfully deployed
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.
Prepare
v1.0.0-beta.6from the dated CHANGELOG section on fixed candidateb892c1d876110e4df275e2b1e5520263d4e11d5e, based on #215 atf9cbb8e3d4a09eb6cd9c9d2e73c5b404ab65c532. The complete renewal feature for #208 was implemented and merged in #214. This preparation updates regenerated locks, package and OpenAPI metadata, the installer version, documentation and Railway template version references.Standards and Spec reviews report zero outstanding findings. The documentation version contract was fixed without changing its assertions. Compiled Rust, Web, native and installer sources and the four release inputs are byte-identical to predecessor
4fed3705959513c5e8ac21bcc7c76b291faa2b6f. The predecessor and candidate have different Git trees; the independently audited disposable-host lifecycle matrix passed all 17 cases on the predecessor's exact runtime inputs.All 14 expected current-head PR jobs succeeded: nine CI jobs, two CI iOS jobs, Documentation, CI Push Relay worker and Commit Attribution. Actual PR checkout
0beb379d48972330401a0329cff3333f07e2dcbband candidate head share tree11ef6542ee287c76b4591d3e2298d0f69f339932. A stale event merge hint in archived iOS metadata is not used as source provenance.Executed validation: Rust 3,564 tests across core targets and all 47 integration targets, including 52 renewal integration cases; Web 889; widget SDK 53; Push Relay 74; Documentation 11 Chromium tests plus contracts; hosted macOS native 473 and real Simulator UI 3, with zero native/UI failures or skips. Five fixture saves across three UI scenarios and all 14 screenshot attachments were retained. The complete UI archive was hashed independently, and its bounded evidence transfer was revalidated against 186 file hashes with strict repository validators and key screenshot inspection.
The additional local Rust gate is complete: the environment-interrupted workspace run supplied 3,033 completed passes, and its remaining 20 integration targets exited zero with 531 passes. Together these cover 2,622 core and 942 integration tests across all 47 targets, with zero failures and one pre-existing privileged Agent ignore. Document tests also exited zero with zero discovered cases. Partial results from the interrupted target are excluded, and the interrupted full command is not reported as an exit-zero run. Existing workspace formatting differences remain baseline-only.
Publication still requires owner-controlled integration at the expected head, all 13 expected main-push jobs, a freshly checked official
make publishdry run, and terminal Release workflow plus public binary, checksum, architecture and distribution verification. No Beta.6 tag or release has been pushed.The existing Railway demo remains Beta.5. Before main can trigger a wrapper build, only its existing non-secret image selector will be held at the verified immutable Beta.5 digest with automatic redeployment skipped. Actual Beta.6 upgrade requires public immutable artifacts and a fresh consistent backup with isolated database restore evidence. The separately authorized backup session keeps production data private; service-level recovery and lossless rollback after new writes remain unverified. Production billing and real notification channels are untouched.