fix(release): use an absolute path for --filename-sha256sums #11

Merged

alice merged 1 commit from fix/release-absolute-sums-path into main

2026-08-28 05:38:17 +00:00

gitea_admin commented

2026-08-28 05:37:11 +00:00

Owner

v0.2.9 got past the mirror and OpenBao-fetch issues (##10) but failed at boring-registry upload provider with "file path is not absolute: dist/terraform-provider-dmarcing_0.2.9_SHA256SUMS". Confirmed by the official docs example, which passes an absolute path -- the CLI apparently rejects a relative one outright before ever touching S3. Fixed by resolving dist/ with $(pwd).

v0.2.9 got past the mirror and OpenBao-fetch issues (##10) but failed at `boring-registry upload provider` with "file path is not absolute: dist/terraform-provider-dmarcing_0.2.9_SHA256SUMS". Confirmed by the official docs example, which passes an absolute path -- the CLI apparently rejects a relative one outright before ever touching S3. Fixed by resolving dist/ with $(pwd).

gitea_admin added 1 commit

2026-08-28 05:37:11 +00:00

fix(release): use an absolute path for --filename-sha256sums

Go lint / lint (pull_request) Successful in 55s

Details

43fcd529ea

boring-registry upload provider rejects a relative path outright
('file path is not absolute'), before it ever touches S3. dist/ is
relative to the job's working directory, so resolve it with $(pwd).