Release notes for 0.107.0

[sholderbach]

Please add your new features and breaking changes to the release notes
by opening PRs against the release-notes-0.107.0 branch.

TODO

• PRs that need to land before the release, e.g. deprecations or removals
• add the full changelog
• categorize each PR
• write all the sections and complete all the TODOs

[ItsHarper]

I've opened #2027 to fix a mistake in this PR

[ItsHarper]

Would it make more sense to list all of the endianness-related additions next to each other?

I forgot that one of them was a breaking change.

[ItsHarper]

The "http subcommands now keep track of redirects" section seems to have a copy/paste that included some control codes or something.

Edit: same for the section about into binary

Edit: OK I knew it wasn't like that before (this was intentionally changed in 88f62b5). I assume these will get rendered correctly on the website? It's quite unfortunate that it makes the code snippets unreadable with the GitHub viewer (especially since there's no website preview). What was the goal of this change?

[ItsHarper]

The command that should be "something resembling an HTTP server" seems incomplete (it literally ends with a pipe and doesn't mention the port number)

[132ikl]

I assume these will get rendered correctly on the website? It's quite unfortunate that it makes the code snippets unreadable with the GitHub viewer (especially since there's no website preview). What was the goal of this change?

It's so that we can get nice syntax highlighting on the blog, including for results where the stock syntax highlighting doesn't cut it. This is especially when we would otherwise have to use an image, like this example which needs real syntax highlighting to make sense:

but it's still a lot nicer for things where we would otherwise have no syntax highlighting at all, like errors:

[132ikl]

The command that should be "something resembling an HTTP server" seems incomplete (it literally ends with a pipe and doesn't mention the port number)

thanks, looks like i messed up when editing the release notes summary in the PR, this should be fixed now