chore: bump _code_freeze workflow to v1.4.2 - #1047
Conversation
Signed-off-by: oliver könig <okoenig@nvidia.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Signed-off-by: oliver könig <okoenig@nvidia.com>
_code_freeze workflow to v1.4.1_code_freeze workflow to v1.4.2
Claude summary
Background / motivation
release-freeze.ymlin line with the rest of the NVIDIA-NeMo/* fleet on the latest tag of the shared_code_freeze.ymlreusable workflow.v1.4.2carries the fix that makes the bumped next-version pre-release/dev tags configurable, so a code freeze no longer re-introduces anrc0pre-release tag on clean-semver repos (fix: make code-freeze next-version pre-release/dev tags configurable FW-CI-templates#487).What changed
NVIDIA-NeMo/FW-CI-templates/.github/workflows/_code_freeze.ymlfromv0.86.0→v1.4.2.Details
.github/workflows/release-freeze.yml:37— version pin updated.Tested
release-freezedispatch.