Skip to content

merge queue: embarking main (9ea7a56) and #61 together#63

Closed
mergify[bot] wants to merge 9 commits intomainfrom
mergify/merge-queue/28b6cab9fd
Closed

merge queue: embarking main (9ea7a56) and #61 together#63
mergify[bot] wants to merge 9 commits intomainfrom
mergify/merge-queue/28b6cab9fd

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 14, 2026 •
edited
Loading

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (9ea7a56) and #61 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #61.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

  • #changes-requested-reviews-by=0
  • base=main
  • check-success=DCO
  • check-success=build-initramfs (amd64)
  • check-success=build-initramfs (arm64)
  • check-success=build-iso (amd64)
  • check-success=build-iso (arm64)
  • check-success=build-kernel (amd64)
  • check-success=build-kernel (arm64)
  • check-success=download-tools (amd64)
  • check-success=download-tools (arm64)
  • label!=do-not-merge
  • label=ready-to-merge
  • queue-position>=0
  • any of:
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = build-initramfs (amd64)
    • check-neutral = build-initramfs (amd64)
    • check-skipped = build-initramfs (amd64)
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = build-initramfs (arm64)
    • check-neutral = build-initramfs (arm64)
    • check-skipped = build-initramfs (arm64)
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = build-kernel (amd64)
    • check-neutral = build-kernel (amd64)
    • check-skipped = build-kernel (amd64)
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = build-kernel (arm64)
    • check-neutral = build-kernel (arm64)
    • check-skipped = build-kernel (arm64)
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = download-tools (amd64)
    • check-neutral = download-tools (amd64)
    • check-skipped = download-tools (amd64)
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = download-tools (arm64)
    • check-neutral = download-tools (arm64)
    • check-skipped = download-tools (arm64)
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = build-iso (amd64)
    • check-neutral = build-iso (amd64)
    • check-skipped = build-iso (amd64)
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = build-iso (arm64)
    • check-neutral = build-iso (arm64)
    • check-skipped = build-iso (arm64)

Required conditions to stay in the queue:

---
checking_base_sha: 9ea7a56e145379a08eaf01c1509ffa4b647f55a9
previous_failed_batches: []
pull_requests:
  - number: 61
    scopes: []
scopes: []
...

rpardini and others added 9 commits April 1, 2026 19:53
@rpardini
docker/mkosi: let /work be a regular directory, and mount specific fi…
929cdb5 
…les and dirs instead

- this avoids remote-fs errors in mkosi when running against remote Docker daemon (eg: colima, Docker Desktop)
- no, one can't simply mount tmpfs to `/work/mkosi.tools` -- mkosi wants to be able to delete it
- ideally, `mkosi.output` (a misnomer?) would also be shared across invocations using a Volume (not yet though)

Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
@rpardini
uv: pyproject.toml: add missing version field
78999f7 
- so one can use `uv run build.py` without worrying about deps

Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
@rpardini
docker/mkosi: add /cache/packages Docker Volume for download caching
3306616 
- this way we don't overwhelm Debian apt mirrors during development

Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
@rpardini
python: use standard logging and Rich
af8537c 
- drop all custom logging infra, standardize on logging
- introduce Rich for logging & exception handling
- replace custom progressbar with Rich's

Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
@rpardini
python: switch to uv everywhere
3b2dbb8 
- switch from system-breaking `pip` to fully-contained `uv`
- let `uv` install Python, don't use Debian's -- we get a single Python version for free
- also: use Docker buildx explicitly; use plain output
- build/docs: switch from plain Python+pip to uv; mention 3.13 instead of 3.10
- consolidate usage of pyproject.toml; drop old requirements-dev.txt and requirements.txt
- docker: run in interactive mode (tty) if isatty(), pass TERM/COLUMNS env
- docker: prime `uv`'s caches during Dockerfile build

Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
@rpardini
gha: better all around GHA logging with colors and wide output
f968309 
- gha/docker: force Rich colored 160-wide console under GHA
  - pass down GITHUB_ACTIONS env so children can know
- gha: reduce apt verbosity drastically with `Dpkg::Use-Pty=0`

Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
@rpardini
gha: bump to cache restore/save v5 and download/upload-artifact v6
6dc8662 
- so gha stops complaining about Node.js 20

Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
@rpardini
README.md: show uv install instructions and fix log.py and __init__.py
e93f658 
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
@mergify
Merge of #61
fbab850
@mergify mergify Bot mentioned this pull request Apr 14, 2026
Merged
@mergify mergify Bot closed this Apr 14, 2026
@mergify mergify Bot deleted the mergify/merge-queue/28b6cab9fd branch April 14, 2026 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@rpardini