[release] Declare forge as an explicit depends_on for publish steps#62687
Merged
[release] Declare forge as an explicit depends_on for publish steps#62687
Conversation
The four :crane: publish: steps in build.rayci.yml run inside the forge docker image (via the default docker plugin), but the dependency on the forge wanda step was implicit — not declared via depends_on. In the default unpruned pipeline this works because rayci includes every step regardless, but under RAYCI_SELECT pruning (where only the selected step and its transitive upstream deps are emitted), the forge step gets filtered out and the publish step crashes with "manifest for citemp:{build_id}-forge not found".
Making the dep explicit lets rayci's upstream dep walker include forge in the pruned pipeline whenever any publish step is selected.
Topic: release-publish-forge-deps
Signed-off-by: andrew <andrew@anyscale.com>
Contributor
Author
Contributor
Author
This was referenced Apr 16, 2026
andrew-anyscale
force-pushed
the
andrew/revup/master/release-publish-forge-deps
branch
from
b23adc4 to
da77ea3
Compare
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the Buildkite release configuration in .buildkite/release/build.rayci.yml by adding a dependency on the forge step for several image build and upload tasks, including CPU, CUDA, LLM, and ML variants. I have no feedback to provide as there are no review comments.
aslonnie
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The four :crane: publish: steps in build.rayci.yml run inside the forge docker image (via the default docker plugin), but the dependency on the forge wanda step was implicit — not declared via depends_on. In the default unpruned pipeline this works because rayci includes every step regardless, but under RAYCI_SELECT pruning (where only the selected step and its transitive upstream deps are emitted), the forge step gets filtered out and the publish step crashes with "manifest for citemp:{build_id}-forge not found".
Making the dep explicit lets rayci's upstream dep walker include forge in the pruned pipeline whenever any publish step is selected.
Topic: release-publish-forge-deps
Signed-off-by: andrew andrew@anyscale.com