Skip to content

Forward-merge release/0.2 into main#117

Merged
willkill07 merged 1 commit into
mainfrom
release/0.2
May 15, 2026
Merged

Forward-merge release/0.2 into main#117
willkill07 merged 1 commit into
mainfrom
release/0.2

Conversation

@rapids-bot
Copy link
Copy Markdown

@rapids-bot rapids-bot Bot commented May 15, 2026

Forward-merge triggered by push to release/0.2 that creates a PR to keep main up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.

#### Overview

Updates the mirrored GitLab publishing workflow so NVIDIA Artifactory publication is triggered by a tag push instead of a GitLab pipeline schedule.

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

- Changes the GitLab workflow and Artifactory publish jobs to run on `CI_COMMIT_TAG` tag push pipelines.
- Uses the GitLab tag directly when waiting for the mirrored GitHub tag and matching GitHub Actions artifact run.
- Removes the scheduled nightly-alpha tag calculation from the GitLab collector path.
- Documents that the mirrored GitLab Artifactory publishing path is tag-driven and does not require a GitLab cron.

#### Where should the reviewer start?

Start with `.gitlab-ci.yml` to review the trigger and artifact collection change, then `RELEASING.md` for the release-process documentation update.

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Relates to: none

## Summary by CodeRabbit

* **Chores**
  * Refactored CI/CD pipeline to trigger releases via tag pushes instead of scheduled builds, updating artifact collection and publication workflows.

* **Documentation**
  * Updated release process documentation to describe tag-driven publishing to Python, Cargo, and npm registries.

Signed-off-by: Will Killian <wkillian@nvidia.com>
@rapids-bot rapids-bot Bot requested a review from a team as a code owner May 15, 2026 11:12
@rapids-bot
Copy link
Copy Markdown
Author

rapids-bot Bot commented May 15, 2026

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

@github-actions github-actions Bot added the size:S PR is small label May 15, 2026
@willkill07 willkill07 removed the size:S PR is small label May 15, 2026
@willkill07 willkill07 merged commit 02a73f9 into main May 15, 2026
16 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant