-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Release 9.2.0 (#3134) #3137
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
Release 9.2.0 (#3134) #3137
Conversation
* Release 9.2.0 * update release notes
🔍 Preview links for changed docs |
| * Add 3.14 to CI builds ([#3103](https://github.com/elastic/elasticsearch-py/pull/3103)) | ||
| * Drop Python 3.9 support ([#3114](https://github.com/elastic/elasticsearch-py/pull/3114)) | ||
|
|
||
| ## 9.1.2 (2025-10-28) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering, is this useful to add in the main branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 9.1.2 change logs? When we branch 9.3 we'd want those to be included, I think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having entries appear twice doesn't seem very useful to me, but the Elasticsearch release notes appear to do it anyway: https://www.elastic.co/docs/release-notes/elasticsearch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see a way around it. To me it is more important to document the changes that went into each release, because people are only going to read the entries for the release they are interested in.
Co-authored-by: Quentin Pradet <quentin.pradet@gmail.com>
Release 9.2.0
update release notes