imp: add version to tm headers in ibctesting (release/v6.3.x)

[damiannolan]

Description

Take changes forward from: #6099
This PR targets release/v6.3.x.

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against the correct branch (see CONTRIBUTING.md).
• Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/).
• Added relevant godoc comments.
• Provide a conventional commit message to follow the repository standards.
• Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
• Re-reviewed Files changed in the GitHub PR explorer.
• Review SonarCloud Report in the comment section below once CI passes.

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[damiannolan]

Noting here that I'm not sure that this is needed given that v6 is an EOL release line. Feel free to close if you think, cc. @crodriguezvega

[damiannolan]

Would we release v6.3.1 with this? Or is it out of scope since v6 is EOL?

Note #6099 is now stale. https://github.com/celestiaorg/celestia-app/blob/main/go.mod#L18

@rootulp @ninabarbakadze do you have plans to go to ibc-go/v7 at some point? I'm assuming that its probably blocking due to sdk forks etc in celestia, and I think I may have been told that you might plan to go directly to v0.50+ (ibc-go/v8) or something along these lines.

[rootulp]

You're spot on that celestia-app is currently blocked on upgrading ibc-go because we maintain a Cosmos SDK fork that is currently on v0.46.x. We don't have firm plans but I think we'll try to bump to Cosmos SDK v0.50+ and upgrade directly to ibc-go/v8 after our next hard-fork.

[damiannolan]

You're spot on that celestia-app is currently blocked on upgrading ibc-go because we maintain a Cosmos SDK fork that is currently on v0.46.x. We don't have firm plans but I think we'll try to bump to Cosmos SDK v0.50+ and upgrade directly to ibc-go/v8 after our next hard-fork.

Hey @rootulp! I wanted to quickly discuss this with the team before merging since v6 is EOL.
Happy to merge this and we'll tag a v6.3.1 for you with this change, however we won't make an official release via GitHub since the release line is EOL. I can let you know when the tag is available!

[rootulp]

Awesome, thanks Damian! A v6.3.1 tag will be super helpful for us :)