v2.0.0-rc.1

Architecture Changes

• Philosophy now more akin to that of a compiler, ie operate on sources while being able to reference built-in defaults
• Dedicated engine for config file parsing, layer metadata and management
• Layers are the definitive source of all configuration variables

New Critical Features

• Defined configuration variable set policies
• Automatic configuration variable validation with defined types
• Layer dependencies
• Configuration file inclusion and hierarchy support

Usage Improvements

• Single format for all declarative files (YAML) with config file migration support
• Dedicated commands for layer introspection, validation and linting
• Informative logging output for variable processing
• Layer listing with categorisation

Flexibility Improvements

• Supports device agnostic filesystems (eg for containerised development, CI, NFS)

Documentation Improvements

• New technical asciidoc manual with index and sub-sections
• Auto-generated layer catalogue with navigation and detailed information, e.g. dependencies, reverse dependencies, variables, installed packages, and other attributes

Breaking changes / migration

• Support for the options file has been removed. Migrate all settings to a config file. See #79 for details.
• All Profile files are redundant and have been removed. A 'profile' can now be simply regarded as a layer with multiple dependencies.
• Several config variables have been renamed and have a different prefix. Please examine the layer reference for details, or use the command line, e.g. rpi-image-gen layer --describe locale-base.
• INI syntax config files are still supported, but can be migrated to YAML using command line config migration.
• If a custom layer is to be found in the search path it must adhere to the embedded metadata specification. Refer to the documentation or command line for help.

What's Changed

• Brave new world by @learmj in #85
• Layer locale by @learmj in #86

Full Changelog: v1.0.0...v2.0.0-rc.1

Initial Release

This is the first release of rpi-image-gen, providing a stable foundation for users who need a reproducible build flow.

For current users:
This release serves as a reference point before the upcoming v2.0.0 changes. If you need to maintain compatibility with the current codebase, you can checkout this tag for reproducible results.

Coming soon:
v2.0.0 is planned for release very soon with the changes described in #79. v1.0.0 ensures you have a stable checkpoint to return to if needed.