Skip to content

chore: update Cinema 4D OpenJD recipe to 0.12.1 - #285

Open
karthikbekalp wants to merge 1 commit into
aws-deadline:mainlinefrom
karthikbekalp:chore/cinema4d-openjd-0.12.1
Open

chore: update Cinema 4D OpenJD recipe to 0.12.1#285
karthikbekalp wants to merge 1 commit into
aws-deadline:mainlinefrom
karthikbekalp:chore/cinema4d-openjd-0.12.1

Conversation

@karthikbekalp

Copy link
Copy Markdown
Contributor

Summary

  • update the Cinema 4D OpenJD adaptor recipe from 0.11.4 to 0.12.1
  • use the official PyPI source archive SHA256
  • align the Deadline runtime constraint with the upstream release metadata

Verification

  • python3 scripts/validate_repository.py
  • built and tested the package for linux-64 and win-64 using the Deadline Cloud package build workflow
  • completed a one-frame Cinema 4D 2026.3.3 smoke render with cinema4d-openjd=0.12.1

Signed-off-by: Karthik BekalPattathana <133984042+karthikbekalp@users.noreply.github.com>
@karthikbekalp
karthikbekalp requested a review from a team as a code owner August 18, 2026 18:02
@karthikbekalp
karthikbekalp enabled auto-merge (squash) August 18, 2026 18:04
@github-actions github-actions Bot added the waiting-on-maintainers Waiting on the maintainers to review. label Aug 18, 2026
run:
- python
- deadline >=0.59,<0.60
- deadline >=0.60.1,<0.61

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new floor deadline >=0.60.1 cannot be satisfied by this repo's own deadline sample recipe, which is still pinned at 0.54.3 (see conda_recipes/deadline/recipe/recipe.yaml line 5). Anyone who builds the sample recipes into a single conda channel and then builds or installs cinema4d-openjd 0.12.1 will hit an unsatisfiable run dependency. The gap existed before this change (>=0.59 vs 0.54.3) but this widens it.

Relatedly, the header comment updated on line 3 now describes the divergence backwards. It says the standalone deadline sample "may track a newer, incompatible minor release", but that sample actually tracks an older release (0.54.3), so the caveat does not warn readers about the failure mode they will actually hit.

openjd-adaptor-runtime is fine here: the sample recipe is at 0.9.3, inside >=0.7,<0.10.

Suggest either bumping conda_recipes/deadline to a 0.60.x release alongside this change, or correcting the comment to say the standalone sample may track an older, incompatible minor release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-on-maintainers Waiting on the maintainers to review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant