Skip to content

Commit

Permalink
Announce upcoming repository rename (#909)
Browse files Browse the repository at this point in the history
Updated README.md to include a warning about the upcoming repository name change to 'nats.net.v1', along with adding a new detailed announcement file, REPO_RENAME.md. The changes are aimed at increasing clarity and consistency across the NATS .NET brand, and important action points for users have been highlighted.
  • Loading branch information
mtmk authored Jul 10, 2024
1 parent ec8fe87 commit db40092
Show file tree
Hide file tree
Showing 2 changed files with 29 additions and 0 deletions.
7 changes: 7 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,10 @@
### :mega: :warning: This repository will be renamed to `nats.net.v1` on Wednesday, July 17th, 2024

Please be prepared to update your references to the new name.
You can also read the [announcement](REPO_RENAME.md) for more information.

---

![NATS](https://raw.githubusercontent.com/nats-io/nats.net/main/documentation/large-logo.png)

# NATS - .NET V1 C# Client
Expand Down
22 changes: 22 additions & 0 deletions REPO_RENAME.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# This repository will be renamed to `nats.net.v1` on Wednesday, July 17th, 2024

We wanted to let you know about an upcoming rename to our NATS .NET GitHub repositories on Wednesday, July 17. Here's what's changing:

* V1 Current: `nats-io/nats.net` New: `nats-io/nats.net.v1`
* V2 Current: `nats-io/nats.net.v2` New: `nats-io/nats.net`

We're renaming them to enhance clarity and to help build a consistent NATS .NET brand.
This change is important to us because it helps prevent confusion for our developers and users,
especially new folks joining us. Plus, it supports our goal of growing the NATS .NET community.

We recommend using NATS .NET v2, but please rest assured that we will continue to support and maintain v1 as usual.

We'll be making these updates around 1 PM ET (GMT-5) on that day. The good news is that we don’t expect any
disruptions, as package delivery is handled through NuGet.

If you have bookmarks to the current repositories or their documentation (GitHub pages), please be prepared
to update them. GitHub will automatically redirect `nats-io/nats.net.v2` to `nats-io/nats.net`, but unfortunately,
it won't do the same for the v1 repository. Also, if you’ve forked these repositories, you'll need to update
your upstream remotes for Git.

Thank you for your understanding and continued support!

0 comments on commit db40092

Please sign in to comment.