ci(invocation): register Helm chart release

[sbaum1994]

TL;DR

Register the HTTP invocation Helm chart as a release subproject so chart changes publish path-scoped releases and can advance the self-managed stack pin.

Additional Details

The release catalog registered the http-invocation service but omitted its chart under deploy/helm/http-invocation. Chart changes after the existing deploy/helm/http-invocation/v1.5.6 release therefore had no chart release lane, leaving the self-managed stack on 1.5.6.

This change adds the chart with its published package name, maps it to the http-invocation service, and adds a regression test for the path, package name, deployment mapping, and existing tag lineage.

Customer release notes: Not customer visible.

Plan summary: Not applicable.

Usage: Not applicable.

Notes: After merge, release automation should publish the pending invocation chart release. The chart release should then refresh #1381 with the invocation pin before that pull request is merged.

Related pull requests: #1371, #1381.

Dependencies: None. No license review or NOTICE update is required.

For the Reviewer

Please verify the http-invocation-helm identity and its deploys relationship in tools/ci/github-release-subprojects.json.

For QA

QA is not needed beyond CI release validation.

Tests run:

• python3 -m json.tool tools/ci/github-release-subprojects.json
• python3 tools/ci/test-github-release.py (47 tests passed)
• git diff --check

Issues

Closes #1385

Checklist

• I am familiar with the Contributing Guidelines.
• I have signed off my commits for Developer Certificate of Origin (DCO) compliance.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

Summary by CodeRabbit

• New Features

  • Added the HTTP invocation Helm chart to the release configuration.
  • Enabled publishing under the designated invocation service release name.

• Tests

  • Added regression coverage to verify the chart’s published path, service mapping, deployment association, and versioned tag format.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 322cd923-d09f-46c2-96b6-82873b23d527

📥 Commits

Reviewing files that changed from the base of the PR and between 2e8144d and edbc94f.

📒 Files selected for processing (2)

• tools/ci/github-release-subprojects.json
• tools/ci/test-github-release.py

Included review availability: Your plan provides up to 12 included reviews per hour; 8 remain after this review.

---

📝 Walkthrough

Walkthrough

The release catalog now includes the HTTP invocation Helm chart. A regression test verifies its path, published name, deployment mapping, and v1.5.6 tag lineage.

Changes

HTTP invocation release lineage

Layer / File(s)	Summary
Release metadata and regression coverage tools/ci/github-release-subprojects.json, tools/ci/test-github-release.py	The catalog registers deploy/helm/http-invocation as helm-nvcf-invocation-service for http-invocation. The test verifies the deployment mapping and generated v1.5.6 tag.

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

Merge Risk: ⚪ Minimal · up to edbc9

This change registers the HTTP invocation Helm chart for path-scoped releases and adds coverage for the catalog entry; no actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: mikeyrcamp

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (1 skipped: 1 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title follows Conventional Commits with the valid ci(invocation): prefix. It accurately describes the CI release-catalog change.
Linked Issues check	✅ Passed	The changes satisfy the coding objectives in issue #1385. They register deploy/helm/http-invocation with the published name helm-nvcf-invocation-service, map it to http-invocation, preserve the …
Out of Scope Changes check	✅ Passed	All changes are within scope. The release catalog entry and regression test directly support issue #1385 and the stated pull request objectives.

Full details: Linked Issues check

Explanation

The changes satisfy the coding objectives in issue #1385. They register deploy/helm/http-invocation with the published name helm-nvcf-invocation-service, map it to http-invocation, preserve the v1.5.6 lineage, and add regression coverage for the metadata and tag format.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (1 skipped: 1 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/invocation-chart-release-catalog

---

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