Release 0.3.0 - #64
Merged
Merged
Conversation
A minor bump rather than a patch, because `DEFAULT_SERVER` is gone: a `drop` upgrading into this finds `--transport relay` erroring where it used to connect, and `auto` no longer falling back. That is not a promise a patch release is allowed to break. - `drop`, `drop send` and `drop recv`, typed on their own in a terminal, open an interface instead of printing usage or asking for an argument. Anything given on the command line, and anything not a terminal, behaves exactly as before. - No default relay. `--server` and `DROP_SERVER` have no compiled-in value, `--transport relay` without one is an error, and `auto` without one is peer-to-peer that says so. decisions.md entry 16. - `DROP_RENDEZVOUS_RELAY` and `DROP_RENDEZVOUS_BOOTSTRAP` point the direct path's rendezvous at infrastructure a deployment runs itself. decisions.md entry 15. - A network lab under `netlab/` runs the real binaries across constructed topologies. One of its eight tests is a known failure, recorded rather than hidden. The release workflow refuses a tag that disagrees with this manifest, which is why the bump is its own commit ahead of the tag. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Version bump only. The release workflow refuses a tag that disagrees with the manifest, so this lands before
v0.3.0is cut.0.3.0, not 0.2.1. A patch release promises nothing you depend on changed, and
DEFAULT_SERVERis gone — anyone upgrading finds--transport relayerroring where it used to connect, andautono longer falling back.What is in it
drop sendanddrop recvopen an interface when typed on their own in a terminal. Anything given on the command line, and anything not a terminal, behaves exactly as before.--serverandDROP_SERVERhave no compiled-in value.decisions.mdentry 16, superseding entry 8.DROP_RENDEZVOUS_RELAYandDROP_RENDEZVOUS_BOOTSTRAP.decisions.mdentry 15.netlab/, with one known failing topology recorded rather than hidden.Not in it
The browser client is still here. Its removal is on
chore/remove-web, which is unfinished and unmerged —src/lib.rsstill servesweb/dist,crypto-wasmis still a workspace member, andinstall.shstill lives only atweb/public/install.sh, whichrelease.ymlsparse-checks-out to publish. That last point is why the removal must not merge before it relocates the installer.🤖 Generated with Claude Code