Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: rm tools/hubl #23562

Merged
merged 4 commits into from
Jan 30, 2025
Merged

chore: rm tools/hubl #23562

merged 4 commits into from
Jan 30, 2025

Conversation

aljo242
Copy link
Collaborator

@aljo242 aljo242 commented Jan 30, 2025

Description

Functionality similar to hubl will be maintained in ignite, so this is one less thing to maintain


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

Release Notes: Hubl Tool Deprecation

  • Deprecation

    • Removed Hubl tool from the Cosmos SDK project
    • Deleted all Hubl-related files, configurations, and documentation
  • Impact

    • Removed CLI tool for querying Cosmos SDK-based blockchains
    • Discontinued support for Hubl keyring and related functionalities
    • Simplified project structure by eliminating Hubl-specific components
  • Next Steps

    • Migrate to alternative CLI tools or methods for blockchain interactions
    • Review and update any existing workflows dependent on Hubl
    • Refer to updated documentation for current recommended practices

Copy link
Contributor

coderabbitai bot commented Jan 30, 2025

📝 Walkthrough

Walkthrough

This pull request involves the comprehensive removal of the hubl tool from the Cosmos SDK project. The changes span multiple files and directories, systematically eliminating references, documentation, build configurations, and the entire tools/hubl directory. The removal includes deletion of source code, configuration files, build scripts, documentation, and workflow configurations related to the hubl tool. This appears to be a deliberate and thorough deprecation of the tool from the Cosmos SDK ecosystem.

Changes

File/Directory Change Summary
.github/CODEOWNERS Removed ownership entry for /tools/hubl
.github/dependabot.yml Removed gomod package ecosystem entry for /tools/hubl
.github/pr_labeler.yml Deleted "C:Hubl" entry and associated pattern
.github/workflows/build.yml Removed Hubl build step
.github/workflows/test.yml Deleted test-hubl job
CHANGELOG.md Removed entire content related to Hubl
ROADMAP.md Removed Hubl-specific tasks and references
client/v2/README.md Removed Hubl keyring references
docs/build/tooling/README.md Deleted Hubl entry from CLI tools
docs/.gitignore Removed exclusion for docs/tooling/03-hubl.md
go.work.example Removed ./tools/hubl module
tools/hubl/ Completely removed entire directory and all contents

Suggested labels

backport/v0.52.x

Suggested reviewers

  • julienrbrt
  • tac0turtle

Possibly related PRs


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
🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
CHANGELOG.md (1)

54-54: Fix empty link in changelog

There is an empty link []() which should either be removed or populated with proper link text and URL.

- []()
+ <!-- Remove this empty link -->
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

54-54: No empty links
null

(MD042, no-empty-links)

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 97c61cf and 280bcbe.

⛔ Files ignored due to path filters (1)
  • tools/hubl/go.sum is excluded by !**/*.sum
📒 Files selected for processing (32)
  • .github/CODEOWNERS (0 hunks)
  • .github/dependabot.yml (0 hunks)
  • .github/pr_labeler.yml (0 hunks)
  • .github/workflows/build.yml (0 hunks)
  • .github/workflows/test.yml (0 hunks)
  • CHANGELOG.md (1 hunks)
  • ROADMAP.md (2 hunks)
  • UPGRADING.md (0 hunks)
  • client/v2/README.md (1 hunks)
  • docs/.gitignore (0 hunks)
  • docs/build/tooling/README.md (0 hunks)
  • docs/post.sh (0 hunks)
  • docs/pre.sh (0 hunks)
  • go.work.example (0 hunks)
  • scripts/build/build.mk (0 hunks)
  • tools/hubl/.gitignore (0 hunks)
  • tools/hubl/CHANGELOG.md (0 hunks)
  • tools/hubl/Makefile (0 hunks)
  • tools/hubl/README.md (0 hunks)
  • tools/hubl/cmd/hubl/main.go (0 hunks)
  • tools/hubl/go.mod (0 hunks)
  • tools/hubl/internal/compat.go (0 hunks)
  • tools/hubl/internal/config/config.go (0 hunks)
  • tools/hubl/internal/flags/flags.go (0 hunks)
  • tools/hubl/internal/keyring.go (0 hunks)
  • tools/hubl/internal/load.go (0 hunks)
  • tools/hubl/internal/registry.go (0 hunks)
  • tools/hubl/internal/remote.go (0 hunks)
  • tools/hubl/internal/root.go (0 hunks)
  • tools/hubl/internal/util.go (0 hunks)
  • tools/hubl/internal/version.go (0 hunks)
  • tools/hubl/sonar-project.properties (0 hunks)
💤 Files with no reviewable changes (29)
  • go.work.example
  • tools/hubl/.gitignore
  • docs/pre.sh
  • docs/post.sh
  • scripts/build/build.mk
  • docs/.gitignore
  • tools/hubl/go.mod
  • tools/hubl/README.md
  • tools/hubl/cmd/hubl/main.go
  • tools/hubl/Makefile
  • docs/build/tooling/README.md
  • tools/hubl/internal/root.go
  • .github/pr_labeler.yml
  • tools/hubl/CHANGELOG.md
  • tools/hubl/sonar-project.properties
  • tools/hubl/internal/keyring.go
  • .github/dependabot.yml
  • .github/CODEOWNERS
  • tools/hubl/internal/config/config.go
  • tools/hubl/internal/flags/flags.go
  • tools/hubl/internal/version.go
  • .github/workflows/build.yml
  • tools/hubl/internal/util.go
  • tools/hubl/internal/compat.go
  • tools/hubl/internal/registry.go
  • tools/hubl/internal/remote.go
  • UPGRADING.md
  • tools/hubl/internal/load.go
  • .github/workflows/test.yml
✅ Files skipped from review due to trivial changes (1)
  • client/v2/README.md
🧰 Additional context used
📓 Path-based instructions (2)
ROADMAP.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

🪛 markdownlint-cli2 (0.17.2)
CHANGELOG.md

54-54: No empty links
null

(MD042, no-empty-links)

⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: repo-analysis
  • GitHub Check: build (arm64)
  • GitHub Check: Analyze
  • GitHub Check: build (amd64)
  • GitHub Check: dependency-review
  • GitHub Check: golangci-lint
  • GitHub Check: markdown-link-check
  • GitHub Check: Summary
🔇 Additional comments (3)
ROADMAP.md (2)

34-34: LGTM! Task description updated correctly.

The simplified task description aligns with the PR objective of removing hubl references.


124-124: LGTM! AutoCLI section updated correctly.

The section has been appropriately updated to focus solely on AutoCLI, which aligns with the PR objective of removing hubl references.

CHANGELOG.md (1)

Line range hint 1-2000: LGTM! Well-structured changelog following best practices

The changelog is well organized with:

  • Clear version sections with dates
  • Categorized changes (Features, Improvements, Bug Fixes etc.)
  • Detailed descriptions with PR/Issue references
  • Breaking changes clearly highlighted
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

54-54: No empty links
null

(MD042, no-empty-links)

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

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

🫡

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
CHANGELOG.md (2)

Line range hint 1-1: Add title to the CHANGELOG file

The CHANGELOG file should start with a # CHANGELOG title for better documentation structure.

+ # CHANGELOG

52-54: Add version release date in consistent format

The Unreleased section should follow the same date format as other releases (YYYY-MM-DD).

- ## [Unreleased]
+ ## [Unreleased] - TBD
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 280bcbe and 9f15f0c.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: Analyze
  • GitHub Check: build (arm64)
  • GitHub Check: build (amd64)
  • GitHub Check: dependency-review
  • GitHub Check: golangci-lint
  • GitHub Check: markdown-link-check
  • GitHub Check: Summary
🔇 Additional comments (2)
CHANGELOG.md (2)

Line range hint 1-15: LGTM: Well-structured changelog guidelines

The guiding principles section clearly explains the purpose and format of the changelog, which is essential for maintainers.


Line range hint 1-1000: Verify all referenced PR links

The changelog contains many PR references. We should verify that all these links are valid and accessible.

✅ Verification successful

All PR references in the changelog appear to be valid and properly formatted

The verification process checked a sample of PR links (#18991, #19043, #18956, #18707, #18772) and confirmed they all exist in the repository. The changelog follows a consistent format for PR references, and all tested links were accessible. While we tested a sample due to API rate limits, the consistent format and successful sample verification suggest all PR references are properly maintained.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Extract PR numbers and verify they exist in the repository
prNumbers=$(grep -o '#[0-9]\{4,5\}' CHANGELOG.md | tr -d '#')
for pr in $prNumbers; do
  gh pr view "$pr" --repo cosmos/cosmos-sdk >/dev/null 2>&1
  if [ $? -ne 0 ]; then
    echo "PR #$pr not found"
  fi
done

Length of output: 111


Script:

#!/bin/bash
# Clone the repository and verify PR links
git clone https://github.com/cosmos/cosmos-sdk.git
cd cosmos-sdk
git checkout v0.50.3

# Extract PR numbers and verify they exist
prNumbers=$(grep -o '#[0-9]\{4,5\}' CHANGELOG.md | tr -d '#')
echo "Found PR numbers:"
echo "$prNumbers"

# Test a few PRs to verify they exist
# We'll check the first 5 PRs to avoid hitting API rate limits
count=0
for pr in $prNumbers; do
  if [ $count -ge 5 ]; then
    break
  fi
  echo "Checking PR #$pr..."
  gh pr view "$pr" --repo cosmos/cosmos-sdk --json number,state >/dev/null 2>&1
  if [ $? -ne 0 ]; then
    echo "PR #$pr not found or inaccessible"
  else 
    echo "PR #$pr exists"
  fi
  count=$((count + 1))
done

Length of output: 7316

@aljo242 aljo242 added this pull request to the merge queue Jan 30, 2025
Merged via the queue into main with commit b87acd2 Jan 30, 2025
71 of 73 checks passed
@aljo242 aljo242 deleted the chore/rm-hubl branch January 30, 2025 17:58
alpe added a commit that referenced this pull request Jan 31, 2025
* main:
  build(deps): Bump actions/create-github-app-token from 1.11.1 to 1.11.2 (#23567)
  docs(keyring): add keyctl docs (#23563)
  chore: rm `tools/hubl` (#23562)
  build(deps): Bump github.com/spf13/pflag from 1.0.5 to 1.0.6 (#23555)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants