Repository navigation
ci: on demand release - #10544
Draft
pvijayakrish wants to merge 68 commits into
Draft
ci: on demand release#10544pvijayakrish wants to merge 68 commits into
pvijayakrish wants to merge 68 commits into
Conversation
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
…nd workflow Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
…nd workflow Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
pvijayakrish
force-pushed
the
pvijayakrish/on-demand-release
branch
from
June 10, 2026 22:54
fbcd220 to
c0ed157
Compare
pvijayakrish
temporarily deployed
to
automated-release
June 10, 2026 22:54 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
pvijayakrish
temporarily deployed
to
manual-release-approval
June 10, 2026 22:55 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
pvijayakrish
had a problem deploying
to
automated-release
June 10, 2026 23:02 — with
GitHub Actions
Failure
GitHub Actions
Failure
pvijayakrish
had a problem deploying
to
automated-release
June 10, 2026 23:02 — with
GitHub Actions
Failure
GitHub Actions
Failure
pvijayakrish
had a problem deploying
to
automated-release
June 10, 2026 23:02 — with
GitHub Actions
Failure
GitHub Actions
Failure
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
pvijayakrish
temporarily deployed
to
automated-release
June 15, 2026 04:56 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
pvijayakrish
temporarily deployed
to
manual-release-approval
June 15, 2026 04:59 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
pvijayakrish
had a problem deploying
to
automated-release
June 16, 2026 00:36 — with
GitHub Actions
Failure
GitHub Actions
Failure
pvijayakrish
had a problem deploying
to
automated-release
June 16, 2026 00:36 — with
GitHub Actions
Failure
GitHub Actions
Failure
Re-stages 1.4.0 off the existing release/1.4.0 branch as rc.2 (staging registries are immutable, so each round needs a distinct rc). Signed-off-by: Nate Mailhot <nmailhot@nvidia.com>
…d-release Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com> # Conflicts: # .github/workflows/release.yml
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
…i-dynamo/dynamo into pvijayakrish/on-demand-release # Conflicts: # .github/workflows/on-demand-release.yml
TEMPORARY redirect of the push-flow fallbacks from 1.4.0/rc3 to 1.3.1/rc1 to stage a patch-line RC off the existing release/1.3.1 branch. release/1.3.1 is already stamped 1.3.1 (#12144), so the bump step is a no-op there. Reverted immediately after the run launches so the branch returns to its 1.4.0 rc3 configuration. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Nate Mailhot <nmailhot@nvidia.com>
This reverts commit e379911, restoring the push-flow fallbacks to the 1.4.0 rc3 configuration they held before the temporary 1.3.1 redirect. The 1.3.1 rc1 run (30951218544) already launched off e379911 and carries its own snapshot of the workflow definition, so this revert does not affect it. [skip ci] because the push trigger would otherwise fire a 1.4.0 rc3 run, and rc3 was already staged on 2026-08-04 — the staging registries are immutable, so a re-run would collide. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Nate Mailhot <nmailhot@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Velonix job admission (velonix#556) only admits push on main, release/*, and pull-request/N. Switch the trigger to pull-request/[0-9]+, the same filter fern-docs.yml uses. Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test ca4e947 |
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test 0c51cb6 |
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test 5f08993 |
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test ed9fb05 |
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test 1d880a5 |
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test b976324 |
rewrite_image_refs only matches <reg>/<img>:<tag>, so a re-cut moved the image clipboards in docs/fern/components/releases.data.ts but left every sibling label:, publishing a page whose copy button contradicts its label. The file also lists per-model dev lines and dated nightlies at the same version literal, which must never move, so a blanket rewrite would corrupt release history. Skip the file and warn instead. Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test 97b3ae1 |
… root lib/bindings/python, lib/bindings/kvbm and lib/runtime/examples are separate cargo workspaces with their own lock files. The root-only 'cargo update --workspace' left their workspace-crate pins on the previous version, so the 1.4.1 cut (9f6c6be) shipped three stale locks and the pre-merge clippy matrix failed 'cargo metadata --locked' in all three. Lock files are discovered from git so a new nested workspace cannot regress this. Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test 8f49180 |
Push-loop fallbacks now cut release_version 1.4.2 from release/1.4.1.
The existing release/1.4.2 branch is reused: the version stamp lands on
top of its cherry-picks and the push fires post-merge builds.
Also stamp the workspace-version pin in member-manifest inline dep
tables (new WORKSPACE_PIN_CARGO_TARGETS): backend-common pins
`dynamo-llm = { path = "../llm", version = "1.4.1", ... }` because
cargo cannot express workspace = true + default-features = false, and
VERSION_LINE_RE deliberately skips inline tables — without this the
1.4.2 stamp would leave the pin at 1.4.1 and backend-common would
publish declaring a stale dynamo-llm dependency.
Signed-off-by: pvijayakrish <pvijayakrish@nvidia.com>
Contributor
Author
|
/ok to test 7a2d51f |
This branch was successfully deployed
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.
Overview:
Details:
Where should the reviewer start?
Related Issues
🔗 This PR is linked to an issue:
🚫 This PR is NOT linked to an issue: