Repository navigation
Conversation
|
This PR does not match any of the 1 configured review trigger rule. |
cameri
force-pushed
the
changeset-release/main
branch
from
October 25, 2026 01:19
87e046b to
519967a
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
nostream@3.8.1
Patch Changes
#972
a46ae06Thanks @chappie-daemon! - fix(compose): keep dynamic container addresses off the static onesdocker-compose.ymlpinsnostream,nostream-dbandnostream-cacheto10.10.10.2–.4, but dynamic allocation drew from the bottom of the same/24. The observability stack has no dependency that orders it afternostream, sootel-collectorcould be given.2andnostreamthen failed to start withAddress already in use— most reliably after a host reboot, when the daemon starts containers in arbitrary order.Dynamic allocation is now confined to
10.10.10.128/26. The subnet and gateway are unchanged, so10.10.10.1stays the trusted proxy, and the overlay pins (.5,.252,.253) stay outside the pool.