Release 1.6.0

crates/cli/Cargo.toml

@@ -16,7 +16,7 @@ platforms = ["*-unknown-linux-gnu"]
 [dependencies]
 anstream = { workspace = true }
 anyhow = { workspace = true }
-bootc-lib = { version = "1.0", path = "../lib" }
+bootc-lib = { version = "1.6", path = "../lib" }
 bootc-utils = { package = "bootc-internal-utils", path = "../utils", version = "0.0.0" }
 tokio = { workspace = true, features = ["macros"] }
 log = "0.4.21"

crates/lib/Cargo.toml

@@ -6,7 +6,7 @@ name = "bootc-lib"
 repository = "https://github.com/bootc-dev/bootc"
 # The intention is we'll follow semver here, even though this
 # project isn't actually published as a crate.
-version = "1.5.1"
+version = "1.6.0"
 # In general we try to keep this pinned to what's in the latest RHEL9.
 # However right now, we bumped to 1.82 as that's what composefs-rs uses.
 rust-version = "1.82.0"

docs/src/man/bootc-container-lint.md

@@ -53,4 +53,4 @@ part of a build process; it will error if any problems are detected.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-container.md

@@ -30,4 +30,4 @@ bootc-container-help(8)
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-edit.md

@@ -36,4 +36,4 @@ Only changes to the \`spec\` section are honored.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-install-ensure-completion.md

@@ -27,4 +27,4 @@ your code is using \`bootc install to-filesystem\` from the start.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-install-finalize.md

@@ -24,4 +24,4 @@ to-filesystem\`
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-install-print-configuration.md

@@ -27,4 +27,4 @@ string-valued filesystem name suitable for passing to \`mkfs.\$type\`.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-install-to-disk.md

@@ -160,4 +160,4 @@ more complex such as RAID, LVM, LUKS etc.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-install-to-existing-root.md

@@ -152,4 +152,4 @@ to be cleaned up if desired when rebooted into the new root.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-install-to-filesystem.md

@@ -34,25 +34,13 @@ is currently expected to be empty by default.
 
     If not provided, the UUID of the target filesystem will be used.
 
-    If the value is empty, i.e. passing `--root-mount-spec=`, the mount
-    spec kernel argument will be ommited entirely.
-    In this case the initramfs must have another way to find the rootfs,
-    such as a partition label or follow the Discoverable Partition
-    Specification.
-
 **\--boot-mount-spec**=*BOOT_MOUNT_SPEC*
 
 :   Mount specification for the /boot filesystem.
 
     This is optional. If \`/boot\` is detected as a mounted partition,
     then its UUID will be used.
 
-    If the value is empty, i.e. passing `--boot-mount-spec=`, the mount
-    spec kernel argument will be ommited entirely.
-    In this case the initramfs must have another way to find the boot
-    parition, such as a partition label or follow the Discoverable
-    Partition Specification.
-
 **\--replace**=*REPLACE*
 
 :   Initialize the system in-place; at the moment, only one mode for
@@ -185,4 +173,4 @@ is currently expected to be empty by default.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-install.md

@@ -71,4 +71,4 @@ bootc-install-help(8)
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-rollback.md

@@ -55,4 +55,4 @@ happen when new deployments are created.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-status.md

@@ -63,4 +63,4 @@ not \`null\`.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-switch.md

@@ -65,4 +65,4 @@ updates via container image tags; for example,
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-upgrade.md

@@ -53,4 +53,4 @@ the update in addition.
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc-usr-overlay.md

@@ -39,4 +39,4 @@ unmount\".
 
 # VERSION
 
-v1.5.1
+v1.6.0

docs/src/man/bootc.md

@@ -72,4 +72,4 @@ bootc-help(8)
 
 # VERSION
 
-v1.5.1
+v1.6.0