Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(iroh-net): Switch to new iroh-relay route /relay instead of /derp #2441

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

matheus23
Copy link
Member

Split out from #2419

Splitting this out means we can deploy the relay changes one release in advance to the changes in the client.

Otherwise, we'd need to update the relays ASAP when we release 0.20, as clients will expect to be able to connect to the /relay route (which may not be deployed immediately after the release).

Description

  • Switches the client to connect to /relay instead of /derp.

Breaking Changes

None

Notes & open questions

Also a PR related to #2378

I allowed myself to add in another derive_more::Debug instance instead of a custom, outdated impl Debug, if that's okay with you 😁

Change checklist

  • Self-review.
  • Documentation updates if relevant.
  • Tests if relevant.
  • All breaking changes documented.

@matheus23 matheus23 added this to the v0.21.0 milestone Jul 2, 2024
@matheus23
Copy link
Member Author

matheus23 commented Jul 2, 2024

DO NOT MERGE YET

Or rather - merge after the 0.20 release was published.

Read this comment for the reasoning.
TLDR: We first publish changes to the relay to support the new /relay route with backwards compatibility in the 0.20 release, then we publish the changes to the client to make use of this new endpoint with the 0.21 release.

@matheus23
Copy link
Member Author

According to @Arqu the relays are now updated to 0.20.
We can merge this, unless we want to wait a bit with breaking changes due to the new release.

If nothing else comes up, I'll merge tomorrow (if I end up with enough time at a computer in Brussels).

@flub
Copy link
Contributor

flub commented Jul 10, 2024

Sounds good, let's merge!

@matheus23 matheus23 merged commit f4f1a89 into matheus23/relay-route Jul 11, 2024
24 checks passed
@matheus23
Copy link
Member Author

I don't really understand why the base branch didn't switch automatically here :/

github-merge-queue bot pushed a commit that referenced this pull request Jul 18, 2024
…f `/derp` (#2489)

Split out from #2419, copy of #2441, because I forgot to switch the base
branch 🙃

Splitting this out means we can deploy the relay changes one release in
advance to the changes in the client.

Otherwise, we'd need to update the relays ASAP when we release 0.20, as
clients will expect to be able to connect to the `/relay` route (which
may not be deployed immediately after the release).

## Description

- Switches the client to connect to `/relay` instead of `/derp`.

## Breaking Changes

None

## Notes & open questions

Also a PR related to #2378 

I allowed myself to add in another `derive_more::Debug` instance instead
of a custom, outdated `impl Debug`, if that's okay with you 😁

## Change checklist

- [X] Self-review.
- [X] Documentation updates if relevant.
- [X] Tests if relevant.
- [X] All breaking changes documented.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants