Skip to content

Conversation

@caspervonb
Copy link
Collaborator

Partially resolves #760

@caspervonb caspervonb changed the title Add first_seq support to StreamConfig Add first_seq support to StreamConfig Nov 7, 2025
@caspervonb caspervonb requested a review from Copilot November 7, 2025 10:42
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds support for the first_seq stream configuration parameter, which allows specifying a custom starting sequence number when creating a JetStream stream. This feature was introduced in nats-server 2.10.0.

  • Added first_seq optional field to StreamConfig class in the API
  • Implemented comprehensive test coverage for the first_seq functionality

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
nats/src/nats/js/api.py Added first_seq optional field to StreamConfig with appropriate documentation indicating it was introduced in nats-server 2.10.0
nats/tests/test_js.py Added test_stream_first_seq test method to verify stream creation with custom starting sequence, message publishing with correct sequence numbers, and message retrieval by sequence

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing StreamConsumerLimits props from StreamConfig

2 participants