Release 2025.11

[jmarrero]

Release 2025.11

Alexander Larsson (1):
      Fix SELinux aliases for /usr/etc/systemd/system (and similar)

Chris Kyrouac (1):
      Update version of afterburn

Colin Walters (3):
      ci: Bump afterburn version
      ci: Update for coreos-assembler API break
      ci: Drop NEVRA override testing

Etienne Champetier (4):
      compose: sort packages before rpmtsOrder()
      treefile: merge 'repo-metadata' config
      treefile,compose: add advisories-metadata option
      compose: allow write-lockfile-to / lockfile / lockfile-strict together

Jonathan Lebon (2):
      compose: Add `--lockfile` to `rpm-ostree compose rootfs`
      compose: Add `--label` for build-chunked-oci

Joseph Marrero Corchado (1):
      Release 2025.11

Marco Hünseler (1):
      fsutil.rs: Make `is_dir` return correct information

ckyrouac (3):
      rechunker: Recursively add directories with user.component xattr
      docs: Update docs with new rechunker features
      rechunker: Parse specific components into (path, checksum)

dependabot[bot] (1):
      build(deps): bump tracing-subscriber from 0.3.19 to 0.3.20

ningmingxiao (1):
      doc:update index.md

[gemini-code-assist]

Code Review

This pull request prepares for the 2025.11 release. The changes primarily consist of version number increments in configure.ac and packaging/rpm-ostree.spec. The updates are consistent and align with the release procedures documented in RELEASE.md. I have one suggestion to improve the release process's maintainability by centralizing the version number definition, which is currently specified in two separate files. This would help prevent potential inconsistencies in future releases.

[gemini-code-assist]

The version number is defined here and also in packaging/rpm-ostree.spec. Having the version number in multiple places increases the chance of them becoming inconsistent during future releases. To improve maintainability, consider defining the version in a single source of truth (e.g., a dedicated VERSION file) and have both this file and the spec file read from it. This would simplify the release process and make it less error-prone.

[gemini-code-assist]

The version number is defined here and also in configure.ac. To improve maintainability and avoid potential inconsistencies in future releases, consider defining the version in a single source of truth (e.g., a dedicated VERSION file) and have both this spec file and configure.ac read from it. This would simplify the release process and make it less error-prone.

[openshift-ci]

@jmarrero: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/fcos-e2e	0da4313	link	true	/test fcos-e2e

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[cgwalters]

/override continuous-integration/jenkins/pr-merge

[openshift-ci]

@cgwalters: Overrode contexts on behalf of cgwalters: continuous-integration/jenkins/pr-merge

Details

In response to this:

/override continuous-integration/jenkins/pr-merge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.