Repository navigation
chore(release): prepare v0.6.9 - #68
Merged
Merged
Conversation
chandarith-chea
force-pushed
the
release-v0.6.9
branch
from
November 14, 2026 02:09
934da10 to
19a6381
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This bumps the version to 0.6.9 on the same 21 lines in 15 files as #66. It also pins Dockiva Engine to
af13b2b(from08c7901).What changes for users
Dockiva Engine (Tomnerb/dockiva-engine#29 to #32):
docker/build-push-actionno longer hangs in its post step (chore(release): prepare v0.3.4 #31). With buildx older than 0.23, the action's build summary opens both ends of two named pipes (FIFOs) from two threads of one Node process. The engine paired a FIFO open only with another process, so those threads waited for each other forever and the job never finished. Threads of one process now pair as on Linux.docker run -mgets Docker's swap allowance (VM-free: exec, -it, networks, Compose, limits and faster writes #30). Without--memory-swap, a container may use as much swap again as its-m, as on Docker. Avite buildthat was OOM-killed at-m 6gnow passes.--memory-swapequal to-mkeeps the strict limit.free,/proc/meminfo,docker inspectanddocker statsreport it.docker statsalso counts a container's running execs.tar -xfof an archive with a./entry into an existing image directory (e.g.actions/setup-node-style extraction) no longer fails with "Directory renamed before its status could be extracted".taras root no longer fails on symlinks (VM-free: 21 popular images run, image size limits removed #32). Anopen(O_PATH|O_NOFOLLOW)of a symlink opens the link, as on Linux. Before, glibc'sfchmodat(AT_SYMLINK_NOFOLLOW)gotELOOP, so extractingnode_modules/.binlinks printed "Too many levels of symbolic links" and tar exited 2.Checks
DOCKIVA_ENGINE_REF.af13b2bis engine main's tip, and v0.6.8's pin08c7901is an ancestor of it. Engine CI (corpus) passed onaf13b2b.go test ./...passes.af13b2b, bundle built withbundle_dockiva_engine.pyfor this release:verify_dockivad.py --new-homepasses 31 of 31.verify_fork_sockets.py --cpus 4: 100 PASS, 0 FAIL, including the newfifo_threads_guestandopath_link_guest.release.ymlis unchanged since v0.6.8. Its runner labels areubuntu-24.04,ubuntu-24.04-arm,macos-26andwindows-2025.Not checked
swift testand a local macOS app build on this branch. Only version lines changed since v0.6.8, which passed both.--guest-assets) on this branch. The release workflow builds that.After merge: tag main
v0.6.9.