[dependabot]

Bumps github.com/nats-io/nats.go from 1.54.0 to 1.55.0.

Release notes

Sourced from github.com/nats-io/nats.go's releases.

Release v1.55.0

Changelog

This is the biggest nats.go release in a long time: 47 changes with more than half of them coming from 18 external contributors - thank you all!

Most of this release is a robustness effort. Nearly 30 bug fixes address deadlocks, goroutine and timer leaks, data races and stalls in reconnect and drain handling, pull and ordered consumers, async publish and service API. It also adds the FetchMaxBytes() option and Conn.RemoteAccount().

ADDED

• Core NATS:
  • Conn.RemoteAccount() and ServerInfo.RemoteAccount exposing the account the client is bound to (#2156)
• JetStream:
  • FetchMaxBytes() option to limit both the number of messages and total bytes in a single Fetch() request. Thanks @​manenim for the contribution (#2198)
  • StreamInfo.Domain, StreamInfo.Alternates, StreamState.Lost, StreamSourceInfo.External and StreamSourceInfo.Error in stream info (#2168)
  • ErrStreamMessageExceedsMaximum for JetStream error code 10054, returned when a message exceeds the stream's MaxMsgSize. Thanks @​matehsan for the contribution (#2110)

FIXED

• Core NATS:
  • ForceReconnect() called while already reconnecting disabling ReconnectWait and custom reconnect delays, so the client dialed in a tight loop. Thanks @​Arsen302 for the contribution and @​MokiMeow for the diagnosis and test (#2179)
  • Connection closing for good instead of reconnecting after a partial write left a truncated message on the wire (#2169)
  • Connection status listeners losing an unread event and being unregistered when the next status was sent (#2193)
  • Message headers not counted against subscription pending byte limits, so header-heavy subscriptions could exceed the limit without reporting a slow consumer. Thanks @​Grivn for the contribution (#2200)
  • Requests interrupted by a reconnect returning ErrConnectionClosed instead of ErrDisconnected. Thanks @​AshSgDe29071999 for the contribution (#2129)
  • Default port added to the path instead of the host for server URLs with a path and no port, e.g. ws://host/nats. Thanks @​dannyshafer for the contribution (#2177)
  • Close() during Drain() flipping the closed connection back to DRAINING_PUBS and flushing on it. Thanks @​Kshot3000 for the contribution (#2163)
  • Drain() waiting for the full DrainTimeout when the connection was closed mid-drain (#2171)
  • IsSystemAccount() reset to false by async INFO updates, such as cluster topology changes or lame duck mode (#2156)
• JetStream:
  • Pull consumer Consume() and Messages() deadlocking on Stop() or Drain() while buffered messages were still being delivered. Thanks @​clwluvw for the contribution (#2165)
  • Messages() iterator goroutines leaking after the connection is closed. Thanks @​clwluvw for the contribution (#2166)
  • Heartbeat timer and status listener left running when Consume() ends because the connection was closed. Thanks @​clwluvw for the contribution (#2164)
  • Messages() iterator returning ErrMsgIteratorClosed instead of the remaining buffered messages when Next() raced with Drain() (#2188)
  • Pull consumer with StopAfter stalling until the missed heartbeat check (30s by default) after a pull expired. Thanks @​huynguyen7 for the contribution (#2208)
  • Ordered consumer with StopAfter hanging on Stop()/Drain(), delivering too many or too few messages, or panicking after a consumer reset. Thanks @​clwluvw for the contribution (#2167)
  • Ordered consumer Fetch(), Next() and FetchBytes() blocking forever after returning ErrOrderedConsumerConcurrentRequests, and FetchNoWait() restarting from the beginning of the stream (#2211)
  • Ordered consumer Consume() and Messages() using the 15s pull consumer heartbeat instead of the 5s ordered default, so a stalled consumer was reset after ~30s instead of ~10s. Thanks @​arminazimi for the contribution (#2182)
  • PublishAsync() exceeding WithPublishAsyncMaxPending() under concurrent calls. Thanks @​ShravanthReddy for the contribution (#2126)
  • Async publish error callbacks for messages pending during a reconnect delayed until the publisher shut down. Thanks @​H-XX-D for the contribution (#2150)
  • Data race between Info() and CachedInfo() on streams and consumers. Thanks @​vulragrag-star for the contribution (#2152)
  • Reusing the same KeyValueConfig.Sources for several KeyValue buckets carrying the first bucket's subject transform into the next ones, so their reads returned ErrKeyNotFound. Thanks @​zhechen-cs for the contribution (#2190)
  • Object Store GetFile() leaving trailing bytes of an existing destination file when downloading a shorter object. Thanks @​zhechen-cs for the contribution (#2197)
• Legacy JetStream:
  • Async publish error callbacks for messages pending during a reconnect delayed until the publisher shut down. Thanks @​H-XX-D for the contribution (#2150)
  • KeyValue Create() and Update() on a cross-domain mirrored bucket failing with nats: no response from stream. Thanks @​spicysharkco for the contribution (#2203)
  • Object Store GetFile() leaving trailing bytes of an existing destination file when downloading a shorter object. Thanks @​zhechen-cs for the contribution (#2197)
• Service API:
  • Panic in AddService() on a closed connection (#2154)
  • Panic with send on closed channel when callbacks were queued during Stop() (#2173)
  • Service stopping on async errors from unrelated subscriptions with overlapping subjects. Async errors are now matched by subscription, recorded in endpoint stats and passed to ErrorHandler, and only a closed connection stops the service (#2174)

... (truncated)

Commits

• 6068694 Release v1.55.0 (#2214)
• 063b4ad [FIXED] Honor ReconnectWait after ForceReconnect during reconnect (#2179)
• 0a4cfc1 [ADDED] JetStream: stream alternates, lost data, source external/error (#2168)
• c3830a0 [IMPROVED] Document default MaxAckPending for legacy JetStream subscriptions ...
• 2560ee4 [IMPROVED] Avoid per-message metadata allocations in JetStream consumers (#2212)
• 8afc207 [FIXED] Ordered consumer Fetch deadlock and FetchNoWait redelivery (#2211)
• d1936d7 [FIXED] Correct StopAfter pending accounting for pull consumers (#2208)
• b431a07 [FIXED] micro: service and endpoint metadata can be changed after it is set (...
• ef8ce42 [FIXED] micro: Reset clears the endpoint queue group in stats (#2195)
• e28f7be [FIXED] Connection status listeners losing unread events (#2193)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ThomasK33]

@codex review

[ThomasK33]

@codex security review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-26T21:34:47.718674Z	75c4616	Manual request
🔒 Security Review	✅ Completed 2026-10-26T21:37:20.667282Z	75c4616	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: 75c4616309

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

🛡️ Codex Security Review

Security review completed. No security issues were found in this pull request.

Reviewed commit: 75c4616309

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.