-
Notifications
You must be signed in to change notification settings - Fork 230
Comparing changes
Open a pull request
base repository: bootc-dev/bootc
base: v1.16.8
head repository: bootc-dev/bootc
compare: v1.16.9
- 10 commits
- 17 files changed
- 7 contributors
Commits on Aug 19, 2026
-
ci: Skip heavy test jobs for docs-only PRs
Assisted-by: AI Signed-off-by: gursewak1997 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 316248c - Browse repository at this point
Copy the full SHA 316248cView commit details -
fix(deps): update bcvk-qemu digest to d0433d9
Signed-off-by: bootc-bot[bot] <225049296+bootc-bot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for fceedf6 - Browse repository at this point
Copy the full SHA fceedf6View commit details
Commits on Aug 20, 2026
-
ci: Fix docs-only detection in compute-ci-level
The previous attempt (merged in #2391) failed silently because compute-ci-level had no checkout step, so gh pr diff could not infer the repository and produced empty output. The pipe into grep swallowed the error, setting docs_only=true for all PRs. Fix by adding a sparse checkout for PR events, separating the gh pr diff fetch from the grep so failures abort via set -euo pipefail, and guarding empty output explicitly. Assisted-by: AI Signed-off-by: gursewak1997 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 04a675c - Browse repository at this point
Copy the full SHA 04a675cView commit details -
test-install: Fix chunkah hang
`priv-integration.sh` was hanging at the chunkah step where we mount an entire image inside a podman container. In the logs I can see `overlay.mount_program=/usr/local/bin/fuse-overlayfs` which might be causing the test to timeout since fuse-overlayfs is pretty slow and the image has tons of layers. Switch to native overlay diff which hopefully fixes the issue Also, skip networking for chunkah container as I see podman hanging at ``` time="2026-08-20T07:45:34Z" level=debug msg="Adding mount /dev" time="2026-08-20T07:45:34Z" level=debug msg="Adding mount /dev/pts" time="2026-08-20T07:45:34Z" level=debug msg="Adding mount /dev/mqueue" time="2026-08-20T07:45:34Z" level=debug msg="Adding mount /sys" time="2026-08-20T07:45:34Z" level=debug msg="Adding mount /sys/fs/cgroup" time="2026-08-20T07:45:34Z" level=debug msg="Successfully loaded 1 networks" ``` Convert the image to an oci dir instead of trying to mount the entire image Signed-off-by: Pragyan Poudyal <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for f280385 - Browse repository at this point
Copy the full SHA f280385View commit details -
ci: Temporarily disable test-install job
This job has been hanging in the chunkah/podman step for hours even after the native-overlay fix in the previous commit, likely blocking this PR and others behind unrelated CI infrastructure flakiness. Disable it for now via if: false (same pattern used for test-coreos) so it reports as skipped rather than pending/failed, and doesn't block required-checks-heavy. Re-enable once the hang is root-caused. Assisted-by: AI Signed-off-by: Colin Walters <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for fa96d7a - Browse repository at this point
Copy the full SHA fa96d7aView commit details -
lib/container_export: Always skip /tmp and /var/tmp during export
CentOS 10 UKI CI jobs fail "bootc container export --format=tar" with "No label found in policy ... for /var/tmp/rhc". rhc's post-install scriptlet drops runtime state under /var/tmp during image build (same rhc-1:0.3.12-1.el10 build in both passing and failing CI runs, so this isn't a version regression in rhc itself), and the SELinux targeted policy simply has no file-context entry for it. This only reproduces reliably on the composefs+uki matrix legs, likely because that build path takes long enough for the scriptlet's async write to land before the image layer is committed - the file can be present or absent on other legs depending on timing. Rather than trying to tolerate arbitrary unlabeled paths anywhere in the tree (which risks silently exporting genuinely mislabeled files), extend the existing SKIP_PATHS list to always exclude /tmp and /var/tmp. These are meant to hold only ephemeral, runtime-created content - ostree-ext::commit's FORCE_CLEAN_PATHS already treats the same two paths (plus /run and /var/cache) this way for regular ostree commits, so tar export dropping them is consistent with how bootc already treats the real /var as not being part of the shippable content. Add a unit test exercising export_filesystem_walk() directly (with SELinux labeling disabled) against a synthetic root, verifying /tmp and /var/tmp content is dropped while everything else is kept. Assisted-by: AI Signed-off-by: Colin Walters <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 9595534 - Browse repository at this point
Copy the full SHA 9595534View commit details -
docs: Add release process documentation
Document bootc's release process, versioning strategy, and support policies for CNCF incubation (Issue #36). Covers semantic versioning, weekly release cadence, the automated release workflow, release assets, GPG-signed tags, pre-releases, security releases, and stability guarantees. Reflects decisions from the August 2026 community meeting: releases are tagged from main with no release branches or backporting, deprecations are announced in minor releases, and feature releases use minor version bumps. Support duration and the deprecation advance-notice window remain open questions pending broader maintainer input. Co-Authored-By: Claude Opus 4.8 <[email protected]> Signed-off-by: mohan-shash <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6e640be - Browse repository at this point
Copy the full SHA 6e640beView commit details -
Add ROADMAP.md following the containerd model, using GitHub issues as the "what" and milestones as the "when" rather than a static list that quickly goes stale. Includes bootc's strategic direction and guidance on how the community can contribute to the roadmap (Issue #35). Co-Authored-By: Claude Opus 4.8 <[email protected]> Signed-off-by: mohan-shash <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 093ff7b - Browse repository at this point
Copy the full SHA 093ff7bView commit details
Commits on Aug 21, 2026
-
docs: Document tmpfs-backed storage for usr-overlay
The transient overlay created by `bootc usr-overlay` is backed by a tmpfs filesystem, meaning installed packages consume system RAM rather than persistent disk. The kernel default sizes this tmpfs at 50% of physical RAM, and there is currently no pre-flight space check before the overlay fills up. This is not obvious from the existing documentation and can lead to confusing ENOSPC errors on memory-constrained systems such as CI runners or small VMs, where users may assume the overlay uses disk storage. Assisted-by: AI Signed-off-by: Joseph Marrero Corchado <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 319e42d - Browse repository at this point
Copy the full SHA 319e42dView commit details -
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 850b12f - Browse repository at this point
Copy the full SHA 850b12fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.16.8...v1.16.9