Add Nats-Expected-Last-Subject-Sequence-Subject#1007
Merged
Conversation
mtmk
deleted the
add-Nats-Expected-Last-Subject-Sequence-Subject-header
branch
December 2, 2025 11:28
mtmk
added a commit
that referenced
this pull request
Dec 11, 2025
* Add prioritized mode (#1011) * Add Publish Timeout on Disconnect (#1001) * Fix test flap (#1012) * Add test to promote mirrored to regular stream (#1008) * Add Nats-Expected-Last-Subject-Sequence-Subject (#1007) * Fix keyed NATS clients with configurations (#1006) * ensure NatsConnectionPool cannot overflow (#1005) * Fix stream config adjustments on update (#995) * Handel Unobserved Exceptions During Connection State Transitions (#999) * Added verification of the consumer sequence number for pull ordered consumers (#981) * Fix build warnings (#991) * Reduce closure allocations (#988)
Merged
mtmk
added a commit
that referenced
this pull request
Dec 11, 2025
* Add prioritized mode (#1011) * Add Publish Timeout on Disconnect (#1001) * Fix test flap (#1012) * Add test to promote mirrored to regular stream (#1008) * Add Nats-Expected-Last-Subject-Sequence-Subject (#1007) * Fix keyed NATS clients with configurations (#1006) * ensure NatsConnectionPool cannot overflow (#1005) * Fix stream config adjustments on update (#995) * Handel Unobserved Exceptions During Connection State Transitions (#999) * Added verification of the consumer sequence number for pull ordered consumers (#981) * Fix build warnings (#991) * Reduce closure allocations (#988)
This was referenced Dec 15, 2025
This was referenced Mar 2, 2026
This was referenced Jul 13, 2026
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
2 participants
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 pull request adds support for the
ExpectedLastSubjectSequenceSubjectoption to JetStream publish operations, allowing users to specify a subject filter (including wildcards) for expected last subject sequence checks. This enables more flexible conditional publishing based on the last sequence of a specific subject. The changes also include a new test to verify the correct behavior of this feature.JetStream publish options enhancements
ExpectedLastSubjectSequenceSubjectto theNatsJSPubOptsrecord, allowing users to specify a subject filter for expected last subject sequence checks.TryPublishAsync<T>andPublishConcurrentAsync<T>methods inNatsJSContext.csto include theNats-Expected-Last-Subject-Sequence-Subjectheader whenExpectedLastSubjectSequenceSubjectis set. [1] [2]Testing improvements
Publish_expected_last_subject_sequence_subject_testto verify that publishing with theExpectedLastSubjectSequenceSubjectoption works as expected, including handling of correct and stale sequence numbers.