Skip to content

Update CHANGELOG to mark v2.3.0 as released #6677

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.

Sign up for GitHub

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
0xbrw wants to merge 1 commit into from
Closed

Update CHANGELOG to mark v2.3.0 as released #6677

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Release channels have their own copy of this changelog:
* [stable - v2.1](https://github.com/anza-xyz/agave/blob/v2.1/CHANGELOG.md)

<a name="edge-channel"></a>
Copy link
Copy Markdown

@t-nelson t-nelson Jun 23, 2025

Choose a reason for hiding this comment

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

is 2.3 still supposed to point to edge?

Copy link
Copy Markdown

@steviez steviez Jun 23, 2025

Choose a reason for hiding this comment

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

In previous release, it seems we landed the "update changelog" PR prior to branching. Ie, #6424 came in after we cut v2.3 if I'm not mistaken.

So, I think just BP'ing 6424 would keep us consistent with past releases

Copy link
Copy Markdown

@t-nelson t-nelson Jun 23, 2025

Choose a reason for hiding this comment

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

yeah wasn't sure if BPing master update was right path or just deleting the channel indications

Copy link
Copy Markdown

@steviez steviez Jun 23, 2025

Choose a reason for hiding this comment

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

Yeah, I could see just deleting the channel indications as v2.3 does go from beta to stable at some point, and keeping it noted here is just another thing to remember to update get out of date.

Copy link
Copy Markdown

@t-nelson t-nelson Jun 24, 2025

Choose a reason for hiding this comment

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

@willhickey any guidance here?

## 2.3.0 - Unreleased
## 2.3.0

### Validator

Expand Down