Skip to content

chore(release): prepare v1.0.0-rc.3 (NO NEED TO MERGE) - #463

Open
dmitsh wants to merge 1 commit into
mainfrom
v1.0.0-rc.3
Open

chore(release): prepare v1.0.0-rc.3 (NO NEED TO MERGE)#463
dmitsh wants to merge 1 commit into
mainfrom
v1.0.0-rc.3

Conversation

@dmitsh

@dmitsh dmitsh commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Signed-off-by: Dmitry Shmulevich <17212177+dmitsh@users.noreply.github.com>
@dmitsh
dmitsh requested a review from ravisoundar as a code owner August 12, 2026 00:32
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated the Topograph chart and application release versions to 1.0.0-rc.3.

Walkthrough

The Helm chart and application versions change from 1.0.0-rc.2 to 1.0.0-rc.3.

Changes

Chart release metadata

Layer / File(s) Summary
Update chart and application versions
charts/topograph/Chart.yaml
The chart and application versions change to 1.0.0-rc.3.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: ravisoundar

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive No pull request description was provided, so the change context is not documented in the description. Add a brief description that states the Helm chart and application versions changed to 1.0.0-rc.3.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the release preparation for version 1.0.0-rc.3, which matches the chart version changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch v1.0.0-rc.3

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Updates the Helm chart metadata in preparation for the v1.0.0-rc.3 release.

  • Advances the chart package version from 1.0.0-rc.2 to 1.0.0-rc.3.
  • Advances the default application/image version from v1.0.0-rc.2 to v1.0.0-rc.3.

Confidence Score: 5/5

The metadata-only release preparation appears safe to merge, with no concrete defects identified.

The chart and application versions are advanced consistently, and the available repository evidence does not establish a broken packaging, rendering, or deployment contract.

Important Files Changed

Filename Overview
charts/topograph/Chart.yaml Consistently advances both the Helm chart version and application version to the same release candidate.

Reviews (1): Last reviewed commit: "chore(release): prepare v1.0.0-rc.3" | Re-trigger Greptile

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@charts/topograph/Chart.yaml`:
- Around line 6-7: Update the documentation associated with the Topograph chart
to reflect the release metadata changes in Chart.yaml, following the required
documentation impact table. Make the documentation update within the supplied
chart scope and ensure it is included before merge.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: db9ac8cb-83d5-4d14-be10-27fd20cc4a92

📥 Commits

Reviewing files that changed from the base of the PR and between dea0a93 and e87533c.

📒 Files selected for processing (1)
  • charts/topograph/Chart.yaml
📜 Review details
🧰 Additional context used
📓 Path-based instructions (3)
charts/topograph/**/*.yaml

📄 CodeRabbit inference engine (AGENTS.md)

Do not enable both ingress.enabled and gatewayAPI.enabled in one Helm release; the routing resources are mutually exclusive.

Files:

  • charts/topograph/Chart.yaml
**/*

📄 CodeRabbit inference engine (AGENTS.md)

**/*: Do not publicly disclose suspected security vulnerabilities; report them privately through NVIDIA PSIRT using the channels documented in SECURITY.md.
Every commit must include a Signed-off-by: trailer for DCO compliance.
Use Conventional Commits with an allowed type such as feat, fix, docs, chore, refactor, test, build, or ci.
Before pushing, run make qualify; all CI checks, including Go build/test/lint, Codecov, and DCO, must be green before merge.
Changes to provider, engine, chart, API, configuration schema, labels, annotations, or user-facing behavior must include the corresponding documentation updates described in the documentation impact table.

Files:

  • charts/topograph/Chart.yaml
charts/topograph/**

⚙️ CodeRabbit configuration file

charts/topograph/**: - Check RBAC least privilege and Kubernetes API compatibility.

  • ingress.enabled and gatewayAPI.enabled must remain mutually exclusive.
  • HTTPRoute must contain only portable Gateway API v1 fields.
  • Flag changes where values, schema, templates, NOTES, tests,
    snapshots, documentation, or changelog become inconsistent.

Files:

  • charts/topograph/Chart.yaml
🧠 Learnings (5)
📚 Learning: 2026-08-08T10:57:01.397Z
Learnt from: CR
Repo: NVIDIA/topograph PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-08T10:57:01.397Z
Learning: Applies to charts/topograph/tests/**/*.{yaml,yml} : Run Helm chart tests when changing `charts/topograph/`; review snapshot changes before committing updates.

Applied to files:

  • charts/topograph/Chart.yaml
📚 Learning: 2026-08-08T10:57:01.397Z
Learnt from: CR
Repo: NVIDIA/topograph PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-08T10:57:01.397Z
Learning: Applies to **/* : Changes to provider, engine, chart, API, configuration schema, labels, annotations, or user-facing behavior must include the corresponding documentation updates described in the documentation impact table.

Applied to files:

  • charts/topograph/Chart.yaml
📚 Learning: 2026-08-08T10:57:01.397Z
Learnt from: CR
Repo: NVIDIA/topograph PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-08T10:57:01.397Z
Learning: Applies to CHANGELOG.md : Record applicable user-facing features, fixes, breaking changes, or Helm migrations under `[Unreleased]`.

Applied to files:

  • charts/topograph/Chart.yaml
📚 Learning: 2026-08-08T10:57:01.397Z
Learnt from: CR
Repo: NVIDIA/topograph PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-08T10:57:01.397Z
Learning: Applies to pkg/providers/**/*.go : Providers discover topology and return the canonical `topology.Graph`; they must not emit scheduler-specific output.

Applied to files:

  • charts/topograph/Chart.yaml
📚 Learning: 2026-08-08T10:57:01.397Z
Learnt from: CR
Repo: NVIDIA/topograph PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-08T10:57:01.397Z
Learning: Applies to pkg/providers/**/*.go : When using `ClusterTopology`, populate fabric tiers closest-first, preserve optional accelerator domain and sub-domain fields, and call `ToGraph`.

Applied to files:

  • charts/topograph/Chart.yaml
🔇 Additional comments (1)
charts/topograph/Chart.yaml (1)

6-7: 🎯 Functional Correctness

Run the chart validation and qualification checks before merge.

Run make chart-test and make qualify. Confirm that Helm lint, Helm unit tests, and all CI checks pass.

Based on learnings, changes under charts/topograph/ require Helm chart tests. As per coding guidelines, run make qualify and require all CI checks to pass before merge.

Sources: Coding guidelines, Learnings

Comment on lines +6 to +7
version: "1.0.0-rc.3"
appVersion: "v1.0.0-rc.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add the required chart documentation update.

Lines 6-7 change the chart release metadata. The supplied cohort contains only charts/topograph/Chart.yaml. Add the documentation update required by the documentation impact table before merge.

As per coding guidelines, chart changes must include the corresponding documentation updates described in the documentation impact table.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@charts/topograph/Chart.yaml` around lines 6 - 7, Update the documentation
associated with the Topograph chart to reflect the release metadata changes in
Chart.yaml, following the required documentation impact table. Make the
documentation update within the supplied chart scope and ensure it is included
before merge.

Source: Coding guidelines

@codecov

codecov Bot commented Aug 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.12%. Comparing base (8468abe) to head (e87533c).
⚠️ Report is 54 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #463      +/-   ##
==========================================
+ Coverage   72.15%   77.12%   +4.96%     
==========================================
  Files          89       99      +10     
  Lines        5689     7200    +1511     
==========================================
+ Hits         4105     5553    +1448     
+ Misses       1382     1358      -24     
- Partials      202      289      +87     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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