Skip to content

Conversation

@miguelgrinberg
Copy link
Contributor

  • Release 9.2.0

  • update release notes

* Release 9.2.0

* update release notes
@github-actions
Copy link

github-actions bot commented Oct 28, 2025

🔍 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)
Copy link
Member

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?

Copy link
Contributor Author

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?

Copy link
Member

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

Copy link
Contributor Author

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.

miguelgrinberg and others added 2 commits October 29, 2025 10:01
@miguelgrinberg miguelgrinberg merged commit 99155fe into elastic:main Oct 29, 2025
15 checks passed
@miguelgrinberg miguelgrinberg deleted the bring-release-9.2.0 branch October 29, 2025 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants