<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Paketo Buildpacks | Blog</title>
    <link>https://blog.paketo.io/</link>
    <description>Recent content on Paketo Buildpacks | Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 02 Apr 2026 14:14:44 -0500</lastBuildDate>
    <atom:link href="https://blog.paketo.io/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Paketo Buildpacks 2025 User Survey Results</title>
      <link>https://blog.paketo.io/posts/paketo-buildpacks-2025-user-survey-results/</link>
      <pubDate>Thu, 02 Apr 2026 14:14:44 -0500</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-buildpacks-2025-user-survey-results/</guid>
      <description>&lt;p&gt;Earlier this year, we ran the Paketo Buildpacks User Survey to better understand how people are using the project and what they&amp;rsquo;d like to see from it. We&amp;rsquo;re excited to share the results and how we&amp;rsquo;re going to incorporate your feedback.&lt;/p&gt;&#xA;&lt;p&gt;Thank you to everyone who took the time to fill it out. Your feedback genuinely helps shape the direction of the project.&lt;/p&gt;&#xA;&lt;h2 id=&#34;survey-results&#34;&gt;Survey Results&lt;/h2&gt;&#xA;&lt;h3 id=&#34;overview&#34;&gt;Overview&lt;/h3&gt;&#xA;&lt;p&gt;We received 18 responses from a broad mix of users, ranging from individual developers working on side projects to engineers at enterprise organizations. The diversity of use cases gives us a good cross-section of how Paketo Buildpacks is being used in the wild.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks 2025 Year in Review</title>
      <link>https://blog.paketo.io/posts/paketo-buildpacks-2025-year-in-review/</link>
      <pubDate>Wed, 14 Jan 2026 13:14:44 -0500</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-buildpacks-2025-year-in-review/</guid>
      <description>&lt;p&gt;As we welcome 2026, it&amp;rsquo;s time to reflect on what has been a great year for the Paketo Buildpacks project. From all of us on the steering committee, we want to extend our gratitude to every contributor, maintainer, and user who has helped grow the project throughout 2025. Whether you&amp;rsquo;ve been with us from the beginning or just discovered Paketo Buildpacks this past year, your engagement and feedback have been the driving force behind our continued growth and innovation. Join us as we look back at the milestones and successes of the project in 2025.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Node.js Buildpacks updates default to Node.js 24</title>
      <link>https://blog.paketo.io/posts/default-version-bump-node-24/</link>
      <pubDate>Thu, 08 Jan 2026 12:32:49 +0100</pubDate>
      <guid>https://blog.paketo.io/posts/default-version-bump-node-24/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Node.js 24 entered active status&lt;/strong&gt; in October 2025 according to the Node.js &lt;a href=&#34;https://nodejs.org/en/about/previous-releases&#34;&gt;release schedule&lt;/a&gt;.&#xA;We are excited to announce that it is now the default version for the &lt;a href=&#34;https://github.com/paketo-buildpacks/nodejs&#34;&gt;Paketo Node.js buildpacks&lt;/a&gt;!&#xA;This means that if no Node.js version is specified via the &lt;code&gt;package.json&lt;/code&gt; file, &lt;code&gt;.node-version&lt;/code&gt; file, &lt;code&gt;.nvmrc&lt;/code&gt; file or through the &lt;code&gt;BP_NODE_VERSION&lt;/code&gt; environment variable, the selected Node.js version will default to 24!&lt;/p&gt;&#xA;&lt;p&gt;Although Node.js 24 has been available on Paketo Buildpacks since &lt;strong&gt;November 4th, 2025&lt;/strong&gt;, via the &lt;a href=&#34;https://github.com/paketo-buildpacks/node-engine/pull/1356&#34;&gt;node-engine buildpack&lt;/a&gt;, we had to ensure that all the Paketo Node.js buildpacks have been tested against it through their testing suite, before setting it as default. This ensures that the current behavior of the Paketo Node.js Buildpacks implementation remains stable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks User Survey</title>
      <link>https://blog.paketo.io/posts/paketo-buildpacks-user-survey-2025/</link>
      <pubDate>Mon, 24 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-buildpacks-user-survey-2025/</guid>
      <description>&lt;h2 id=&#34;user-survey-2025&#34;&gt;User Survey 2025&lt;/h2&gt;&#xA;&lt;p&gt;As long as I have been working on Paketo Buildpacks, it has been a challenge to understand how our users make use of the project. What buildpacks get used? What features are important? Where should we spend project time and resources? We just don&amp;rsquo;t know &amp;#x1f937;&amp;zwj;&amp;#x2642;&amp;#xfe0f;&lt;/p&gt;&#xA;&lt;p&gt;This is because for your privacy, Paketo Buildpacks do not have telemetry in them nor do they capture any information about your usage patterns. Because we do not capture telemetry, it does make it difficult for the project to plan and prioritize work for our buildpacks.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks add support for .NET 10</title>
      <link>https://blog.paketo.io/posts/paketo-dotnet-10-support/</link>
      <pubDate>Wed, 12 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-dotnet-10-support/</guid>
      <description>&lt;h2 id=&#34;net-10-is-now-available&#34;&gt;.NET 10 is now available&lt;/h2&gt;&#xA;&lt;p&gt;The Paketo Buildpacks team is excited to announce that the same day .NET 10 was released, it is now available to&#xA;be used in your Paketo Buildpacks builds!&lt;/p&gt;&#xA;&lt;p&gt;All you need to do is update the target framework to &lt;code&gt;net10.0&lt;/code&gt; in your &lt;code&gt;.csproj&lt;/code&gt; file, and the buildpack will&#xA;automatically use the latest SDK and ASP.NET Core runtime.&lt;/p&gt;&#xA;&lt;p&gt;Please reach out to the team if you have any questions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What has changed on how we ship the Builders and the base images</title>
      <link>https://blog.paketo.io/posts/builders-stacks-base-images-restructure/</link>
      <pubDate>Mon, 20 Oct 2025 23:25:07 +0200</pubDate>
      <guid>https://blog.paketo.io/posts/builders-stacks-base-images-restructure/</guid>
      <description>&lt;p&gt;We recently finished implementing the &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0061-core-builder.md&#34;&gt;core builder RFC&lt;/a&gt;. This means quite a few changes across the Paketo Buildpacks organization, so we would like to walk you through the new structure (noble/UBI9) by comparing it with the old structure (jammy/UBI8) to highlight the differences.&lt;/p&gt;&#xA;&lt;h2 id=&#34;changes-to-base-images-former-stacks&#34;&gt;Changes to Base images (former stacks)&lt;/h2&gt;&#xA;&lt;p&gt;For Ubuntu Jammy, each repository publishes the build and the run image, as follows:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/jammy-full-stack&#34;&gt;Jammy-full-stack&lt;/a&gt;&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;docker.io/paketobuildpacks/build-jammy-full&lt;/li&gt;&#xA;&lt;li&gt;docker.io/paketobuildpacks/run-jammy-full&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/jammy-base-stack&#34;&gt;Jammy-base-stack&lt;/a&gt;&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;docker.io/paketobuildpacks/build-jammy-base&lt;/li&gt;&#xA;&lt;li&gt;docker.io/paketobuildpacks/run-jammy-base&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/jammy-tiny-stack&#34;&gt;Jammy-tiny-stack&lt;/a&gt;&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;docker.io/paketobuildpacks/build-jammy-tiny&lt;/li&gt;&#xA;&lt;li&gt;docker.io/paketobuildpacks/run-jammy-tiny&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/jammy-static-stack&#34;&gt;Jammy-static-stack&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks add support for Java 25</title>
      <link>https://blog.paketo.io/posts/paketo-java-25-support/</link>
      <pubDate>Fri, 19 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-java-25-support/</guid>
      <description>&lt;h2 id=&#34;java-25-is-now-available-from-java-buildpacks&#34;&gt;Java 25 is now available from Java buildpacks&lt;/h2&gt;&#xA;&lt;p&gt;The Paketo Buildpacks team is excited to announce that, after only 3 days since the first Java 25 builds appeared, Java 25 is now an option for your Paketo Buildpacks Java builds.&lt;/p&gt;&#xA;&lt;p&gt;Check out those release notes!&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/java/releases/tag/v18.14.0&#34;&gt;https://github.com/paketo-buildpacks/java/releases/tag/v18.14.0&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/java-native-image/releases/tag/v11.17.0&#34;&gt;https://github.com/paketo-buildpacks/java-native-image/releases/tag/v11.17.0&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;But even better, try them out now!&lt;/p&gt;&#xA;&lt;h3 id=&#34;first-option-force-java-to-25-using-bp_jvm_version&#34;&gt;First option: force Java to 25 using BP_JVM_VERSION&lt;/h3&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;cd paketo-buildpacks/samples/java/maven&#xA;pack config default-builder paketobuildpacks/builder-noble-java-tiny:latest&#xA;pack build applications/maven --env BP_JVM_VERSION=25&#xA;[...]&#xA;[builder]     Using Java version 25 from BP_JVM_VERSION&#xA;[...]&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&#34;second-option-set-your-sdkmanrc-to-java-25&#34;&gt;Second option: set your &lt;code&gt;.sdkmanrc&lt;/code&gt; to Java 25&lt;/h3&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;cd paketo-buildpacks/samples/java/maven&#xA;sdk install java 25-zulu&#xA;sdk use java 25-zulu&#xA;sdk env init&#xA;cat .sdkmanrc &#xA;java=25-zulu&#xA;&#xA;pack config default-builder paketobuildpacks/builder-noble-java-tiny:latest&#xA;pack build applications/maven&#xA;[...]&#xA;[builder]     Using Java version 25 extracted from .sdkmanrc&#xA;[builder]   BellSoft Liberica JDK 25.0.0: Contributing to layer&#xA;[builder]     Downloading from https://github.com/bell-sw/Liberica/releases/download/25+37/bellsoft-jdk25+37-linux-aarch64.tar.gz&#xA;[...]&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;what-about-the-other-jdk--jre-distributions&#34;&gt;What about the other JDK / JRE distributions?&lt;/h2&gt;&#xA;&lt;p&gt;At the time of writing: &lt;a href=&#34;https://github.com/paketo-buildpacks/azul-zulu/releases/tag/v11.3.0&#34;&gt;Azul Zulu&lt;/a&gt;, &lt;a href=&#34;https://github.com/paketo-buildpacks/bellsoft-liberica/releases/tag/v11.3.0&#34;&gt;Bellsoft Liberica (not NIK yet)&lt;/a&gt;, &lt;a href=&#34;https://github.com/paketo-buildpacks/oracle/releases/tag/v4.2.0&#34;&gt;Oracle and GraalVM&lt;/a&gt;, &lt;a href=&#34;https://github.com/paketo-buildpacks/sap-machine/releases/tag/v12.2.0&#34;&gt;SAP Machine&lt;/a&gt;, &lt;a href=&#34;https://github.com/paketo-buildpacks/amazon-corretto/releases/tag/v9.3.0&#34;&gt;Amazon Corretto&lt;/a&gt; all got upgraded to support Java 25 (and lost support for Java 24)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks Sunsets Java Azure Composite Buildpack</title>
      <link>https://blog.paketo.io/posts/paketo-java-azure-sunsets/</link>
      <pubDate>Fri, 11 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-java-azure-sunsets/</guid>
      <description>&lt;h2 id=&#34;urgent-news&#34;&gt;Urgent News&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://github.com/paketo-buildpacks/java-azure&#34;&gt;Paketo Buildpacks Java Azure&lt;/a&gt; composite buildpack is being sunset. It will be archived on May 9th, 2025.&lt;/p&gt;&#xA;&lt;p&gt;Please &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/java/0018-retire-java-azure-composite.md&#34;&gt;see the RFC&lt;/a&gt; for rationale and details.&lt;/p&gt;&#xA;&lt;h2 id=&#34;action-items-for-you&#34;&gt;Action Items for You&lt;/h2&gt;&#xA;&lt;p&gt;If you are using this buildpack, you have two choices on how to proceed.&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;You may migrate off it. The primary feature of this buildpack is that it includes the Microsoft OpenJDK JVM. You do not need this buildpack to use the Microsoft OpenJDK JVM though. To continue to using Microsoft OpenJDK and migrate off of the Java Azure composite buildpack, you need to use &lt;a href=&#34;https://paketo.io/docs/howto/java/#use-an-alternative-jvm&#34;&gt;the alternative JVM instructions&lt;/a&gt; in the Paketo docs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo UBI builders moving to paketo-buildpacks from paketo-community</title>
      <link>https://blog.paketo.io/posts/paketo-ubi-builders-move-from-community-to-buildpacks/</link>
      <pubDate>Wed, 02 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-ubi-builders-move-from-community-to-buildpacks/</guid>
      <description>&lt;p&gt;The Paketo community has been working on &lt;a href=&#34;https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image&#34;&gt;UBI&lt;/a&gt;&#xA;support over the last few years after agreeing on the direction in&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0056-ubi-based-stacks.md&#34;&gt;0056-ubi-based-stacks.md&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Typically support for new components starts in the&#xA;&lt;a href=&#34;https://github.com/paketo-community&#34;&gt;paketo-community&lt;/a&gt; organization and then is moved to the&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks&#34;&gt;paketo-buildpacks&lt;/a&gt; organization once it matures.&lt;/p&gt;&#xA;&lt;p&gt;It&amp;rsquo;s now time to move the &lt;a href=&#34;https://github.com/paketo-community/builder-ubi-base&#34;&gt;builder-ubi-base&lt;/a&gt; and&#xA;&lt;a href=&#34;https://github.com/paketo-community/builder-ubi-buildpackless-base&#34;&gt;builder-ubi-buildpackless-base&lt;/a&gt; over&#xA;to the paketo-buildpacks organization. We plan to do the move Wednesday April 16th.&lt;/p&gt;&#xA;&lt;p&gt;We are publishing this blog post because this will impact users who have been using the builders to&#xA;build their application with pack. We plan to update the instructions in&#xA;&lt;a href=&#34;https://developers.redhat.com/articles/2024/06/18/build-applications-paketo-buildpacks-and-red-hat-ubi-container-images&#34;&gt;Build applications with Paketo Buildpacks and Red Hat UBI container images&lt;/a&gt;.&#xA;to point to the new builder name after the move.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks usage and socials</title>
      <link>https://blog.paketo.io/posts/paketo-java-usage-socials/</link>
      <pubDate>Mon, 31 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-java-usage-socials/</guid>
      <description>&lt;h2 id=&#34;paketo-buildpacks-where-are-they-used&#34;&gt;Paketo Buildpacks: where are they used?&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://blog.dahanne.net/2024/04/10/state-of-the-paas-in-2024/&#34;&gt;While preparing for a talk about PaaS&lt;/a&gt;, I found out that CNBs (Cloud Native Buildpacks), in particular &lt;a href=&#34;https://github.com/paketo-buildpacks&#34;&gt;Paketo Buildpacks&lt;/a&gt;, are widely used across the industry!&lt;/p&gt;&#xA;&lt;p&gt;Sure, there&amp;rsquo;s the Dockerfile as our main competition (with all its cons: maintainability, no SBOM generation, no third party agent nor a standard mechanism to include CA certs, etc.), but interestingly enough &lt;a href=&#34;https://github.com/railwayapp/nixpacks&#34;&gt;NixPacks&lt;/a&gt; (maintained by Railway but used in other PaaS too) are also gaining traction as our competitor.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks Sunsets GCR Images</title>
      <link>https://blog.paketo.io/posts/paketo-gcr-registry-sunset/</link>
      <pubDate>Fri, 28 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-gcr-registry-sunset/</guid>
      <description>&lt;h2 id=&#34;urgent-news&#34;&gt;Urgent News&lt;/h2&gt;&#xA;&lt;p&gt;We have important news regarding project infrastructure that requires your immediate attention. The Paketo Buildpacks GCP (Google Cloud Platform) project is scheduled to be shutdown in the near future, likely within the next two week.&lt;/p&gt;&#xA;&lt;p&gt;I apologize that we cannot provide an exact date, as we do not have one ourselves. We were notified recently that our sponsor who was paying the bills for GCP will be halting that sponsorship. As such, we will no longer be storing Paketo images on GCR.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks Contributors Wanted</title>
      <link>https://blog.paketo.io/posts/paketo-buildpacks-contributors-wanted/</link>
      <pubDate>Sun, 23 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-buildpacks-contributors-wanted/</guid>
      <description>&lt;p&gt;As an open-source project, Paketo Buildpacks depends on its maintainers to keep the project running day-to-day and to provide guidance to move the project forward. In a nutshell, maintainers keep the project running and produce all the software our users love.&lt;/p&gt;&#xA;&lt;p&gt;Unfortunately, we have had a few maintainers move on from the project recently. This is a part of open-source software. People&amp;rsquo;s lives change, jobs change, interests change and they move on to other things. It happens, and it&amp;rsquo;s OK. Thank you to our departing maintainers, we&amp;rsquo;re grateful for your contributions, we&amp;rsquo;ll miss you, and we wish you the best.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo UBI stack moving to paketo-buildpacks from paketo-community</title>
      <link>https://blog.paketo.io/posts/paketo-ubi-stack-move-from-community-to-buildpacks/</link>
      <pubDate>Fri, 14 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-ubi-stack-move-from-community-to-buildpacks/</guid>
      <description>&lt;p&gt;The Paketo community has been working on &lt;a href=&#34;https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image&#34;&gt;UBI&lt;/a&gt;&#xA;support over the last few years after agreeing on the direction in&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0056-ubi-based-stacks.md&#34;&gt;0056-ubi-based-stacks.md&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Typically suport for new components starts in the&#xA;&lt;a href=&#34;https://github.com/paketo-community&#34;&gt;paketo-community&lt;/a&gt; organization and then is moved to the&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks&#34;&gt;paketo-buildpacks&lt;/a&gt; organization once it matures.&lt;/p&gt;&#xA;&lt;p&gt;It&amp;rsquo;s now time to move the &lt;a href=&#34;https://github.com/paketo-community/ubi-base-stack&#34;&gt;ubi-base-stack&lt;/a&gt; over&#xA;to the packet-buildpacks organization. We plan to do the move Monday February 24th.&lt;/p&gt;&#xA;&lt;p&gt;We are publishing this blog post because this will impact users who have been specifying the stack container&#xA;images on the command line or in their toml files (we expect this is a small number). If you are&#xA;using the builders no changes are needed yet, we&amp;rsquo;ll let you know when they are moved over.&#xA;For those using the builders, you can continue to follow the instructions in&#xA;&lt;a href=&#34;https://developers.redhat.com/articles/2024/06/18/build-applications-paketo-buildpacks-and-red-hat-ubi-container-images&#34;&gt;Build applications with Paketo Buildpacks and Red Hat UBI container images&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Java Buildpacks Updates Default to Java 21</title>
      <link>https://blog.paketo.io/posts/paketo-java-buildpacks-updates-default-to-java-21/</link>
      <pubDate>Tue, 08 Oct 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-java-buildpacks-updates-default-to-java-21/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s that time again, time to update the default Java version in Paketo Java buildpacks!&lt;/p&gt;&#xA;&lt;p&gt;Through our community RFC process, the Paketo Java subteam &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/java/0014-selecting-default-java-version.md&#34;&gt;adopted an official policy on updating the default version of the JVM&lt;/a&gt;, RFC #0014.&lt;/p&gt;&#xA;&lt;p&gt;The policy states that &amp;ldquo;the default should be changed once the latest released LTS version of Java is at least one year old&amp;rdquo;. Java 21 was released in September of 2023, and it&amp;rsquo;s now October of 2024 which puts us over a year from the release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Oracle GraalVM Support has Arrived!</title>
      <link>https://blog.paketo.io/posts/oracle-graalvm-support-has-arrived/</link>
      <pubDate>Mon, 11 Dec 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/oracle-graalvm-support-has-arrived/</guid>
      <description>&lt;h2 id=&#34;oracle-graalvm-support-has-arrived&#34;&gt;Oracle GraalVM Support has Arrived!&lt;/h2&gt;&#xA;&lt;p&gt;Today marks the start of support for building native image applications with &lt;a href=&#34;https://www.oracle.com/java/graalvm/&#34;&gt;Oracle GraalVM&lt;/a&gt;. Since Oracle released Oracle GraalVM under the &lt;a href=&#34;https://blogs.oracle.com/java/post/graalvm-free-license&#34;&gt;GraalVM Free License&lt;/a&gt;, we&amp;rsquo;ve been receiving lots of feedback to add support for it. Starting with the 3.11.0 release of the Paketo Buildpack for Oracle we now have official support!&lt;/p&gt;&#xA;&lt;p&gt;With this first release, you can build native image applications with Oracle GraalVM. Building your application is simple. You follow the &lt;a href=&#34;https://paketo.io/docs/howto/java/#use-an-alternative-java-native-image-toolkit&#34;&gt;process for selecting a Native Image Toolkit&lt;/a&gt; and use the Oracle buildpack.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo&#39;s Bionic Builder Is Unsafe</title>
      <link>https://blog.paketo.io/posts/paketo-bionic-builder-is-unsafe/</link>
      <pubDate>Tue, 14 Nov 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-bionic-builder-is-unsafe/</guid>
      <description>&lt;h2 id=&#34;paketos-bionic-builder-is-unsafe&#34;&gt;Paketo&amp;rsquo;s Bionic Builder Is Unsafe&lt;/h2&gt;&#xA;&lt;p&gt;It&amp;rsquo;s a strange thing for the Paketo Project to call out its builder as being unsafe, but the key detail here is that it&amp;rsquo;s the &lt;strong&gt;Ubuntu Bionic Builder&lt;/strong&gt; we&amp;rsquo;re saying is unsafe.&lt;/p&gt;&#xA;&lt;p&gt;On May 31st, 2023, Ubuntu 18.04 (Bionic Beaver) went out of support for OSS customers (&lt;a href=&#34;https://ubuntu.com/blog/18-04-end-of-standard-support&#34;&gt;source&lt;/a&gt;). At the same time, the Paketo Project &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0057-bionic-eos.md&#34;&gt;stopped supporting its Bionic Stacks and Builders based on Ubuntu 18.04&lt;/a&gt;. This was further communicated in a &lt;a href=&#34;https://blog.paketo.io/posts/bionic-eos/&#34;&gt;blog post on July 28, 2023&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo buildpacks team is welcoming new contributors from Hacktoberfest!</title>
      <link>https://blog.paketo.io/posts/paketo-buildpacks-hacktoberfest-2023/</link>
      <pubDate>Thu, 05 Oct 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-buildpacks-hacktoberfest-2023/</guid>
      <description>&lt;h2 id=&#34;what-is-hacktoberfest&#34;&gt;What is Hacktoberfest?&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://hacktoberfest.com/&#34;&gt;Hacktoberfest&lt;/a&gt; is a recurring (yearly) event that lasts the whole month of October and encourages participants to contribute to Open Source projects.&lt;/p&gt;&#xA;&lt;p&gt;The contributions can be technical (code) but also about documentation -  the goal is to make a new population of developers familiar with Open Source.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://hacktoberfest.com/about/&#34;&gt;Digital Ocean and other companies&lt;/a&gt; organize this event each year and of course you win awards participating!&lt;/p&gt;&#xA;&lt;p&gt;You already have a Github account? that&amp;rsquo;s all you need to participate! &lt;a href=&#34;https://hacktoberfest.com/auth/&#34;&gt;Go ahead and register now&lt;/a&gt;!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bionic End of Support</title>
      <link>https://blog.paketo.io/posts/bionic-eos/</link>
      <pubDate>Fri, 28 Jul 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/bionic-eos/</guid>
      <description>&lt;p&gt;As of May 31, 2023, Ubuntu 18.04 (Bionic Beaver) is &lt;a href=&#34;https://ubuntu.com/blog/18-04-end-of-standard-support&#34;&gt;out of&#xA;support&lt;/a&gt; for open-source&#xA;customers.&lt;/p&gt;&#xA;&lt;p&gt;As a result, Paketo will stop supporting Bionic in the project. If you&#xA;currently depend on our Bionic-based offerings, this blog post will contain&#xA;all of the relevant information about what this means and how to migrate.&lt;/p&gt;&#xA;&lt;h2 id=&#34;end-of-support-details&#34;&gt;End of Support Details&lt;/h2&gt;&#xA;&lt;p&gt;The removal of Bionic support in Paketo was announced and ratified in the&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0057-bionic-eos.md&#34;&gt;Bionic End of Support RFC&lt;/a&gt;.&#xA;The following stacks and builders will no longer be supported, meaning&lt;/p&gt;</description>
    </item>
    <item>
      <title>Java Buildpacks enhancements</title>
      <link>https://blog.paketo.io/posts/java-buildpacks-enhancements/</link>
      <pubDate>Fri, 16 Jun 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/java-buildpacks-enhancements/</guid>
      <description>&lt;p&gt;During the last few weeks, some enhancements were brought to buildpacks related to the Java ecosystem.&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s discover what&amp;rsquo;s new!&lt;/p&gt;&#xA;&lt;h3 id=&#34;tldr&#34;&gt;TL;DR&lt;/h3&gt;&#xA;&lt;p&gt;Checkout the &lt;a href=&#34;https://github.com/paketo-buildpacks/samples/tree/main/java&#34;&gt;samples repository for Java examples&lt;/a&gt; and the &lt;a href=&#34;https://paketo.io/docs/howto/java/&#34;&gt;Paketo Buildpacks official documentation&lt;/a&gt; - those provide way more details about Paketo uses cases (native, certificates, network-less, etc.) than the different build plugins (Maven and Gradle) documentation.&lt;/p&gt;&#xA;&lt;p&gt;And they&amp;rsquo;re always up-to-date! In the rare event they&amp;rsquo;re not, create an &lt;a href=&#34;https://github.com/paketo-buildpacks/java&#34;&gt;issue or Pull Request&lt;/a&gt; or reach us on &lt;a href=&#34;https://join.slack.com/t/paketobuildpacks/shared_invite/zt-2jayv12ro-eTP8AtcmvyIpEtlANfIb~g&#34;&gt;Slack&lt;/a&gt;, and we will fix that!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Manually testing changes to a Paketo Buildpack</title>
      <link>https://blog.paketo.io/posts/manually-testing-changes-to-paketo-buildpacks/</link>
      <pubDate>Tue, 23 May 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/manually-testing-changes-to-paketo-buildpacks/</guid>
      <description>&lt;p&gt;&lt;em&gt;While this article is mainly about how to manually test Java family Paketo buildpacks, still, most of the instructions should work fine with other Paketo buildpacks; and even non Paketo buildpacks!&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Suppose that you started working on a new feature for the &lt;a href=&#34;https://github.com/paketo-buildpacks/spring-boot/&#34;&gt;&lt;code&gt;spring-boot&lt;/code&gt;&lt;/a&gt; buildpack&amp;hellip;&lt;/p&gt;&#xA;&lt;h2 id=&#34;unit-tests-first&#34;&gt;Unit tests first&lt;/h2&gt;&#xA;&lt;p&gt;Of course, during your development, you will make sure that you did not break any tests, regularly running &lt;code&gt;go test -v ./...&lt;/code&gt; but you would also add new tests covering your new code; the classic combination &lt;code&gt;go test -v ./... -coverprofile=coverage.out&lt;/code&gt; followed with &lt;code&gt;go tool cover -html=coverage.out&lt;/code&gt; will allow you to verify you did not forget to test some errors or edge cases.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Java Buildpacks Updates its Default JVM Version</title>
      <link>https://blog.paketo.io/posts/paketo-java-buildpacks-updates-its-default-jvm-version/</link>
      <pubDate>Thu, 09 Feb 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-java-buildpacks-updates-its-default-jvm-version/</guid>
      <description>&lt;p&gt;Time and tides wait for no one, nor does software. The Oracle and the OpenJDK project have been steadily releasing new versions of Java for years now, with new Java versions every six months and now long-term support releases every two years (with Java 21, it&amp;rsquo;s dropped to two years from three).&lt;/p&gt;&#xA;&lt;p&gt;As of writing this post, the Java buildpack is currently using Java 11 as its default. This has been the same default version since the Paketo Java buildpack was released, but we&amp;rsquo;re falling behind and it&amp;rsquo;s time for a change.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks 2023 - Onward and Upward</title>
      <link>https://blog.paketo.io/posts/2023-roadmap/</link>
      <pubDate>Thu, 26 Jan 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/2023-roadmap/</guid>
      <description>&lt;p&gt;This last year was a big one for the project. We grew significantly, matured&#xA;our buildpack and stack offerings, and found new ways to engage with our users.&#xA;For 2023, we hope for all of that and more.&lt;/p&gt;&#xA;&lt;p&gt;We want to thank everyone who contributed to the project in 2022. Whether that&#xA;was direct contibution to our codebases or feedback in the form of issues,&#xA;discussions, or Slack messages, you&amp;rsquo;ve been a big part of the success we&amp;rsquo;ve had&#xA;this year.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks 2022 - Another Year in Review</title>
      <link>https://blog.paketo.io/posts/2022-recap/</link>
      <pubDate>Tue, 24 Jan 2023 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/2022-recap/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://blog.paketo.io/images/posts/0003/logo.png&#34; alt=&#34;Logo&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;In 2022, the major roadmap themes were improvements and expansions of our stack&#xA;offerings, paying down significant technical debt in our dependency management&#xA;system, and making efforts to improve buildpack authoring tools.&lt;/p&gt;&#xA;&lt;h2 id=&#34;improving-and-expanding-our-base-image--stack--builder-offering&#34;&gt;Improving and Expanding our Base Image / Stack / Builder Offering&lt;/h2&gt;&#xA;&lt;p&gt;We launched sweeping support for Ubuntu 2022.04 Jammy Jellyfish across our&#xA;stacks, buildpacks, and builders. This was a tremendous effort with&#xA;contributions across the entire Paketo Core team and community. It touched&#xA;every buildpack and took the better part of 9 months to complete as we resolved&#xA;huge amounts of technical debt in the process. If you are more interested in&#xA;what happened on this front, check out the RFCs below:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Buildpack Development: Selecting a Cloud-Native Buildpacks Library</title>
      <link>https://blog.paketo.io/posts/buildpack-dev-selecting-a-library/</link>
      <pubDate>Mon, 03 Oct 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/buildpack-dev-selecting-a-library/</guid>
      <description>&lt;p&gt;In the Paketo Buildpacks community, we’ve standardized around writing our buildpacks using the Go language. Go works great for buildpack development because it compiles down to a relatively compact static binary, so our buildpack images are small, and it runs very fast, so our buildpacks run fast. It also provides great support for testing and since we want to have rock solid buildpacks, testing is very important as well.&lt;/p&gt;&#xA;&lt;p&gt;To write a buildpack in the Go language, it helps if you have a library that implements the Cloud-Native Buildpacks (CNB) specification. You could certainly write buildpacks without a library, but it’s going to require more work and you then need to validate that your buildpack follows the specification.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Introducing the Contributor of the Month initiative</title>
      <link>https://blog.paketo.io/posts/oss-contributor-of-the-month/</link>
      <pubDate>Thu, 01 Sep 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/oss-contributor-of-the-month/</guid>
      <description>&lt;p&gt;Why someone contributes to open source?&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;The Open Source Way 2.0&lt;/em&gt; &lt;a href=&#34;https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html#_why_do_people_participate_in_open_source_communities&#34;&gt;guidebook&lt;/a&gt; describes some of the diverse motivations that lead individuals to participate in open source communities, including:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Extrinsic motivation: contributing to OSS is part of their job, career advancement by developing code that it&amp;rsquo;s in the open or to collaboratively solve a problem they are facing.&lt;/li&gt;&#xA;&lt;li&gt;Intrinsic motivation: a sense of purpose while contributing to a cause that is beneficial to a community, collaborative learning and the perceived professional benefit that it produces.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;While intrinsic motivation is the kind of altruist behavior usually associated with OSS contributions, extrinsic motivation and rewards also play an important role on encouraging and recognizing the diverse forms of contributions an open source project wants and needs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>WebSphere Liberty now available</title>
      <link>https://blog.paketo.io/posts/websphere-liberty-now-included-in-liberty-buildpack/</link>
      <pubDate>Thu, 25 Aug 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/websphere-liberty-now-included-in-liberty-buildpack/</guid>
      <description>&lt;p&gt;I am pleased to announce that &lt;a href=&#34;https://www.ibm.com/cloud/websphere-liberty&#34;&gt;WebSphere Liberty&lt;/a&gt; is now included in the &lt;a href=&#34;https://github.com/paketo-buildpacks/liberty&#34;&gt;Paketo Liberty&lt;/a&gt; buildpack and available to currently entitled WebSphere Liberty users. WebSphere Liberty is built on &lt;a href=&#34;openliberty.io&#34;&gt;Open Liberty&lt;/a&gt; and is a lightweight, efficient, Java™ EE, Jakarta EE and MicroProfile cloud-native runtime.&lt;/p&gt;&#xA;&lt;p&gt;The Paketo Liberty buildpack now gives you a choice to use WebSphere Liberty or Open Liberty to run your application.&lt;/p&gt;&#xA;&lt;p&gt;To use WebSphere Liberty in your container, set the &lt;code&gt;BP_LIBERTY_INSTALL_TYPE&lt;/code&gt; environment variable to specify the &lt;a href=&#34;https://github.com/paketo-buildpacks/liberty#install-types&#34;&gt;install type&lt;/a&gt; &lt;code&gt;wlp&lt;/code&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Growing a healthy open source community, one metric at a time</title>
      <link>https://blog.paketo.io/posts/oss-health-assessment/</link>
      <pubDate>Wed, 22 Jun 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/oss-health-assessment/</guid>
      <description>&lt;p&gt;In this post, I plan to share the framework the Paketo Buildpacks project will be using to approach the goal of building and sustaining an inclusive community of users, contributors and maintainers; and how it translates to a set of action items we will be executing during the remaining of 2022.&lt;/p&gt;&#xA;&lt;p&gt;Currently, the project follows the Community Engagement guidelines and best practices &lt;a href=&#34;https://github.com/vmware-tanzu/community-engagement/blob/main/GUIDELINES.md&#34;&gt;outlined here&lt;/a&gt; as they represent a diverse set of initiatives designed to provide the community with tools and processes for improved collaboration. To make sure we are doing it effectively, an assessment is conducted twice per year, providing recommendations and an action plan to address the possible findings.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Introducing the Paketo Web Servers Buildpack</title>
      <link>https://blog.paketo.io/posts/webservers-rearchitecture/</link>
      <pubDate>Wed, 18 May 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/webservers-rearchitecture/</guid>
      <description>&lt;p&gt;The Paketo team is pleased to introduce the &lt;a href=&#34;https://github.com/paketo-buildpacks/web-servers&#34;&gt;Web Servers buildpack&lt;/a&gt;, available in the Paketo Full Builder as of &lt;a href=&#34;https://github.com/paketo-buildpacks/full-builder/releases/tag/v0.2.74&#34;&gt;version 0.2.74&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This buildpack allows you to serve static content using the popular NGINX or HTTPD web servers, with a variety of utilities for ease of use. Whether you have static files and a server configuration file that you want to package in an image, or you need to transform your dynamic content into static files and want the buildpack to generate the necessary server configuration file, the Web Servers buildpack has you covered.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reintroducing the PHP Buildpack</title>
      <link>https://blog.paketo.io/posts/php-rearchitecture/</link>
      <pubDate>Thu, 12 May 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/php-rearchitecture/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a new and exciting development in the Paketo Buildpacks project! The&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/php&#34;&gt;Paketo PHP Buildpack&lt;/a&gt; has been fully&#xA;re-architected and is ready to make containerizing PHP applications simple and&#xA;transparent. With the rearchitecture, the same base set of functionality is&#xA;supported as in the original PHP buildpack, but the buildpacks have been&#xA;modernized using the newest Paketo tooling and modularized to separate concerns&#xA;into individual buildpacks.&lt;/p&gt;&#xA;&lt;h2 id=&#34;whats-new&#34;&gt;What&amp;rsquo;s new?&lt;/h2&gt;&#xA;&lt;h3 id=&#34;breaking-it-down&#34;&gt;Breaking it down&lt;/h3&gt;&#xA;&lt;p&gt;The rearchitecture has made it vastly easier for maintainers and contributors&#xA;to add new functionality to the language family, by breaking down&#xA;what used to be three larger buildpacks, into 10+ new buildpacks responsible&#xA;for single parts of the build process. This may sound like a lot of new&#xA;buildpacks, but small lighter-weight buildpacks are actually what we strive&#xA;for in the project. This concept is well-described in the &lt;a href=&#34;https://blog.paketo.io/posts/buildpack-philosophy-part-1/&#34;&gt;Paketo Buildpacks&#xA;Philosophy Part 1 blog&#xA;post&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks 2022 - Full speed ahead</title>
      <link>https://blog.paketo.io/posts/2022-roadmap/</link>
      <pubDate>Wed, 11 May 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/2022-roadmap/</guid>
      <description>&lt;p&gt;Before we share the big plans we have for 2022, the Paketo Buildpacks Steering&#xA;Committee would like to thank everyone that joined in the 2022 roadmap&#xA;discussion, as well as everyone that’s provided feedback across all of the&#xA;Paketo Buildpacks in 2021. The team is grateful for all of the feedback that we&#xA;receive, as it helps to shape the project and ensure we’re building the tools&#xA;that everyone wants to use.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks 2021 - A Year in Review</title>
      <link>https://blog.paketo.io/posts/2021-recap/</link>
      <pubDate>Tue, 10 May 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/2021-recap/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://blog.paketo.io/images/posts/0003/logo.png&#34; alt=&#34;Logo&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Thanks so much to the Paketo community for all your hard work over the last&#xA;year! The project made significant progress on the themes identified in our&#xA;&lt;a href=&#34;https://blog.paketo.io/posts/2021-roadmap/&#34;&gt;2021 Roadmap&lt;/a&gt;. We won’t be able to&#xA;cover everything in this blog post, but here are some highlights.&lt;/p&gt;&#xA;&lt;h2 id=&#34;solidifying-existing-buildpacks&#34;&gt;Solidifying Existing Buildpacks&lt;/h2&gt;&#xA;&lt;p&gt;While the work of standardizing our buildpacks continues, we are proud of the&#xA;progres we have made, including:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Moving to &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0026-environment-variable-configuration-of-buildpacks.md&#34;&gt;environment&#xA;variables&lt;/a&gt;&#xA;as the primary mode of configuration for all buildpacks&lt;/li&gt;&#xA;&lt;li&gt;Standardized handling of &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0019-buildpack-set-env-vars-defaults.md&#34;&gt;language-ecosystem environment&#xA;variables&lt;/a&gt;&#xA;such as &lt;code&gt;JAVA_TOOL_OPTIONS&lt;/code&gt; and &lt;code&gt;NODE_ENV&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0029-semantic-versioning.md&#34;&gt;Standardized&#xA;versioning&lt;/a&gt;&#xA;of buildpacks, stacks, and builders&lt;/li&gt;&#xA;&lt;li&gt;Standardized configuration options, including &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0027-log-levels.md&#34;&gt;log&#xA;levels&lt;/a&gt;&#xA;and &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/0010-dependency-mappings.md&#34;&gt;dependency&#xA;mappings&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Inclusion of utility buildpacks in all language families, allowing users to:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://paketo.io/docs/howto/configuration/#ca-certificates&#34;&gt;Configure additional CA&#xA;Certificates&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://paketo.io/docs/howto/configuration/#applying-custom-labels&#34;&gt;Apply custom image&#xA;labels&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/environment-variables&#34;&gt;Set runtime environment&#xA;variables&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://paketo.io/docs/howto/configuration/#procfiles&#34;&gt;Contribute additional process&#xA;types&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;We also &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/python/0001-restructure.md&#34;&gt;restructured the Python&#xA;buildpack&lt;/a&gt;,&#xA;improving modularity and composability. A similar &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs/blob/main/text/php/0001-restructure.md&#34;&gt;restructure of the PHP&#xA;buildpack&lt;/a&gt;&#xA;is nearing completion.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Introducing the Liberty buildpack</title>
      <link>https://blog.paketo.io/posts/introducing-liberty-buildpack/</link>
      <pubDate>Mon, 04 Apr 2022 09:38:38 -0400</pubDate>
      <guid>https://blog.paketo.io/posts/introducing-liberty-buildpack/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://blog.paketo.io/images/posts/0008/open-liberty-logo.png&#34; alt=&#34;Open Liberty Logo&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/paketo-buildpacks/liberty&#34;&gt;Liberty&lt;/a&gt; is finally available in Paketo and included in the &lt;a href=&#34;https://github.com/paketo-buildpacks/java&#34;&gt;java&lt;/a&gt; buildpack! Liberty is an open application framework designed for the cloud. It’s small, lightweight, and designed with modern cloud-native application development in mind.&lt;/p&gt;&#xA;&lt;p&gt;With the Liberty buildpack, you can:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Build Java apps from source or a pre-configured on-prem Liberty&lt;/li&gt;&#xA;&lt;li&gt;Install Liberty and user custom features&lt;/li&gt;&#xA;&lt;li&gt;Install Liberty interim fixes&lt;/li&gt;&#xA;&lt;li&gt;Create UBI-based OCI images&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;what-do-you-need&#34;&gt;What do you need?&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Your application source or a pre-configured on-prem Liberty&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://hub.docker.com/search?type=edition&amp;amp;offering=community&#34;&gt;Docker&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://buildpacks.io/docs/tools/pack/&#34;&gt;pack&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;lets-get-started&#34;&gt;Let&amp;rsquo;s get started!&lt;/h2&gt;&#xA;&lt;p&gt;The following examples use the &lt;a href=&#34;https://openliberty.io/guides/getting-started.html&#34;&gt;Open Liberty starter&lt;/a&gt; application as the application source.&#xA;Download the Open Liberty starter application:&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Philosophy for Developing Paketo Buildpacks, Part 1</title>
      <link>https://blog.paketo.io/posts/buildpack-philosophy-part-1/</link>
      <pubDate>Wed, 26 Jan 2022 15:03:39 -0700</pubDate>
      <guid>https://blog.paketo.io/posts/buildpack-philosophy-part-1/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://blog.paketo.io/images/posts/0000/road.jpg&#34;&#xA;    alt=&#34;A road through the wilderness&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;p&gt;Photo by &lt;a href=&#34;https://unsplash.com/@jonflobrant?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText&#34;&gt;Jon Flobrant&lt;/a&gt; on &lt;a href=&#34;https://unsplash.com/collections/1666315/philosophy-topics?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText&#34;&gt;Unsplash&lt;/a&gt;&lt;/p&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;h2 id=&#34;sharing-what-weve-learned&#34;&gt;Sharing what we&amp;rsquo;ve learned&lt;/h2&gt;&#xA;&lt;p&gt;The Paketo Buildpacks Team has been developing our Cloud Native Buildpacks for&#xA;the better part of 2 years now. In the process, we&amp;rsquo;ve learned a lot about what&#xA;works well and what doesn&amp;rsquo;t. We&amp;rsquo;ve made mistakes and interated toward solutions&#xA;that are more flexible, easier to maintain, and provide better experiences for&#xA;our users. In the process, we&amp;rsquo;ve developed a set of guidelines – a philosophy,&#xA;maybe – for how we think about developing buildpacks. These guidelines don&amp;rsquo;t&#xA;always apply, but they are what we strive for in the vast majority of cases.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Java Buildpack Support and Debug Enhancements</title>
      <link>https://blog.paketo.io/posts/java-rearchitecture/</link>
      <pubDate>Thu, 09 Dec 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/java-rearchitecture/</guid>
      <description>&lt;p&gt;I’m pleased to announce that the Paketo Java Buildpack has been enhanced to make it even easier to analyze and debug your JVM based applications. A host of features have been added or integrated in the form of environment variable flags, and some features which previously required image rebuilds can now simply be toggled at runtime. This post will outline how to both configure the JVM itself and make use of the following features:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building a Cloud Native Buildpack Isn’t as Hard as You Think</title>
      <link>https://blog.paketo.io/posts/building-a-cloud-native-buildpack-isnt-as-hard-as-you-think/</link>
      <pubDate>Fri, 26 Feb 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/building-a-cloud-native-buildpack-isnt-as-hard-as-you-think/</guid>
      <description>&lt;p&gt;Maybe you’ve heard that many companies today are transitioning to, or have already transitioned to, a container-based platform like Kubernetes. With this movement comes the need to containerize your applications, new and old. Buildpacks provide a seamless mechanism for doing that &lt;em&gt;without Dockerfiles.&lt;/em&gt; &lt;a href=&#34;https://paketo.io&#34;&gt;Paketo Buildpacks&lt;/a&gt; is a community-driven project that provides &lt;a href=&#34;https://buildpacks.io&#34;&gt;Cloud Native Buildpacks&lt;/a&gt; implementations for the most popular languages.&lt;/p&gt;&#xA;&lt;p&gt;Buildpacks provide great out-of-box support for many languages, but &lt;strong&gt;what if you need a buildpack that doesn’t exist yet?&lt;/strong&gt; As a community-driven initiative, it may feel like the onus is on you to create that buildpack. Where would you even begin? 🤯&lt;/p&gt;</description>
    </item>
    <item>
      <title>Introducing a re-architected .NET Core Buildpack!</title>
      <link>https://blog.paketo.io/posts/dotnet-core-rearchitecture/</link>
      <pubDate>Thu, 11 Feb 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/dotnet-core-rearchitecture/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://blog.paketo.io/images/posts/0004/dotnet-core-logo.png&#34; alt=&#34;.NET Core Logo&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;On behalf of the Paketo contributors, I&amp;rsquo;m pleased to unveil the new and&#xA;improved .NET Core Buildpack! With the release of &lt;a href=&#34;https://github.com/paketo-buildpacks/dotnet-core/releases&#34;&gt;Paketo .NET Core Buildpack&#xA;0.1.0&lt;/a&gt;, you’ll enjoy&#xA;a host of new features and improvements that will make containerizing your .NET&#xA;apps a breeze. 🍃&lt;/p&gt;&#xA;&lt;p&gt;With the new buildpack, you can:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Build .NET 5 apps&lt;/li&gt;&#xA;&lt;li&gt;Build your app from source code, from a framework-dependent deployment&#xA;(FDD), from a framework-dependent executable (FDE), or from a&#xA;self-contained deployment&lt;/li&gt;&#xA;&lt;li&gt;Build Visual Basic apps&lt;/li&gt;&#xA;&lt;li&gt;Have source code removed from final app image. Your app container will&#xA;only contain the built artifacts&lt;/li&gt;&#xA;&lt;li&gt;Use a&#xA;&lt;a href=&#34;https://paketo.io/docs/buildpacks/configuration/#procfiles&#34;&gt;Procfile&lt;/a&gt; to&#xA;specify custom start processes&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;We also re-wrote the buildpacks using&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/packit&#34;&gt;packit&lt;/a&gt;, our library for&#xA;buildpack developers. This will ensure that the buildpack benefits from future&#xA;innovations in the &lt;a href=&#34;https://github.com/buildpacks/spec/blob/main/buildpack.md&#34;&gt;Cloud Native Buildpacks&#xA;specification&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>2021 Paketo Buildpacks Roadmap</title>
      <link>https://blog.paketo.io/posts/2021-roadmap/</link>
      <pubDate>Fri, 29 Jan 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/2021-roadmap/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://blog.paketo.io/images/posts/0003/logo.png&#34; alt=&#34;Logo&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;We’re not even at the one year anniversary of the Paketo Buildpacks launch, but&#xA;we’ve already got so much to celebrate 🎉. 2020 was a busy year for the Paketo&#xA;Buildpacks core development team. Looking back on the last year, a few&#xA;highlights stand out:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Establishing our &lt;a href=&#34;https://github.com/paketo-buildpacks/community/blob/main/GOVERNANCE.md&#34;&gt;project&#xA;governance&lt;/a&gt;&#xA;and &lt;a href=&#34;https://github.com/paketo-buildpacks/rfcs&#34;&gt;RFC process&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Moving all project tooling to Github-based workflows&lt;/li&gt;&#xA;&lt;li&gt;Building out a foundational set of buildpacks for some of the most popular&#xA;languages including &lt;a href=&#34;https://github.com/paketo-buildpacks/java&#34;&gt;Java&lt;/a&gt;,&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/nodejs&#34;&gt;Node.js&lt;/a&gt;, &lt;a href=&#34;https://github.com/paketo-buildpacks/dotnet-core&#34;&gt;.Net&#xA;Core&lt;/a&gt;,&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/go&#34;&gt;Go&lt;/a&gt;, and&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/ruby&#34;&gt;Ruby&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For 2021, one of our most important goals is to align on a community-driven&#xA;project roadmap. We started a discussion&#xA;&lt;a href=&#34;https://github.com/paketo-buildpacks/feedback/discussions/2&#34;&gt;thread&lt;/a&gt; at the&#xA;start of the new year to solicit interest in areas of development for this year&#xA;and received a lot of responses.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Paketo Buildpacks Hot Topic at Cloud Foundry Summit</title>
      <link>https://blog.paketo.io/posts/paketo-buildpacks-hot-topic-at-cf-summit/</link>
      <pubDate>Tue, 30 Jun 2020 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/paketo-buildpacks-hot-topic-at-cf-summit/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://blog.paketo.io/images/posts/0002/logo.jpg&#34; alt=&#34;Logo&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Paketo Buildpacks were a hot topic at the recently concluded &lt;a href=&#34;https://www.cloudfoundry.org/events/summit/na-virtual-2020/&#34;&gt;Cloud Foundry&#xA;Summit&lt;/a&gt;, the first&#xA;&lt;strong&gt;virtual Summit run by the Cloud Foundry Foundation&lt;/strong&gt;. The Summit featured project&#xA;updates, particularly in the Kubernetes space, including a talk on Paketo&#xA;Buildpacks. Dan Thornton, an engineer contributing to the Paketo Buildpacks&#xA;project, maintained that they are the ideal tool for transforming app source&#xA;code into container images.&lt;/p&gt;&#xA;&lt;p&gt;So, we wanted to share Dan’s talk here and dive into a Q&amp;amp;A of all of the&#xA;questions we didn’t get to answer during this session. A comprehensive list of&#xA;other sessions can be found on the Cloud Foundry &lt;a href=&#34;https://www.youtube.com/channel/UC0ZYS0Y7b5oiVLvxGf4magw&#34;&gt;YouTube&#xA;channel&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building apps for Kubernetes? Get to Know Paketo Buildpacks.</title>
      <link>https://blog.paketo.io/posts/get-to-know-paketo-buildpacks/</link>
      <pubDate>Tue, 21 Apr 2020 00:00:00 +0000</pubDate>
      <guid>https://blog.paketo.io/posts/get-to-know-paketo-buildpacks/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://blog.paketo.io/images/posts/0001/logo.png&#34; alt=&#34;Logo&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;I’m excited to announce the launch of &lt;a href=&#34;https://paketo.io/&#34;&gt;Paketo Buildpacks&lt;/a&gt;,&#xA;a collection of Cloud Native Buildpacks for the most popular languages and&#xA;frameworks. Paketo Buildpacks make it easy for you to build and patch&#xA;containerized apps so that you can spend all your time on the thing that&#xA;matters the most… &lt;strong&gt;developing great software&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;first-off-what-are-paketo-buildpacks-and-why-would-i-use-them&#34;&gt;First off… what are Paketo Buildpacks, and why would I use them?&lt;/h2&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Buildpacks provide a higher-level abstraction for building apps&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
