Instead of crating MRs, renovate will:
- Create the branch, wait for test results
- Rebase it any time it gets out of date with the base branch
- Automerge the branch commit if it's:
(a) up-to-date with the base branch, and
(b) passing all tests
- As a backup, raise a PR only if either:
(a) tests fail, or
(b) tests remain pending for too long (default: 24 hours)
Resolves#62
Signed-off-by: Miguel Martín <mmartinv@redhat.com>
Changes in `bootc-base-imagectl` and `install-manifests` files
must trigger konflux builds for all the existing base images.
Also changes in "minimal" or "minimal-plus" must trigger konflux
builds in all the "standard" images.
Signed-off-by: Miguel Martín <mmartinv@redhat.com>
chore(deps): update quay.io/bootc-devel/fedora-bootc-rawhide-compose docker tag to fedora-rawhide-20250627.n.0 (main)
See merge request fedora/bootc/base-images!230
chore(deps): update quay.io/bootc-devel/fedora-bootc-rawhide-compose docker tag to fedora-rawhide-20250626.n.0 (main)
See merge request fedora/bootc/base-images!227
chore(deps): update quay.io/bootc-devel/fedora-bootc-42-compose docker tag to fedora-42-updates-testing-20250627.0 (main)
See merge request fedora/bootc/base-images!226
chore(deps): update quay.io/bootc-devel/fedora-bootc-rawhide-compose docker tag to fedora-rawhide-20250625.n.0 (main)
See merge request fedora/bootc/base-images!223
chore(deps): update quay.io/bootc-devel/fedora-bootc-42-compose docker tag to fedora-42-updates-testing-20250625.0 (main)
See merge request fedora/bootc/base-images!222
chore(deps): update quay.io/bootc-devel/fedora-bootc-42-compose docker tag to fedora-42-updates-testing-20250624.0 (main)
See merge request fedora/bootc/base-images!220
chore(deps): update quay.io/bootc-devel/fedora-bootc-rawhide-compose docker tag to fedora-rawhide-20250623.n.0 (main)
See merge request fedora/bootc/base-images!221
chore(deps): update quay.io/bootc-devel/fedora-bootc-42-compose docker tag to fedora-42-updates-testing-20250623.0 (main)
See merge request fedora/bootc/base-images!219
chore(deps): update quay.io/bootc-devel/fedora-bootc-rawhide-compose docker tag to fedora-rawhide-20250622.n.0 (main)
See merge request fedora/bootc/base-images!215
Not sure why but when you try to build c9s with rpm-ostree from
git main the change in [1] causes the sed commands here to exit
with a weird error:
```
sed: couldn't close stdout: Bad file descriptor
```
Let's just redirect to /dev/null for now and maybe we can drop
it longer term when c9s goes away. See also [2] where this was
reported.
[1] f4aecb9b62
[2] https://github.com/coreos/rpm-ostree/pull/5388#issuecomment-2971623787
chore(deps): update quay.io/bootc-devel/fedora-bootc-rawhide-compose docker tag to fedora-rawhide-20250619.n.0 (main)
See merge request fedora/bootc/base-images!206
Those are more like package requests than package names, so things like
`foo > 1.0` should be supported.
Pass the install arguments through `shlex.quote`.
chore(deps): update quay.io/bootc-devel/fedora-bootc-42-compose docker tag to fedora-42-updates-testing-20250619.0 (main)
See merge request fedora/bootc/base-images!212
We don't currently want the minimal-plus target to be user-facing. It's
intended only for other Fedora variants.
Let's support "hidden" manifests by having their names end in
`.hidden.yaml`. Then, make `minimal-plus` hidden.
I considered instead having them start with `.` to match
well-established semantics, but I don't like either that this hides them
from an `ls` in the git repo (or even with `-a`, puts them higher up
whereas I want it to be close to `minimal.yaml`).
I also considered leveraging the existing symlink hiding semantics, but
it also felt awkward to rename a file and add a symlink to it just for
the purpose of hiding it.
The `if os.path.isdir(args.manifest)` bit dates from the introduction
of this script, but doesn't really work. I suspect the intent here was
to abstract over some manifests being top-level YAML files and others
being directories).
Except that:
1. The script didn't actually check the right path. It's checking
`$PWD/{args.manifest}` instead of `$MANIFESTDIR/{args.manifest}`.
2. `list` doesn't have the equivalent logic to look for `manifest.yaml`
files in subdirectories.
3. Nowadays, there is both a e.g. `standard.yaml` _and_ a
`standard/manifest.yaml` directory. The established semantic there
AIUI is that the top-level manifests are opinionated for a specific
OS (Fedora/CentOS/RHEL), whereas the directories are shared across
all of those.
So let's just nuke support for the directory path.
It's confusing right now how the manifest names differ across
fedora-bootc, centos-bootc and rhel-bootc. Both rhel-bootc and
centos-bootc only use "bare" names like `minimal`, and `standard`, while
fedora-bootc prefixes everything with `fedora-`.
For FCOS/SCOS/RHCOS, it would be beneficial to maintain the same naming
across all of those.
Let's just match the naming here to the "bare" version. But add symlinks
so that we don't break the old names (but note that being symlinks, they
will no longer show up in `bootc-base-imagectl list`).
