docs: add proto versions table docs

[baktun14]

🌟 Add protobuf table docs for better visibility

📝 Description

Added a markdown table to map protobuf types and their versions

🔧 Purpose of the Change

• New feature implementation
• Bug fix
• Documentation update
• Code refactoring
• Dependency upgrade
• Other: [specify]

[coderabbitai]

Walkthrough

Adds a new documentation file detailing protobuf message/proto types and their supported versions across node and provider modules. No code or API changes.

Changes

Cohort / File(s)	Change summary
Documentation docs/proto-versions.md	Introduces tables mapping modules to message/proto types with version support (v1beta3/v1beta4/v1beta5/v1 for node modules; v1/v2beta3 for provider modules). Purely docs; no code or API modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I twitch my whiskers, skim the charted streams,
Of protos, msgs, neatly lined in beams.
From beta burrows up to v1’s clear light,
I stamp my paws—versions mapped just right.
A hop, a note: no code to rearrange—
Just tidy trails of versioned range.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description includes a title, a brief summary, and the purpose checkbox for documentation updates, but it omits several required sections from the repository’s template, including related issues, the full checklist, and notes for reviewers. These missing elements are needed to ensure proper tracking, review guidance, and adherence to contribution standards.	Please update the description to include the “Related Issues” section with any issue links, the complete “✅ Checklist” as specified in the template, and a “📎 Notes for Reviewers” section to guide the review process.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title “docs: add proto versions table docs” directly reflects the core change of adding documentation for protobuf version tables and is concise enough for a teammate to understand the primary purpose of the PR. It accurately highlights the main documentation update without extraneous details or off-topic wording.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch features/protobuf-docs

---

🧪 Early access (Sonnet 4.5): enabled

We are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience.

Note:

• Public repositories are always opted into early access features.
• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

docs/proto-versions.md (3)

1-1: Update title to reflect both Msg Types and Proto Types.

The title only mentions "Msg Types" but the document covers both "Node Modules - Msg Types" and "Provider Modules - Proto Types". Consider updating to something like "Protobuf Types by Module and Version" for accuracy.

-# Protobuf Msg Types by Module and Version
+# Protobuf Types by Module and Version

---

36-36: Remove trailing whitespace for consistency.

Line 36 has trailing whitespace after the final pipe character, which is inconsistent with line 8 in the Node Modules table.

-|:-------|:-----------|:--:|:-------:| 
+|:-------|:-----------|:--:|:-------:|

---

75-75: Consider adding a trailing newline at the end of file.

The file appears to end without a trailing newline character after the last content line (74). While not critical, adding a trailing newline is a common convention that many style guides and tools expect, and helps avoid "No newline at end of file" warnings from Git.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a0da1a3 and 2045597.

📒 Files selected for processing (1)

• docs/proto-versions.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: coverage
• GitHub Check: test
• GitHub Check: go

🔇 Additional comments (2)

docs/proto-versions.md (2)

5-32: Node Modules table looks well-structured.

The table is clearly formatted and provides good visibility into which message types are supported across different versions. The version evolution pattern (e.g., deployment messages in v1beta3/v1beta4, market messages in v1beta4/v1beta5) appears intentional and logical.

---

37-74: Provider Modules table is comprehensive and well-organized.

The table clearly documents the proto types across modules with good organization. The grouping by module (inventory, manifest, provider) and consistent use of version markers makes it easy to understand version support.

[cloud-j-luna]

Overall the modules are correct but I find it confusing to have them together as at a first glance I check that for example MsgSignProviderAttributes is not in v1beta4 and v1beta5, but that is due to the fact that those versions don't even exist in that module, so I recommend we make a table per module only with the available versions in that module. It's way easier to digest and map.

[baktun14]

Overall the modules are correct but I find it confusing to have them together as at a first glance I check that for example MsgSignProviderAttributes is not in v1beta4 and v1beta5, but that is due to the fact that those versions don't even exist in that module, so I recommend we make a table per module only with the available versions in that module. It's way easier to digest and map.

Sure, could you update it with your suggestions please?