v1.25.1

What's Changed

• fix: make sure base python pkgs 'install' method is called even if not in install mode by @g-arjones in #131
• fix: make sure Environment#[] returns an inherited value after the inherit call by @doudou in #133. Doing e.g. env.inherit("PATH") would actually not define PATH (env["PATH"] would return nil) until some other values get added to it.

Full Changelog: v1.25.0...v1.25.1

v1.24.0

Bugfixes

• none

New Features

• the git importer now supports doing shallow clones. Either set Autobuild::Git.shallow to true globally, or set the shallow option per importer. This is incompatible with specifying a tag or commit, as well as with the single_branch option.
• the git importer now supports using the tree SHA instead of the commit SHA for fingerprinting. In CI, this means that a branch and its merge commit would have the same SHA, allowing to save rebuild times. Set Autobuild::Git.default_fingerprint_mode to "tree" to enable globally. The option is also available on a per-importer basis as fingerprint_mode.
• It is now possible to add a post-test coverage processing step. Pass the processing as a block to test_utility.with_coverage

Release of autobuild v1.22.0

New Features

• the git handler now auto-detects the name of the default remote branch if it is unspecified, thus properly handling main on newly created repositories on github
• orogen: pass the job server options to orogen if it supports it (for parallel code parsing)

Fixes

• improve detection of pkg-config paths
• cmake: run tests with -V to log the test output
• git: fixes related to submodule handling

1.12.2

Main bugfixes:

• do run the LFS hooks even on update error. This allows to run aup -n in a package after having modified the working copy and get the LFS hooks properly executed
• fix some corner cases where the subcommand output would not be available when displaying an error
• save the command's exit status to the log file

Bugfix release 1.11.1

Changes since 1.11.0:

Fixed git submodule handling (rock-core/autoproj#147, #37). Until 1.11.1, submodules would basically be checked out when the master repository was checked out and that's it - no update, no reset.