Skip to content

Changelog and version bump for 4.9.0 #458

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

Merged
absurdfarce merged 1 commit into from
Apr 24, 2026
+23 −4
Merged

Changelog and version bump for 4.9.0 #458

Show file tree
Hide file tree
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
19 changes: 19 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,24 @@
# ChangeLog - DataStax Node.js Driver

## 4.9.0

2026-04-23

This release marks the first release of the driver under the Apache Software
Foundation, following its donation from DataStax.

### Features

- [NODEJS-692] - Add Node.js v24 support
- [CASSNODEJS-2] - Update CONTRIBUTING.md after ASF donation, drop Node.js 18 support
- [CASSNODEJS-4] - Update DRIVER_NAME after donation to ASF
- [CASSNODEJS-3] - Public CI after Donation

### Bug fixes
- [PR #432] - Fix retry on socket error
- [NODEJS-693] - Remove broken jsdoc from 4.8.0
- [NODEJS-691] - Fix generated timestamp on retry

## 4.8.0

2025-02-20
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "cassandra-driver",
"version": "4.8.0",
"version": "4.9.0",
"description": "Apache Cassandra Node.js Driver",
"author": "Apache Software Foundation",
"keywords": [
Expand Down Expand Up @@ -54,4 +54,4 @@
"engines": {
"node": ">=20"
Copy link
Copy Markdown
Contributor

@absurdfarce absurdfarce Apr 23, 2026

Choose a reason for hiding this comment

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

So, this is a little bit of a weird one.

node.js 20.x is scheduled to go end-of-life on 4/30/26. As of this writing that's in the future but by the time we get the release staged, voted on and actually done it will very likely be after 4/30.

So I guess I'm wondering... should we continue support 20.x? By a strict understanding of our "only support what's not EOL" policy we shouldn't. That said we've already tested against 20.x... and it'll only just be EOL by the time we release it.

I think we're prolly good to keep this as >= 20... but it seemed worth raising as a question.

Copy link
Copy Markdown
Contributor Author

@SiyaoIsHiding SiyaoIsHiding Apr 24, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

Nobody says we shouldn't support an EOL version. We had been supporting Node.js 18 which has been EOL for a long time. Java driver also has been supporting JAVA 8 forever. I don't think it's a problem that we support Node.js 20.

Copy link
Copy Markdown
Contributor

@jorgebay jorgebay Apr 24, 2026

Choose a reason for hiding this comment

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

I'm +1 on supporting EOL versions for some time. It takes some time for users to upgrade :)

Copy link
Copy Markdown
Contributor

@absurdfarce absurdfarce Apr 24, 2026

Choose a reason for hiding this comment

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

We can discuss more but in general the drivers only support platforms/runtime that aren't EOL at the time of release. We don't do that for the Java driver but honestly that's a problem with the Java driver... we should be way better about that there.

}
}
}