Repository navigation
chore(release): prepare v0.6.8 - #66
Merged
Merged
Conversation
Version 0.6.7 -> 0.6.8 on the same 21 lines in 15 files as v0.6.7. Pin Dockiva Engine b8bb543 -> 08c7901.
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.8 on the same 21 lines in 15 files as #63. It also pins Dockiva Engine to
08c7901(fromb8bb543).What changes for users
Containers in the app (#65):
Dockiva Engine (Tomnerb/dockiva-engine#7, #13 to #28):
xt_CONNMARK.handxt_connmark.h. The first start after the update moves each engine home into a case-sensitive store, a sparse bundle the engine attaches. The store detaches when the engine stops.RUNsteps have no memory limit, as in Docker, unlessdocker build -msets one. Before, the 2 GiB default gotgo buildkilled.apkpackage scripts run again: exec of an open file (fexecve,/dev/fd/N) works.go buildlinks again. Shared file mappings are written back and released when their process exits, and the Go linker can map a large module's archives.linux/amd64Go builds and runs under FEX:GODEBUG=asyncpreemptoff=1).docker rm -fanddocker stopof a running--rmcontainer no longer answer 500 (build(deps-dev): bump vite from 7.3.6 to 8.3.4 in /frontend #13).sudoworks afteraptin the same container (build(deps): bump github.com/containerd/containerd/v2 from 2.3.4 to 2.4.0 #17).Not in this release: running the amd64 Go toolchain under FEX can still hit a FEX bug (vfork pipe) and an unexplained fault. Use a native
--platform=$BUILDPLATFORMbuilder stage when an amd64 Go build fails.Checks
DOCKIVA_ENGINE_REF.08c7901is on engine main, and v0.6.7's pinb8bb543is an ancestor of it.go test ./...andswift test --package-path macospass. The macOS app builds (arm64,--external-only, ad-hoc signed).08c7901. Its tree is identical to the combined tree of build(deps): bump github.com/containerd/containerd/v2 from 2.3.4 to 2.4.1 #18 to Bind mounts and volumes for the VM-free engine #28 tested before merging:verify_fork_sockets.py: 95 of 95 at--cpus 1and--cpus 4.go -C dockivad test -race: ok.corpus) passed on every PR.08c7901's bundle, built withbundle_dockiva_engine.pyfor this release:verify_dockivad.pypasses 31 of 31. The first run timed out at the script's 10-second startup wait, on the first launch of the freshly built binaries; the rerun passed.release.ymlis unchanged since v0.6.7. Its runner labels areubuntu-24.04,ubuntu-24.04-arm,macos-26andwindows-2025.Not checked
--guest-assets) on this branch. The release workflow builds that.After merge: tag main
v0.6.8.