Thanks Julian, the date has been fixed (oversight on my part).

On 30/09/2025 10:23 am, Julian Hyde wrote:
Shouldn’t the release date on that page be 2025-09-30? It currently appears as 
2025-10-30. (Seems to be correct on the news page, 
https://calcite.apache.org/avatica/news/.)


On Sep 29, 2025, at 5:04 PM, Francis Chuang <[email protected]> wrote:

Thanks for catching that. There were 2 GitHub workflows running to publish the 
website and the latest commit completed earlier than the earlier commit, so the 
changes were overwritten [1].

I manually restarted the workflow on the latest commit, so the changes should 
be visible now.

[1] https://github.com/apache/calcite-site/commits/main/

On 30/09/2025 9:30 am, 我 wrote:
Thanks for Francis to release Calcite Avatica 1.27.0!
But the title of this link[1] has some wrong, currently it is 
"1.27.0/2025-10-XX".
[1] https://calcite.apache.org/avatica/docs/history.html#v1-27-0
At 2025-09-30 07:04:17, "Francis Chuang" <[email protected]> wrote:
The Apache Calcite team is pleased to announce the release of Apache
Calcite Avatica 1.27.0.

Avatica is a framework for building database drivers. Avatica defines a
wire API and serialization mechanism for clients to communicate with a
server as a proxy to a database. The reference Avatica client and server
are implemented in Java and communicate over HTTP. Avatica is a
sub-project of Apache Calcite.

Avatica 1.27.0 contains dependency upgrades, support for Gradle 8.14 and
support for MySQL unsigned types.

For a full list of changes, please see the release notes:

https://calcite.apache.org/avatica/docs/history.html#v1-27-0

The release is available here:

https://calcite.apache.org/avatica/downloads/avatica.html

We welcome your help and feedback. For more information on how to report
problems and get involved, visit the project website at:

https://calcite.apache.org/avatica/

or the Apache Calcite project website:

https://calcite.apache.org/

Thanks to everyone involved!

Francis Chuang, on behalf of the Apache Calcite team




Reply via email to