Skip to content

Releases: helidon-io/helidon

3.2.4

01 Dec 17:38
Compare
Choose a tag to compare

This is a bugfix release of Helidon and is recommended for all users of Helidon 3. Helidon 3 requires Java 17 or newer.

CHANGES

For a list of changes please see the Helidon 3.2.4 CHANGELOG.

4.0.1

27 Nov 22:43
Compare
Choose a tag to compare

This release contains bugfixes and ehancements and is recommended for all users of Helidon 4.

Java 21 is required to use Helidon 4.0.1.

Notable Changes

  • Added PROXY protocol support to Helidon WebServer
  • WebServer performance improvements
  • CorsConfig.Builder.enabled() now returns an Optional<Boolean> instead of boolean. This change was required to fix a CORS issue and we expect the number of users impacted by this change to be small.

CHANGES

For a list of changes please see the Helidon 4.0.1 CHANGELOG.

3.2.3

26 Oct 19:57
Compare
Choose a tag to compare

This is a bugfix release of Helidon and is recommended for all users of Helidon 3. Helidon 3 requires Java 17 or newer.

CHANGES

For a list of changes please see the Helidon 3.2.3 CHANGELOG.

2.6.4

26 Oct 19:56
Compare
Choose a tag to compare

This is a bugfix release of Helidon and is recommended for all users of Helidon 2. Helidon 2 requires Java 11 or newer.

CHANGES

For a list of changes please see the Helidon 2.6.4 CHANGELOG.

4.0.0

24 Oct 00:36
Compare
Choose a tag to compare

We are pleased to announce the release of Helidon 4.0.0. The big news in Helidon 4.0.0 is the introduction of Helidon Níma -- a ground up webserver implementation based on JDK Project Loom virtual threads. With Helidon 4 you get the high throughput of a reactive server with the simplicity of thread-per-request style programming.

The Helidon SE API in 4.0.0 has changed significantly from Helidon 3. The use of virtual threads have enabled these APIs to change from asynchronous to blocking. This results in much simpler code that is easier to write, maintain, debug and understand. Existing Helidon SE code will require modification to run on these new APIs. For more information see the Helidon SE Upgrade Guide.

Helidon 4 supports MicroProfile 6. This means your existing Helidon MP 3.x applications will run on Helidon 4 with only minor modifications. And since Helidon’s MicroProfile server is based on the new Níma WebServer you get all the benefits of running on virtual threads. For more information see the Helidon MP Upgrade Guide.

New to Helidon? Then jump in and get started.

Java 21 is required to use Helidon 4.0.0

CHANGES

For a list of changes please see the Helidon 4.0.0 CHANGELOG.

4.0.0-RC1

28 Sep 17:41
Compare
Choose a tag to compare
4.0.0-RC1 Pre-release
Pre-release

This is the first RC build of Helidon 4.0.0 and is intended as a preview release only. Do not use this release in production. It is suitable only for experimentation. APIs are subject to change. Documentation is incomplete. And some functionality is experimental.

The big news in Helidon 4.0.0 is the introduction of Helidon Nima -- a ground up webserver implementation based on JDK Project Loom virtual threads. With Helidon 4 you get the high throughput of a reactive server with the simplicity of thread-per-request style programming.

Java 21 is required to use Helidon 4.0.0-RC1.

Notable Changes

  • Major refactoring of APIs is complete.
  • HTTP/2 support is complete and in general WebServer and WebClient are feature complete

CHANGES

For a full list of changes please see 4.0.0-RC1 CHANGELOG

4.0.0-M2

08 Sep 22:58
Compare
Choose a tag to compare
4.0.0-M2 Pre-release
Pre-release

This is the second Milestone build of Helidon 4.0.0 and is intended as a preview release only. Do not use this release in production. It is suitable only for experimentation. APIs are subject to change. Documentation is incomplete. And some functionality is experimental.

The big news in Helidon 4.0.0 is the introduction of Helidon Nima -- a ground up webserver implementation based on JDK Project Loom virtual threads. With Helidon 4 you get the high throughput of a reactive server with the simplicity of thread-per-request style programming.

Java 21 is required to use Helidon 4.0.0-M2.

Notable Changes

  • Java 21 is required for 4.0.0-M2
  • Finish integration of Níma WebServer into Helidon 4. This means that the nima Java package has been assimilated into the base Helidon packages.
  • Helidon SE apis are significantly refactored to optimize imperative/blocking use cases.
  • Numerous enhancements to WebServer and WebClient to achieve feature parity with Helidon 3.

The above is work-in-progress. There are still some gaps, and APIs are subject to change.

CHANGES

For a full list of changes please see 4.0.0-M2 CHANGELOG

2.6.3

07 Sep 23:22
Compare
Choose a tag to compare

This is a bugfix release of Helidon. It is recommended for all users of Helidon 2.

CHANGES

  • Config: Fix SeConfig.asMap to not truncate keys 7493
  • OCI: Make OciMetricsDataTest.beforeEach non private 7332
  • Security: Fix get in evictable cache, as it did not update last accessed timestamp 7465
  • Security: Fix google-login behind proxy 7473
  • Security: JWK signature now follows P1363 pair format 7197
  • Security: Security context not overridden 7511
  • WebServer Replace deprecated socket(String) on namedSocket(String) from ServerConfiguration 7325
  • WebServer: Correctly handle IPv6 addresses for requested URI. 7479
  • WebServer: fix out of order chunk 7460
  • Dependencies: Upgrade EclipseLink and ByteBuddy for Java 21 7495
  • Dependencies: Upgrade grpc-java to 1.57.1 and remove repackaging of io.grpc 7300
  • Dependencies: upgrade okio to 3.4.0 7259
  • Docs: fix various issues 7526
  • Examples: Add Docker and Kubernetes files to bare-* and database-* (2.x) 7290
  • Examples: Refactor TODO app examples to not use NodeJS/NPM 7467
  • Examples: Remove license from generated files 7233 7250
  • Examples: Use JSON-B instead of JSON-P in MP quickstarts 7523

4.0.0-M1

18 Jul 21:30
Compare
Choose a tag to compare
4.0.0-M1 Pre-release
Pre-release

This is the first Milestone build of Helidon 4.0.0 and is intended as a preview release only. Do not use this release in production. It is suitable only for experimentation. APIs are subject to change. Documentation is incomplete. And some functionality is experimental and not fully tested.

The big news in Helidon 4.0.0 is the introduction of Helidon Nima -- a ground up webserver implementation based on JDK Project Loom virtual threads.

Java 20 is required to use Helidon 4.0.0-M1.

Any easy way to get started with Helidon 4.0.0-M1 is using the helidon CLI

helidon init --version 4.0.0-M1

Notable Changes

  • Removed the Helidon Reactive WebServer and WebClient that were based on Netty as we fully commit to new implementations based on virtual threads that have a blocking style API (Project Níma).
  • Converted other modules with reactive APIs to blocking style APIs. The io.helidon.common.reactive APIs will stay as general purpose reactive utilities and operators
  • Introduced Helidon Injection, a deterministic, source-code-first, compile time injection framework
  • Upgraded MicroProfile support to MicroProfile 6 and Jakarta 10 Core Profile running on the Níma WebServer
  • Started adoption of Helidon Builders, a builder code generation framework

The above is work-in-progress. There are still missing features, and APIs are undergoing change. For example
the Grpc implementation is limited and MicroProfile Grpc support is temporarily absent.

2.6.2

12 Jul 23:13
Compare
Choose a tag to compare

This is a bugfix release of Helidon. It is recommended for all users of Helidon 2.

CHANGES

  • WebServer: Response should not be chunked if there is no entity 6916
  • WebServer: Avoid reflecting back user data coming from exception messages. 6981
  • Dependencies: Upgrade graphql to 18.6 6975 6939
  • Dependencies: Upgrade jackson to 2.15.2 7126
  • Dependencies: Upgrade netty, grpc, guava, snappy-java and use slim neo4j driver 7085
  • Dependencies: Upgrade to Jersey 2.40 7150
  • Docs: wls-helidon integration for 2.x 6946
  • Test: CipherSuiteTest intermittent failure 6948
  • Test: Use Hamcrest assertions instead of JUnit in integrations/cdi/jpa-cdi- 5252