chore: bump web-container version to 30000375 after publish - #594
Merged
Conversation
`cargo make sign-webapp` incremented the counter during the publish of main @ 01aac14 (#593). Committing it so the next publish starts from a strictly higher number — the contract enforces monotonicity. Published: contract raAqMhMG7KUpXBU2SxgCQ3Vh4PYjttxdSWd9ftV7RLv, version 30000374 -> 30000375. Verified served by both local peers (:7509 and :7530, distinct processes) and by try.freenet.org: river-ui-dxhea72f231ce20c24b.js -> river-ui-dxhba19fed1bd326284.js. No WASM changed: all three committed contract/delegate binaries are byte-identical before and after the build, so no migration entry is needed and the delegate key is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DHubk7vg1mSjBQaoLVzs2h
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
1 participant
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
Commits the version counter that
cargo make sign-webappincremented during the publish of main @01aac14c(#593).published-contract/contract-version.txt: 30000374 → 30000375.The counter is the canonical source of the web-container version and the contract enforces monotonicity, so this has to land or the next publish reuses a version the network has already seen.
Publish record
01aac14c— verifiedHEAD == origin/mainat build time, not merely "on a branch off main"raAqMhMG7KUpXBU2SxgCQ3Vh4PYjttxdSWd9ftV7RLvriver-ui-dxhea72f231ce20c24b.js→river-ui-dxhba19fed1bd326284.js. Confirmed on both local peers (:7509and:7530— distinctfreenetprocesses) and on the publictry.freenet.org.fdevpublished to one node, so the other received it over the network rather than locally.chat_delegate.wasm9daa93c1…,room_contract.wasm9e311226…in bothui/public/contracts/andcli/contracts/). No migration entry needed; the delegate key is unchanged. This is the check that matters most — a stray full build here would re-key the delegate and orphan every user's rooms.Risk
Mechanical single-line counter change; no code. Skip-tier per the review rules — deterministic CI still gates it.
[AI-assisted - Claude]