Changes from the 0.16.1 branch (rerun-io#6457)

### What

Stuff from rerun-io#6447 that needs to also land on `main`.

### Checklist
* [x] I have read and agree to [Contributor
Guide](https://github.com/rerun-io/rerun/blob/main/CONTRIBUTING.md) and
the [Code of
Conduct](https://github.com/rerun-io/rerun/blob/main/CODE_OF_CONDUCT.md)
* [x] I've included a screenshot or gif (if applicable)
* [x] I have tested the web demo (if applicable):
* Using examples from latest `main` build:
[rerun.io/viewer](https://rerun.io/viewer/pr/6457?manifest_url=https://app.rerun.io/version/main/examples_manifest.json)
* Using full set of examples from `nightly` build:
[rerun.io/viewer](https://rerun.io/viewer/pr/6457?manifest_url=https://app.rerun.io/version/nightly/examples_manifest.json)
* [x] The PR title and labels are set such as to maximize their
usefulness for the next release's CHANGELOG
* [x] If applicable, add a new check to the [release
checklist](https://github.com/rerun-io/rerun/blob/main/tests/python/release_checklist)!

- [PR Build Summary](https://build.rerun.io/pr/6457)
- [Recent benchmark results](https://build.rerun.io/graphs/crates.html)
- [Wasm size tracking](https://build.rerun.io/graphs/sizes.html)

To run all checks from `main`, comment on the PR with `@rerun-bot
full-check`.

CHANGELOG.md

@@ -2,6 +2,13 @@
 
 ## [Unreleased](https://github.com/rerun-io/rerun/compare/latest...HEAD)
 
+## [0.16.1](https://github.com/rerun-io/rerun/compare/0.16.0...0.16.1) - Bug fix - 2024-05-29
+- Don't log warnings when unknown clients connect over TCP [#6368](https://github.com/rerun-io/rerun/pull/6368)
+- Fix not being able to set time series' Y axis ranges from the UI [#6384](https://github.com/rerun-io/rerun/pull/6384)
+- Fix error when logging segmentation image [#6449](https://github.com/rerun-io/rerun/pull/6449)
+- Fix broken example source links in Viewer example list [#6451](https://github.com/rerun-io/rerun/pull/6451)
+
+
 ## [0.16.0](https://github.com/rerun-io/rerun/compare/0.15.1...0.16.0) - First configurable views - 2024-05-16
 
 ### ✨ Overview & highlights

RELEASES.md

@@ -60,13 +60,19 @@ If we are doing a patch release, we do a branch off of the latest release tag (e
    Note that `release-0.x` is _invalid_. Always specify the `y`, even if it is `0`,
    e.g. `release-0.15.0` instead of `release-0.15`.
 
-![Image showing the branch create UI. You can find the `new branch` button at https://github.com/rerun-io/rerun/branches](https://github.com/rerun-io/rerun/assets/1665677/becaad03-9262-4476-b811-c23d40305aec)
+   For minor release, the branch is typically created from `main`. For patch release, the branch is typically created
+   from the previous release's tag.
 
-Note: you do not need to create a PR for this branch -- the release workflow will do that for you.
+   ![Image showing the branch create UI. You can find the `new branch` button at https://github.com/rerun-io/rerun/branches](https://github.com/rerun-io/rerun/assets/1665677/becaad03-9262-4476-b811-c23d40305aec)
+
+   Note: you do not need to create a PR for this branch -- the release workflow will do that for you.
 
 3. ### If this is a patch release, cherry-pick commits for inclusion in the release into the branch.
 
-  When done, run [`cargo semver-checks`](https://github.com/obi1kenobi/cargo-semver-checks) to check that we haven't introduced any semver breaking changes.
+   When done, run [`cargo semver-checks`](https://github.com/obi1kenobi/cargo-semver-checks) to check that we haven't introduced any semver breaking changes.
+
+   :warning: Any commits between the last release's tag and the `docs-latest` branch should also be cherry-picked.
+   Otherwise, these changes will be lost when `docs-latest` is updated.
 
 4. ### Update [`CHANGELOG.md`](/CHANGELOG.md).
 
@@ -102,5 +108,12 @@ Note: you do not need to create a PR for this branch -- the release workflow wil
    The PR description will contain next steps.
 
    Note: there are two separate workflows running -- the one building the release artifacts, and the one running the PR checks.
-   You will have to wait for the [former](https://github.com/rerun-io/rerun/actions/workflows/release.yml) in order to get a link
-   to the artifacts.
+   You will have to wait for the [former](https://github.com/rerun-io/rerun/actions/workflows/release.yml) in order to get a link to the artifacts.
+
+7. ### Merge changes to `main`
+
+   For minor release, merge the release branch to `main`.
+
+   For patch release, manually create a new PR from `main` and cherry-pick the required commits. This includes at least
+   the `CHANLGE.log` update, plus any other changes made on the release branch that hasn't been cherry-picked in the
+   first place.