Skip to content

nats upgrade from 2.x.x to 3.x.x #15050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
mrosm20 opened this issue Apr 30, 2025 · 3 comments
Closed
1 task done

nats upgrade from 2.x.x to 3.x.x #15050

mrosm20 opened this issue Apr 30, 2025 · 3 comments

Comments

@mrosm20
Copy link

mrosm20 commented Apr 30, 2025

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe it

Is there a timeline to update nestjs microservices to the latest major version for nats. the packages have changed from nats to these
"@nats-io/jetstream": "^3.0.0-35",
"@nats-io/kv": "^3.0.0-29",
"@nats-io/nats-core": "^3.0.0-48",
"@nats-io/services": "^3.0.0-23",
"@nats-io/transport-node": "^3.0.0-33",

Describe the solution you'd like

upgrade nats packages

Teachability, documentation, adoption, migration strategy

upgrade nats packages

What is the motivation / use case for changing the behavior?

upgrade nats packages

@mrosm20 mrosm20 added needs triage This issue has not been looked into type: enhancement 🐺 labels Apr 30, 2025
@kamilmysliwiec
Copy link
Member

AFAIK a stable release of nats v3 was released a few weeks ago - let's give it some time to settle.

@jdinsel-xealth
Copy link

Has enough time elapsed?

@micalevisk micalevisk removed the needs triage This issue has not been looked into label May 23, 2025
@kamilmysliwiec
Copy link
Member

Let's track this here #15190

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

No branches or pull requests

4 participants