release: v0.4.2 — don't export BUBBLEBOX_PROFILE when the profile is absent #12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release/v0.4.2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes the second stacked cause of the pkgs publish failure (run 116), then bumps to 0.4.2 so it can ship immediately — one PR, one merge, one tag.
The bug (mine, from the v0.3.0
--profilework):export_envpublishedBUBBLEBOX_PROFILEeven when it resolved to a profile that doesn't exist. Nested engine invocations inherit it and treat it as an explicit location — so on a host with no profile.toml (the nightly/publish store), every composing package died in smoke withprofile not found(rust-dev'scommand -v cargo, nvim, and two more in run 116). The thinkpad never saw it because its profile exists.Fix: export the profile only when it exists; profile-less hosts resolve the same (missing) default in children instead of erroring.
cargo test --workspace: 137 pass, including a regression test for both cases. Live-verified end to end on bee:bubblebox run nvim(composes rg/fd via the nested child) with no profile present now works; before the fix it printed exactly the CI error.After merge: tag
v0.4.2(I'll do it), pkgs CI pin follows, publish re-dispatched (I'll do both). Then the cache finally gains the 66 unpublished packages and cn#79 unblocks.