Rockcraft 1.14 release notes¶
29 August 2025
Learn about the new features, changes, and fixes introduced in Rockcraft 1.14. For information about the Rockcraft release cycle, see the Release policy and schedule.
Requirements and compatibility¶
To run Rockcraft, a system requires the following minimum hardware and installed software. These requirements apply to local hosts as well as VMs and container hosts.
Minimum hardware requirements¶
AMD64, ARM64, ARMv7-M, RISC-V 64-bit, PowerPC 64-bit little-endian, or S390x processor
2GB RAM
10GB available storage space
Internet access for remote software sources and the Snap Store
Platform requirements¶
Platform |
Version |
Software requirements |
---|---|---|
GNU/Linux |
Popular distributions that ship with systemd and are compatible with snapd |
systemd |
What’s new¶
Rockcraft 1.14 brings the following features, integrations, and improvements.
New entrypoint-command
project key¶
This key defines the rock’s OCI entrypoint, bypassing the default Pebble-powered entrypoint. It can be necessary for cases like OS and base images, where an application-centric Pebble service is inadequate.
See the rockcraft.yaml reference for usage details.
New jlink-extra-modules
key¶
The new jlink-extra-modules
key in the JLink plugin defines
modules to add to the generated OpenJDK image.
Maven Use plugin reference¶
In the documentation, we added a Maven Use plugin reference.
Contribution guidelines¶
We’ve added a CONTRIBUTING.md file describing the general approach and guidelines for contributing to the Rockcraft codebase. If you have an idea for an improvement, be sure to check it out.
Minor features¶
Rockcraft 1.14 brings the following minor changes.
Improved test
command¶
The test
command now packs and tests all platforms that can be built on the running
environment.
Improved keyserver support in package-repositories
¶
If an attempt to connect to the default keyserver to retrieve a public key fails, the
package-repositories
mechanism will now try to connect through port 80
while also respecting proxy addresses set via the standard http_proxy
and
https_proxy
environment variables.
Improved conflict detection between the overlay and build steps¶
The collision resolution during the stage step now takes into account the contents of the overlay.
Improved documentation for 12-factor app extensions¶
The tutorial and reference pages for all 12-factor app extensions were improved based on user feedback, with fixes to multiple steps that were showstoppers.
Contributors¶
We would like to express a big thank you to all the people who contributed to this release.
@alesancor1
,
@bepri
,
@erinecon
,
@jahn-junior
,
@javierdelapuente
,
@medubelko
,
and @tigarmo
.