Skip to content

release-notes-v5.1.0.md

Latest commit

 

History

History
69 lines (55 loc) · 3.97 KB

release-notes-v5.1.0.md

File metadata and controls

69 lines (55 loc) · 3.97 KB
Raw

v5.1.0 Release Notes

Note: This project's practice is to publish curated release notes directly in the GitHub Release for milestone versions (e.g. v5.0.0) — the CI pipeline then appends an auto-generated packaged-binaries table below them. This doc is kept in-repo as a durable, reviewable draft; its content is intended to be pasted into the v5.1.0 GitHub Release body when that release is cut.

🎉 First GA Release

v5.1.0 is the first generally available (GA) release of the Go-based Java Buildpack.

Per RFC-0050 (Java Buildpack Migration to Golang), the v5.0.x series was an experimental release intended to collect broad community feedback before committing to API/behavior stability. Since v5.0.0, one container type was removed (see "Removed since v5.0.0" below) and several bug fixes changed previously-buggy or inconsistent runtime behavior (see "Notable fixes since v5.0.0" below) — review both sections before upgrading.

v5.1.0 supersedes the experimental 5.0.x releases. The Ruby-based buildpack (4.x) is no longer receiving feature updates; operators are encouraged to migrate to v5.1.0 or later. See the Migration Guide for upgrade guidance, and RUBY_VS_GO_BUILDPACK_COMPARISON.md for a detailed Ruby vs. Go feature comparison.

Removed since v5.0.0

  • Spring Boot CLI container support was removed in v5.0.7 (8c1816ec, "Remove spring-boot-cli outdated container"). It was still present in v5.0.0–v5.0.6. Applications previously detected and run via the Spring Boot CLI container (executable Groovy scripts with the spring-boot-cli runtime) are no longer supported — this was not called out in a prior release's notes. If your application relies on this, stay on v5.0.0–v5.0.6/v4.x or migrate to a supported container (e.g. package as a Spring Boot fat JAR).

Notable fixes since v5.0.0

Scanning commits between v5.0.0 and 86056b23 (main, as of this writing) shows no other intentionally-breaking API/config changes (no other removed frameworks, no default-value flips beyond what v5.0.0 already announced). However, several bug fixes changed previously-buggy or inconsistent runtime behavior. These are fixes "for the better" (bringing behavior in line with intent), but some upgrading apps could still observe a difference:

  • Fixed JBP_CONFIG_JAVA_MAIN not taking effect when the app is detected as Spring Boot — silently-ignored config now applies.
  • Fixed SERVER_PORT/$PORT injection for the Spring Boot JAR, Spring Boot CLI, and generic profile.d scripts (previously not shell-expanded correctly).
  • Fixed LoadConfig reading the wrong JBP_CONFIG_*_JRE vendor prefix — configs could previously silently apply to the wrong JRE vendor.
  • Restricted -XX:ActiveProcessorCount to HotSpot JREs only (previously applied incorrectly to non-HotSpot JREs like IBM/OpenJ9).
  • Changed Tomcat's server.xml to set allowSchemeMismatch=true.
  • Fixed multiple Tomcat context-path/ROOT.xml/WAR-filename XML-escaping issues — changes the generated Tomcat context descriptors for non-root context paths.
  • Fixed multiple JAVA_OPTS/USER_JAVA_OPTS assembly-script quoting/escaping issues (multiline values, $DEPS_DIR/$HOME substitution, bash 5.1 compatibility).
  • Clarified/fixed Java-version-detection fallback-to-default behavior.

💬 Feedback Welcome

Try it out and report any issues or unexpected behaviour: