feat: Add actions and scripts to verify if conda package is available. - #94
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
karthikbekalp
force-pushed
the
chkConda
branch
3 times, most recently
from
August 31, 2026 20:47
0eaedb1 to
9677baf
Compare
crowecawcaw
reviewed
Aug 31, 2026
Comment on lines
+387
to
+393
| default_branch_ref = _fetch_default_branch(args.default_branch) | ||
| tag = resolve_release_tag( | ||
| args.requested_tag, | ||
| args.force_publish, | ||
| default_branch_ref, | ||
| ) | ||
| validate_release_tag(tag, args.default_branch, default_branch_ref) |
There was a problem hiding this comment.
Do we need to validate the tag? Could something pass in a tag upstream, maybe pull it from the rest of the github workflow that already knows it?
Author
There was a problem hiding this comment.
The tag is known by Release Prepare (the first phase of the release) , but Release Publish (the second phase which uses this workflow) runs separately on a schedule, so workflow outputs cannot be passed directly between them.
We use the Git tag as the durable handoff. Manual runs can provide the tag explicitly; scheduled runs discover the highest merged version tag. We still validate it exists and belongs to default-branch history before publishing.
Signed-off-by: Karthik BekalPattathana <133984042+karthikbekalp@users.noreply.github.com>
karthikbekalp
force-pushed
the
chkConda
branch
from
August 31, 2026 21:21
9677baf to
3dd6107
Compare
crowecawcaw
approved these changes
Aug 31, 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
3 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.
What was the problem/requirement? (What/Why)
We want to enable DCC Github repos to be able to automatically check if the conda package version is released in all regions and if so continue with the release.
What was the solution? (How)
The main problem was to know whether a conda package has been released or not.
We now have a URL: https://downloads.deadlinecloud.amazonaws.com/conda/manifest.json that tells us whether a conda package has been released or not.
So adding some reusable functions that can be utilized by any DCC Github repo to use to automatically verify if a conda package has been released.
What is the impact of this change?
Less manual steps hence faster releases
How was this change tested?
Ran a bunch of tests on my personal fork to verify the workflow worked as expected.
All guarded scenarios passed against the live manifest:
Package available
(https://github.com/karthikbekalp/deadline-cloud-for-cinema-4d/actions/runs/33427972352)
Package unavailable
(https://github.com/karthikbekalp/deadline-cloud-for-cinema-4d/actions/runs/33428061602):
Four-day timeout
(https://github.com/karthikbekalp/deadline-cloud-for-cinema-4d/actions/runs/33428555881): five-day-old
tag correctly timed out
Was this change documented?
No documentation change, just new workflow code and scripts.
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.