Set version and changelog for 0.29.2

Author: Ortham

Cargo.lock

@@ -38,7 +38,7 @@ lto = "thin"
 members = ["cpp", "ffi-errors", "nodejs", "array-parameterized-test", "python"]
 
 [workspace.package]
-version = "0.29.1"
+version = "0.29.2"
 repository = "https://github.com/loot/libloot.git"
 edition = "2024"
 license = "GPL-3.0-or-later"

Cargo.toml

@@ -5,7 +5,7 @@ endif()
 if(POLICY CMP0167)
     cmake_policy(SET CMP0167 NEW)
 endif()
-project(libloot VERSION "0.29.1")
+project(libloot VERSION "0.29.2")
 include(CMakeDependentOption)
 include(CMakePackageConfigHelpers)
 include(GNUInstallDirs)

cpp/CMakeLists.txt

@@ -37,7 +37,7 @@ inline constexpr unsigned int LIBLOOT_VERSION_MAJOR = 0;
 inline constexpr unsigned int LIBLOOT_VERSION_MINOR = 29;
 
 /** @brief libloot's patch version number. */
-inline constexpr unsigned int LIBLOOT_VERSION_PATCH = 1;
+inline constexpr unsigned int LIBLOOT_VERSION_PATCH = 2;
 
 /**
  * @brief Get the library version.

cpp/include/loot/loot_version.h

@@ -2,8 +2,8 @@
 #include <windows.h>
 
 1 VERSIONINFO
-FILEVERSION 0, 29, 1, 0
-PRODUCTVERSION 0, 29, 1, 0
+FILEVERSION 0, 29, 2, 0
+PRODUCTVERSION 0, 29, 2, 0
 FILEOS VOS__WINDOWS32
 FILETYPE VFT_DLL
 BEGIN
@@ -13,12 +13,12 @@ BLOCK "040904b0"
 BEGIN
 VALUE "CompanyName", "LOOT"
 VALUE "FileDescription", "Library providing LOOT's core functionality"
-VALUE "FileVersion", "0.29.1"
+VALUE "FileVersion", "0.29.2"
 VALUE "InternalName", "loot"
 VALUE "LegalCopyright", "Copyright (C) 2013-2022 Oliver Hamlet"
 VALUE "OriginalFilename", "loot.dll"
 VALUE "ProductName", "LOOT"
-VALUE "ProductVersion", "0.29.1"
+VALUE "ProductVersion", "0.29.2"
 END
 END
 BLOCK "VarFileInfo"

cpp/src/api/resource.rc

@@ -2,6 +2,44 @@
 Version History
 ***************
 
+0.29.2 - 2026-03-27
+===================
+
+Added
+-----
+
+- Support for recognising when Starfield BlueprintShips plugins are implicitly
+  active.
+
+  Starfield treats a plugin named BlueprintShips-X.esm (where X can be anything)
+  as active even if it is not listed as active in plugins.txt (or not listed in
+  plugins.txt at all), so long as there is an active plugin named X.esm, X.esp
+  or X.esl. I.e. activating X.esm will also activate BlueprintShips-X.esm if it
+  exists.
+
+  libloot will account for this behaviour when reading the load order. When it
+  sets the load order, it will include the implicitly-active BlueprintShips
+  plugins in ``plugins.txt``, making them explicitly active until after the next
+  time Starfield starts. Via libloadorder.
+- Support for persisting blueprint master load order across Starfield starts.
+
+  When libloot sets the load order, it will now set the modification timestamps
+  of blueprint masters to match the load order that it writes to
+  ``plugins.txt``. When Starfield next starts, it will use the order in
+  ``plugins.txt`` and then remove the blueprint masters from ``plugins.txt``.
+  Subsequent Starfield starts will then load any implicitly active blueprint
+  masters in order of their modification timestamps. Via libloadorder.
+
+Changed
+-------
+
+- Updated libloadorder to v18.6.0.
+- Updated the accepted regress version range to include v0.11.x.
+- Updated dependency versions in Cargo.lock (which sets the versions used by the
+  C++ wrapper):
+
+  - Updated regress to v0.11.0.
+
 0.29.1 - 2026-03-13
 ===================
 

docs/api/changelog.rst

@@ -1,6 +1,6 @@
 [project]
 name = "libloot-docs"
-version = "0.29.1"
+version = "0.29.2"
 requires-python = ">=3.11"
 dependencies = [
     "breathe==4.36.0",

docs/pyproject.toml

@@ -1,6 +1,6 @@
 {
   "name": "libloot-nodejs-linux-x64-gnu",
-  "version": "0.29.1",
+  "version": "0.29.2",
   "os": [
     "linux"
   ],

docs/uv.lock

@@ -1,6 +1,6 @@
 {
   "name": "libloot-nodejs-win32-x64-msvc",
-  "version": "0.29.1",
+  "version": "0.29.2",
   "os": [
     "win32"
   ],