oops, meant this

Author: cristeigabriela

ADOPTERS.md

@@ -17,6 +17,7 @@ We're proud to be used by the most innovative teams around the world! If you're
 | [BforeAI](https://bfore.ai) | [User Story](https://metalbear.com/mirrord/stories/bfore-ai/) |
 | [Utila](https://utila.io) | [User Story](https://metalbear.com/mirrord/stories/utila/) |
 | [Savvy Security](https://www.savvy.security) | [User Story](https://metalbear.com/mirrord/stories/savvy/) |
+| [HM Courts & Tribunal Service](https://www.gov.uk/government/organisations/hm-courts-and-tribunals-service) | [Use Case](https://github.com/hmcts/civil-citizen-ui/blob/master/README.md#development--debugging-environment---preview-with-mirrord) | 
 
 \* Optional: link to a blog post, tweet, internal write-up, or leave blank.
 

CHANGELOG.md

@@ -8,6 +8,70 @@ This project uses [*towncrier*](https://towncrier.readthedocs.io/) and the chang
 
 <!-- towncrier release notes start -->
 
+## [3.174.0](https://github.com/metalbear-co/mirrord/tree/3.174.0) - 2025-11-20
+
+
+### Added
+
+- Added HM Courts & Tribunal Service to ADOPTERS.md.
+- Added a new option under `mirrord ci start` to run the binary and wait for it
+  to complete.
+
+
+### Changed
+
+- Allow an overlap in the configuration for `incoming.ports` and
+  `incoming.http_filter.ports`.
+
+
+### Fixed
+
+- Fixed minor edge case where intproxy might hit code that's supposed to be
+  unreachable and panic
+  [#intproxy-panic](https://github.com/metalbear-co/mirrord/issues/intproxy-panic)
+- Fixed a DNS regression that happens when user's DNS library bind their
+  outgoing
+  socket to unspecified address before send UDP message to the nameserver.
+
+## [3.173.2](https://github.com/metalbear-co/mirrord/tree/3.173.2) - 2025-11-18
+
+
+### Changed
+
+- Exclude `GOPATH` and `GOMODCACHE` from env fetched
+
+## [3.173.1](https://github.com/metalbear-co/mirrord/tree/3.173.1) - 2025-11-16
+
+
+### Internal
+
+- Add cleanup of unnecessary items in CI builder for docker builds.
+  [#add-cleanup-before-docker-build](https://github.com/metalbear-co/mirrord/issues/add-cleanup-before-docker-build)
+
+## [3.173.0](https://github.com/metalbear-co/mirrord/tree/3.173.0) - 2025-11-16
+
+
+### Changed
+
+- Update `experimental.non_blocking_tcp_connect` config default to `false`.
+
+
+### Fixed
+
+- Fixed the security advisories of the config's template engine by updating it
+  to the newest version
+  [#3657](https://github.com/metalbear-co/mirrord/issues/3657)
+
+
+### Internal
+
+- Fix the way release script gets workspace version.
+- Kubernetes-related packages have been removed from the devshell, they should
+  be installed system-wide instead.
+- Use the pip from the setup action, not the one preinstalled on the runner.
+- make CI workflow trigger for PRs targeted to `windows-support` branch
+  (windows main)
+
 ## [3.172.0](https://github.com/metalbear-co/mirrord/tree/3.172.0) - 2025-11-06
 
 

CONTRIBUTING.md

@@ -17,6 +17,7 @@ Make sure to take a look at the project's [style guide](STYLE.md).
 - [Adding new target types](#adding-new-target-types)
 - [Testing the release workflow](#testing-the-release-workflow)
 - [Architecture](#architecture)
+- [Release mirrord](#release-mirrord)
 
 # Getting Started
 
@@ -660,7 +661,7 @@ Add a changelog file in `changelog.d/` named `<identifier>.<category>.md`
 **Category:**
 Check `towncrier.toml` for available categories (`added`, `changed`, `fixed`, etc.) and choose the one that fits your change.
 
-## Architecture
+# Architecture
 
 A high level view of mirrord.
 
@@ -755,3 +756,27 @@ flowchart TB
     style Pod fill:#e6ffe6,stroke:#006600,stroke-width:2px
     style Binary fill:#f9f9f9,stroke:#333,stroke-width:2px
 ```
+
+# Release mirrord
+
+## Release PR
+
+1. Create a new branch named after the new version, e.g. `3.333.0`. This will trigger additional CI jobs.
+2. On the new branch, bump the workspace version in `Cargo.toml` and run `cargo update -w` to update `Cargo.lock`.
+3. Generate the changelog with: `towncrier build --version <new-version>`.
+4. Review the generated changelog and fix any issues or typos.
+5. Push the release branch and open a PR.
+
+**Note:** All the steps above can also be completed by running: `./scripts/release.sh 3.333.0`.
+Before running the script, ensure there are no uncommitted changes in your repository.
+
+## Create a new GitHub release
+
+1. After the release PR is merged, create a new GitHub release with a new tag. Use the new version for both 
+   the tag name and the release title. Use the changelog from the release PR as the release description, 
+   excluding the `Internal` section if present.
+
+   **Note**: Ensure the tag is attached to the release commit.
+
+2. Creating the release will trigger the `Release` workflow, which builds and publishes all artifacts, including images.
+3. When the `Release` workflow completes successfully, update the relevant environment variables in the analytics server.