chore(common): bump the common submodule to 4de5dfa and adopt the tree-ownership guard #100
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/GOV-45-update-common-submodule"
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?
Bumps the
commonsubmodule gitlink fromc809345to4de5dfa(currentpsa-systems/commonmain) and ports the new tree-ownership guard into this repo'spre-commitoverride. Part of the cross-repo sync tracked in GOV-45.What the new pin brings in: the reusable check workflow's
compile_step/test_args/cacheinputs and its runner-label switch toRUNS_ON_OPENSUSE_DEV_LATEST, thedev_extra_volumesvariable ondev-clean, thevirtual-workspacerelease layout, the nu line-continuation fix inbuild-docker-export, and thecheck-tree-ownershiprecipe.vervain-apps overrides
pre-commit(it builds Tailwind first, checks the wasm target, and feature-gates clippy and the tests), so guards added inside common's own variants do not reach this repo through the gitlink alone.just check-tree-ownershipis ported into the override and runs after the tests: it fails the commit if any path in the working tree is not owned by the host user. That is the same failure thebuild-cssrecipe already guards against from the other side by running the bun container as the host uid/gid, so the two now cover both directions.Not applicable here:
defaultis already the first recipe, the rootCargo.tomlis a single-package manifest so thegenericrelease layout still holds, there is nocompose.dev.ymlsodev_extra_volumeshas nothing to add, and vervain-apps ships its owncheck.ymlrather than calling the shared workflow.Verification:
just pre-commitpasses on the new pin (Tailwind build, fmt, clippy with--features server,cargo check --features server,cargo check --target wasm32-unknown-unknown, 102 tests, andcheck-tree-ownershipreports the working tree fully owned by the host user).#GOV-45