Both repository workflows need a network: verify fetches modules for the build,
vet, license scan, vulnerability scan, packaging, and tests; release fetches the
module graph and packaging tools for the tag build.
Until now they relied on the runner’s --container-network bridge default. A runner
started with --container-network none would still take the job and fail at the
first fetch, which is the confusing failure network: exists to prevent.
This declares network: bridge on both jobs:
.vole/workflows/verify.yaml— theverifyjob.vole/workflows/release.yaml— thereleasejob
The field is already parsed, pinned with the run, and honoured by the runner and the local run, so this is the follow-up recorded under #138 §5, not a format change.
Checks: vole workflow check and vole workflow run verify pass.