Changelogs for strelaysrv and stdiscosrv?

Support
1

Hey folks,

I was wondering: for syncthing itself, changelogs are present, yet there are none for the discovery server or the relay server - at least not for the recent releases (see https://github.com/syncthing/discosrv/releases/tag/v1.8.0 and https://github.com/syncthing/relaysrv/releases/tag/v1.8.0).

It’s a bit of a gamble to run the new version without knowing what changed.

Cheers & Thanks, Thomas

2

Sometimes the changelog for syncthing mentions changes to the discovery/relay server (if corresponding issues were filed), but not always.

For the 1.8.0 release:

Relay server

Discovery server

  • To aid in TCP hole-punching, the discovery server now processes more port information about remote peers. In reverse-proxy setups the discovery server can’t normally see the client’s connection port. In order to support such setups, the discovery server now interprets a custom reverse proxy header “X-Client-Port”. See the docs and the corresponding PR.

Note: These changes were gathered by comparing 1.7.1 and 1.8.0. Since the discovery & relay servers only see irregular releases, there may be more (older) changes involved that I overlooked.

3

The main Syncthing changelog covers those as well, it’s just we don’t publish new binaries for them with every Syncthing release if they didn’t change. (Which is the norm.)

The changelog itself consists of resolved GitHub issues for the release in question. If something changed but there wasn’t an issue for it it doesn’t get into the changelog.

4

I see.

Especially this part is a bummer though. One has to to hope for everybody to always have an issue for a change. Makes sense, but leaves open the possibility of code changes without according changelog entrys.

Anyway, thanks for getting back!

Cheers, Thomas

5

We mention stuff worth mentioning in the changelogs, not every internal shuffle that has no meaning to users but is still a “code change”.

You are free to follow the commits that land in the main branch if you genuinely care about all “code changes”.

1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.