Repository navigation
v0.4.3
[0.4.3] - 2026-04-28
The "make the action actually invokable" patch release. No new
features; fixes a layout bug that has silently broken every consumer
trying to use Metbcy/bomdrift@v1 since v0.1.0 was tagged.
Fixed
-
action.ymlmoved fromaction/action.ymlto the repo root.
GitHub Actions resolves a composite action's manifest at the repo
root by default; subdirectory actions require consumers to type
Metbcy/bomdrift/action@v1instead ofMetbcy/bomdrift@v1. Every
example in the README and docs site used the latter form, so any
consumer copying those snippets hit:Can't find 'action.yml', 'action.yaml' or 'Dockerfile' for action 'Metbcy/bomdrift@v1'.The bug surfaced when bomdrift's own dogfood workflow (introduced
in60e772d) tried to self-invokeMetbcy/bomdrift@v1and
failed for the same reason. With the manifest at the repo root,
Metbcy/bomdrift@v1(the form the docs always advertised) now
works.entrypoint.shmoved alongside it; the
${{ github.action_path }}/entrypoint.shreference continues
to resolve correctly because that variable points at whatever
directory contains the loadedaction.yml.Note: this is a v0.x patch release, so the layout change is fine
for existing consumers who pinned to a prior tag (those tags still
work as they always did — broken). v1.0 will keepaction.ymlat
the root permanently.
Verifying signatures
Each archive is signed with cosign keyless (Sigstore via GitHub OIDC). To verify a download:
cosign verify-blob \
--certificate-identity 'https://github.com/Metbcy/bomdrift/.github/workflows/release.yml@refs/tags/v0.4.3' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate bomdrift-v0.4.3-<target>.<ext>.pem \
--signature bomdrift-v0.4.3-<target>.<ext>.sig \
bomdrift-v0.4.3-<target>.<ext>