Skip to content
BAML Release

chore: fix an oopsie in release.yml (#1040) #260

Sign in to view logs

chore: fix an oopsie in release.yml (#1040)

chore: fix an oopsie in release.yml (#1040) #260

Triggered via push October 14, 2024 23:19
@aaronvgaaronvg
pushed e2b990f
0.61.0
Status Startup failure
Total duration –
Artifacts –

release.yml

on: push
Matrix: build-python-release / build
Waiting for pending jobs
Matrix: build-ruby-release / build
Waiting for pending jobs
Matrix: build-typescript-release / build
Waiting for pending jobs
Build WASM
Build WASM
assert-all-builds-passed
assert-all-builds-passed
publish-to-npm
publish-to-npm
publish-to-pypi
publish-to-pypi
publish-to-rubygems
publish-to-rubygems
release-github
release-github
Fit to window
Zoom out
Zoom in

Annotations

1 error
Invalid workflow file: .github/workflows/release.yml#L92
The workflow is not valid. .github/workflows/release.yml (Line: 92, Col: 3): Error calling workflow 'BoundaryML/baml/.github/workflows/build-ruby-release.reusable.yaml@e2b990fcd9ea8938848d4ac83c54ce4d93495f41'. The workflow is requesting 'id-token: write', but is only allowed 'id-token: none'.