Skip to content

Commit 55210ca

Browse files
author
jbossorg-bot
committed
Published latest aggregated blog posts
1 parent f57e2d5 commit 55210ca

20 files changed

+107
-106
lines changed

src/content/posts-aggregator/1.json

+7-6
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,14 @@
11
{
2-
"title": "Quarkus 3.20 - new LTS version",
3-
"link": "https://quarkus.io/blog/quarkus-3-20-0-released/",
2+
"title": "Register now for KubeCon Japan in June",
3+
"link": "https://www.keycloak.org/2025/03/keycloak-kubecon25-japan-announce",
44
"author": [
55
{
6-
"name": "Guillaume Smet",
6+
"name": "Alexander Schwartz",
77
"avatar": null
88
}
99
],
10-
"date": "2025-03-26T00:00:00.000Z",
11-
"feed_title": "Quarkus",
12-
"content": "It is our pleasure to announce the release of Quarkus 3.20, which is our new LTS (Long Term Support) version. This version is built on the top of Quarkus 3.19 with some additional bugfixes. New features landed in , which was also released today. If you want to know more about our LTS policy, the is a must read. LTS releases are supported for 12 months. If you are coming from the previous LTS, Quarkus 3.15, there are a lot of exciting new features and we recommend reading the following announcements: * * * * UPDATE To update to Quarkus 3.20, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.20 LTS. If you are upgrading from 3.19, there’s nothing to do as 3.20 is the direct continuation of 3.19. If you are upgrading from the previous LTS, Quarkus 3.15, please refer to the following migration guides: * * * * * - this one is empty as 3.20 is the continuation of 3.19 Note that quarkus update should handle most of the heavy lifting for you, but there are still cases that should be handled manually and we recommend reading these migration guides carefully. WHAT’S NEW? PLATFORM COMPONENT UPGRADES CAMEL QUARKUS Camel Quarkus has been updated to 3.20.0. You can find everything you need to know about it in the . QUARKUS CXF Quarkus CXF 3.20 was released and is now available in . Check the release notes for more information about what is new in this release. AMAZON SERVICES The Amazon Services extensions have been upgraded to version 3.3.1. FULL CHANGELOG The core part of Quarkus 3.20.0 is a rebadged release of Quarkus 3.19.4 so nothing new here. CONTRIBUTORS The Quarkus community is growing and has now . Many many thanks to each and everyone of them. In particular for the 3.20 release, thanks to Ales Justin, Alexey Loubyansky, Andreas Maechler, Andy Damevin, Auri Munoz, brunobat, Clement Escoffier, cmoulliard, David Cotton, Dennis Kronbügel, Fabian, Foivos Zakkak, Georg Leber, George Gastaldi, Georgios Andrianakis, Guillaume Smet, Jakub Jedlicka, Jan Martiska, jcjveraa, Karm Michal Babacek, Katia Aresti, Ladislav Thon, Marco Belladelli, Martin Kouba, Martin Panzer, masecla22, Maximilian Zellhofer, melloware, Michal Maléř, Michal Vavřík, Ozan Gunalp, Peter Palaga, Phillip Kruger, Robert Stupp, Roberto Cortez, Rolfe Dlugy-Hegwer, Ryan Dens, Rüdiger zu Dohna, Sergey Beryozkin, shjones, Stephan Strate, Steve Hawkins, Stuart Douglas, Thomas Canava, w0pp, Welton Rodrigo Torres Nascimento, Willem Jan Glerum, xstefank, and Yoshikazu Nojima. The list is a bit smaller than usual as 3.20 only contains bugfixes on top of 3.19. COME JOIN US We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together! If you are a Quarkus user or just curious, don’t be shy and join our welcoming community: * provide feedback on ; * craft some code and ; * discuss with us on and on the ; * ask your questions on ."
10+
"date": "2025-03-27T00:00:00.000Z",
11+
"feed_title": "Keycloak Blog",
12+
"feed_avatar": "https://www.gravatar.com/avatar/87fe00619f08c241da8dfb23d907ffa2?s=50",
13+
"content": "This year is the first time there is a KubeCon in Japan, and the Keycloak project is excited to be part of it! Join us on June 16-17 2025 in Tokyo, Japan for this exciting event. Keycloak has a powerful community in Japan, and we have received several contributions in the past. There will be two talks about Keycloak (see below). TALKS AT KUBECON The schedule of KubeCon + CloudNativeCon Japan 2025 has been released, see below talks about Keycloak: * Monday June 16, 2025 11:30 - 12:00 JST Takashi Norimatsu, Hitachi & Marek Posolda, Red Hat * Tuesday June 17, 2025 14:50 - 15:20 JST Yoshiyuki Tabata, Hitachi, Ltd. We’re preparing for KubeCon Japan 2025 and can’t wait to connect with our community. Mark your calendars and join us. See you in Tokyo!"
1314
}

src/content/posts-aggregator/10.json

+6-6
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
{
2-
"title": "Narayana and its relationship to Red Hat middleware strategy",
3-
"link": "https://jbossts.blogspot.com/2025/03/narayana-and-its-relationship-to-red.html",
2+
"title": "Quarkus 3.15.4 released - LTS maintenance release",
3+
"link": "https://quarkus.io/blog/quarkus-3-15-4-released/",
44
"author": [
55
{
6-
"name": "Tom Jenkinson",
6+
"name": "Jan Martiška",
77
"avatar": null
88
}
99
],
10-
"date": "2025-03-17T16:55:00.001Z",
11-
"feed_title": "Narayana team blog",
12-
"content": " Hi everyone, You might have already seen that Red Hat announced significant changes to its middleware strategy last month (if not, please do check out the relevant “Red Hat Blog” article: Evolving our middleware strategy [1]) and so I want to speak a little to the change and its relevance to our Narayana project. As you may know, Narayana is a part of a number of Red Hat products, in particular Red Hat’s JBoss Enterprise Application Platform product and so this makes the strategic decision relevant to the Narayana project. That said, a key point in that article from the “Red Hat Blog” with regards to our Narayana project is that all transitioning Red Hat technology will remain open source and continue to follow an upstream-first development model. So as well as the technology still relying on being able to upstream-first (in projects like Narayana), it’s also that this upstream should remain open source (you can find what open source means at Red Hat over here [2]). Not only is the Narayana source code open source, but moreover its project operates in an open source manner, exhibiting the principles of open source and gratefully benefits from a healthy community of users and contributors. This will help us to keep innovating in the area of transactions as we move forwards. I will also take this opportunity to add a “Thank you” for being part of our Narayana community - I am excited to see the results of what we achieve together next! Tom Jenkinson [1] https://www.redhat.com/en/blog/evolving-our-middleware-strategy [2] https://www.redhat.com/en/about/open-source "
10+
"date": "2025-03-18T00:00:00.000Z",
11+
"feed_title": "Quarkus",
12+
"content": "Today, we released Quarkus 3.15.4, our next maintenance release for the 3.15 LTS stream. This release contains bugfixes and documentation improvements. It should be a safe upgrade for anyone already using 3.15. However, as part of fixing a security issue, one small potentially breaking change had to be applied: . This may affect you if you consume Netty allocator metrics. UPDATE To update to Quarkus 3.15, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update --stream=3.15 Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.15. FULL CHANGELOG You can get . COME JOIN US We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together! If you are a Quarkus user or just curious, don’t be shy and join our welcoming community: * provide feedback on ; * craft some code and ; * discuss with us on and on the ; * ask your questions on ."
1313
}

src/content/posts-aggregator/11.json

+6-7
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,13 @@
11
{
2-
"title": "Submit to KeyConf25 Japan Call-for-Papers!",
3-
"link": "https://www.keycloak.org/2025/03/keyconf-25-japan-call-for-papers",
2+
"title": "Narayana and its relationship to Red Hat middleware strategy",
3+
"link": "https://jbossts.blogspot.com/2025/03/narayana-and-its-relationship-to-red.html",
44
"author": [
55
{
6-
"name": "Alexander Schwartz",
6+
"name": "Tom Jenkinson",
77
"avatar": null
88
}
99
],
10-
"date": "2025-03-17T00:00:00.000Z",
11-
"feed_title": "Keycloak Blog",
12-
"feed_avatar": "https://www.gravatar.com/avatar/87fe00619f08c241da8dfb23d907ffa2?s=50",
13-
"content": "The call for papers for is now open! Submit your talks to the first-ever KeyConf in Japan. KeyConf 2025 Japan is a free half-day meetup in Tokyo, Japan on June 13 where the community of Keycloak gathers. It provides opportunities for technical lectures, growth, and networking with talks related Identity and Access Management (IAM) and Single Sign On (SSO). This event is designed to share insights from developers and maintainers, as well as the latest features, updates, and real-world use cases of Keycloak. Participants will have the valuable opportunity to interact directly with Keycloak experts and other users, deepening their knowledge. RELATED EVENTS A few days later, on June 16-17, takes place in Tokyo as well. The Keycloak team will be on-site for KubeCon Japan, so join us and a lot of other CNCF projects for this event as well. See you in Tokyo!"
10+
"date": "2025-03-17T16:55:00.001Z",
11+
"feed_title": "Narayana team blog",
12+
"content": " Hi everyone, You might have already seen that Red Hat announced significant changes to its middleware strategy last month (if not, please do check out the relevant “Red Hat Blog” article: Evolving our middleware strategy [1]) and so I want to speak a little to the change and its relevance to our Narayana project. As you may know, Narayana is a part of a number of Red Hat products, in particular Red Hat’s JBoss Enterprise Application Platform product and so this makes the strategic decision relevant to the Narayana project. That said, a key point in that article from the “Red Hat Blog” with regards to our Narayana project is that all transitioning Red Hat technology will remain open source and continue to follow an upstream-first development model. So as well as the technology still relying on being able to upstream-first (in projects like Narayana), it’s also that this upstream should remain open source (you can find what open source means at Red Hat over here [2]). Not only is the Narayana source code open source, but moreover its project operates in an open source manner, exhibiting the principles of open source and gratefully benefits from a healthy community of users and contributors. This will help us to keep innovating in the area of transactions as we move forwards. I will also take this opportunity to add a “Thank you” for being part of our Narayana community - I am excited to see the results of what we achieve together next! Tom Jenkinson [1] https://www.redhat.com/en/blog/evolving-our-middleware-strategy [2] https://www.redhat.com/en/about/open-source "
1413
}

src/content/posts-aggregator/12.json

+5-5
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
{
2-
"title": "Keycloak 26.1.4 released",
3-
"link": "https://www.keycloak.org/2025/03/keycloak-2614-released",
2+
"title": "Submit to KeyConf25 Japan Call-for-Papers!",
3+
"link": "https://www.keycloak.org/2025/03/keyconf-25-japan-call-for-papers",
44
"author": [
55
{
6-
"name": null,
6+
"name": "Alexander Schwartz",
77
"avatar": null
88
}
99
],
10-
"date": "2025-03-14T00:00:00.000Z",
10+
"date": "2025-03-17T00:00:00.000Z",
1111
"feed_title": "Keycloak Blog",
1212
"feed_avatar": "https://www.gravatar.com/avatar/87fe00619f08c241da8dfb23d907ffa2?s=50",
13-
"content": "To download the release go to . UPGRADING Before upgrading refer to for a complete list of changes. ALL RESOLVED ISSUES ENHANCEMENTS * Allow admin to disable automatic refresh of event views admin/ui * Upgrade to Infinispan 15.0.14 BUGS * Cannot fetch realm role that was renamed admin/api * When calling the token revoke endpoint multiple times with the same token, a database REVOKED-TOKEN constraint error is reported storage * Admin events: resource type filter does not work admin/ui * Unwanted placeholder texts in user profile fields admin/ui * KC_HTTPS_TRUST_STORE_TYPE not working dist/quarkus * The default setting of the client request object parameter is empty admin/ui"
13+
"content": "The call for papers for is now open! Submit your talks to the first-ever KeyConf in Japan. KeyConf 2025 Japan is a free half-day meetup in Tokyo, Japan on June 13 where the community of Keycloak gathers. It provides opportunities for technical lectures, growth, and networking with talks related Identity and Access Management (IAM) and Single Sign On (SSO). This event is designed to share insights from developers and maintainers, as well as the latest features, updates, and real-world use cases of Keycloak. Participants will have the valuable opportunity to interact directly with Keycloak experts and other users, deepening their knowledge. RELATED EVENTS A few days later, on June 16-17, takes place in Tokyo as well. The Keycloak team will be on-site for KubeCon Japan, so join us and a lot of other CNCF projects for this event as well. See you in Tokyo!"
1414
}

src/content/posts-aggregator/13.json

+7-6
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,14 @@
11
{
2-
"title": "Quarkus & Red Hat's evolving middleware strategy",
3-
"link": "https://quarkus.io/blog/quarkus-redhat-strategy/",
2+
"title": "Keycloak 26.1.4 released",
3+
"link": "https://www.keycloak.org/2025/03/keycloak-2614-released",
44
"author": [
55
{
6-
"name": "Max Rydahl Andersen",
6+
"name": null,
77
"avatar": null
88
}
99
],
10-
"date": "2025-03-13T00:00:00.000Z",
11-
"feed_title": "Quarkus",
12-
"content": "Over the past weeks, we’ve received questions about the that Red Hat’s Middleware engineering and product teams, which include Quarkus, are moving to IBM. We want to take this opportunity to acknowledge this change while reaffirming what has always been true: Quarkus is an open-source project driven by a global community of contributors, spanning companies, individuals, and open-source enthusiasts. From its inception, Quarkus has been shaped by real-world adoption across industries, with companies , leveraging Quarkus’s unmatched performance and developer joy in the Java ecosystem. We recently celebrated our , a testament to the strength of this diverse and thriving community. Speaking as Quarkus contributors employed by Red Hat and soon IBM, we love our project and intend to keep making it awesome. IBM and Red Hat have clearly communicated that the current and future contributions to Quarkus are a key component of the middleware strategy. IBM has already been an active contributor to Quarkus, and we look forward to increased contribution - alongside the many other individuals and companies who contribute, innovate, and drive Quarkus forward. Additionally, Quarkus is already on the path to becoming part of an open-source foundation, further ensuring its long-term independence and success as a truly community-driven project. The move to the foundation and the Red Hat/IBM move could look suspicious timing-wise, but the two are unrelated. We described our reasons in a , but if anything, this announcement reaffirms the importance of a foundation-hosted project for its stability. To our contributors and users: your involvement has always been what makes Quarkus thrive. Keep building, experimenting, and shaping the future of Java with us. -- The Quarkus Team"
10+
"date": "2025-03-14T00:00:00.000Z",
11+
"feed_title": "Keycloak Blog",
12+
"feed_avatar": "https://www.gravatar.com/avatar/87fe00619f08c241da8dfb23d907ffa2?s=50",
13+
"content": "To download the release go to . UPGRADING Before upgrading refer to for a complete list of changes. ALL RESOLVED ISSUES ENHANCEMENTS * Allow admin to disable automatic refresh of event views admin/ui * Upgrade to Infinispan 15.0.14 BUGS * Cannot fetch realm role that was renamed admin/api * When calling the token revoke endpoint multiple times with the same token, a database REVOKED-TOKEN constraint error is reported storage * Admin events: resource type filter does not work admin/ui * Unwanted placeholder texts in user profile fields admin/ui * KC_HTTPS_TRUST_STORE_TYPE not working dist/quarkus * The default setting of the client request object parameter is empty admin/ui"
1314
}

src/content/posts-aggregator/14.json

+4-4
Large diffs are not rendered by default.

src/content/posts-aggregator/15.json

+5-5
Large diffs are not rendered by default.

src/content/posts-aggregator/16.json

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
{
2-
"title": "Quarkus Newsletter #54 - March",
3-
"link": "https://quarkus.io/blog/quarkus-newsletter-54/",
2+
"title": "Quarkus 3.19.3 - Maintenance release",
3+
"link": "https://quarkus.io/blog/quarkus-3-19-3-released/",
44
"author": [
55
{
6-
"name": "James Cobb",
6+
"name": "Guillaume Smet",
77
"avatar": null
88
}
99
],
1010
"date": "2025-03-12T00:00:00.000Z",
1111
"feed_title": "Quarkus",
12-
"content": "Make sure you read Mario Fusco’s two-part blog about Agentic AI with Quarkus, where he discusses common workflows and agentic AI patterns and architectures, with practical examples using Quarkus and LangChain4j. Learn about the power of intelligent applications by combining the robustness of Java, the efficiency of Quarkus, and the advanced capabilities of RAG in a great article by Daniel Oh. Emil Lefkof gives a real-world example of how LangChain4j and AI can be leveraged to automatically extract structured metadata from PDF documents. Leveraging the combination of LangChain4j and Google Gemini AI proves to be a powerful approach for automating document analysis workflows. \"Performance & Productivity: Rethinking Java Dependencies for the Cloud Era\" by Markus Eisele discusses how Quarkus extensions are curated, lightweight, and optimized for microservices and serverless. You will also see the latest Quarkus Insights episodes, top tweets/discussions and upcoming Quarkus attended events. Check out ! Want to get newsletters in your inbox? using the on page form."
12+
"content": "We released Quarkus 3.19.3, the second (we skipped 3.19.0) maintenance release for our 3.19 release train. We also released two candidate releases: * Quarkus 3.20.0.CR1 LTS - it is going to be our next LTS, it is based on 3.19 * Quarkus 3.21.0.CR1 - a regular minor release with new features UPDATE To update to Quarkus 3.19, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.19. For more information about the adjustments you need to make to your applications, please refer to the . FULL CHANGELOG You can get the full changelog of on GitHub. COME JOIN US We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together! If you are a Quarkus user or just curious, don’t be shy and join our welcoming community: * provide feedback on ; * craft some code and ; * discuss with us on and on the ; * ask your questions on ."
1313
}

0 commit comments

Comments
 (0)