[chore] release version for chain v1.20.1#419
Conversation
📝 WalkthroughWalkthroughBumps the SDK to v1.16.0, updates build dependencies ( Changesv1.16.0 Release
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 `@buf.gen.yaml`:
- Around line 19-23: Update the Injective Core dependency entry in buf.gen.yaml
so generation uses the current live upstream instead of the broken
InjectiveLabs/injective-core repository URL. Keep the existing dependency
structure, but replace the git_repo value for the Injective Core input with the
correct active repository reference and verify the tag remains compatible with
the other buf.gen.yaml inputs.
In `@Makefile`:
- Line 29: The clone target in the Makefile is pointing to an unreachable
Injective indexer repository/ref, which breaks clone-all and copy-proto. Update
the git clone command to use a reachable upstream repository and valid
branch/tag, keeping the existing behavior of cloning injective-indexer for the
downstream targets.
🪄 Autofix (Beta)
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: CHILL
Plan: Pro
Run ID: f7932995-bde2-4ed4-81ae-c18f8f4907ba
📒 Files selected for processing (13)
CHANGELOG.mdMakefilebuf.gen.yamlpyinjective/proto/exchange/injective_chart_rpc_pb2.pypyinjective/proto/exchange/injective_exchange_rpc_pb2.pypyinjective/proto/exchange/injective_exchange_rpc_pb2_grpc.pypyinjective/proto/exchange/injective_rfq_gw_rpc_pb2.pypyinjective/proto/exchange/injective_rfq_rpc_pb2.pypyinjective/proto/exchange/injective_tc_derivatives_rpc_pb2.pypyinjective/proto/exchange/injective_tc_derivatives_rpc_pb2_grpc.pypyinjective/proto/injective/peggy/v1/msgs_pb2.pypyinjective/proto/injective/peggy/v1/rate_limit_pb2.pypyproject.toml
| tag: v1.0.1-inj.9 | ||
| - git_repo: https://github.com/InjectiveLabs/cosmos-sdk | ||
| tag: v0.50.14-inj.10 | ||
| tag: v0.50.14-inj.11 | ||
| - git_repo: https://github.com/InjectiveLabs/injective-core | ||
| tag: v1.20.0 | ||
| tag: v1.20.1 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
for repo_tag in \
"https://github.com/InjectiveLabs/cometbft.git v1.0.1-inj.9" \
"https://github.com/InjectiveLabs/cosmos-sdk.git v0.50.14-inj.11" \
"https://github.com/InjectiveLabs/injective-core.git v1.20.1"
do
repo="${repo_tag% *}"
tag="${repo_tag#* }"
git ls-remote --tags "$repo" "$tag"
doneRepository: InjectiveLabs/sdk-python
Length of output: 1155
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== buf.gen.yaml excerpt =="
nl -ba buf.gen.yaml | sed -n '1,40p'
echo
echo "== git ls-remote checks without .git suffix =="
for repo_tag in \
"https://github.com/InjectiveLabs/cometbft v1.0.1-inj.9" \
"https://github.com/InjectiveLabs/cosmos-sdk v0.50.14-inj.11" \
"https://github.com/InjectiveLabs/injective-core v1.20.1"
do
repo="${repo_tag% *}"
tag="${repo_tag#* }"
echo "-- $repo $tag"
git ls-remote --tags "$repo" "$tag" || true
done
echo
echo "== ls-remote full tag listing for injective-core URL variants =="
for repo in \
"https://github.com/InjectiveLabs/injective-core" \
"https://github.com/InjectiveLabs/injective-core.git"
do
echo "-- $repo"
git ls-remote --tags "$repo" 2>&1 | sed -n '1,20p' || true
doneRepository: InjectiveLabs/sdk-python
Length of output: 229
🌐 Web query:
InjectiveLabs injective-core GitHub repository v1.20.1 tag
💡 Result:
The Injective protocol v1.20.1 release is associated with Injective Mainnet Upgrade Proposal 665 [1]. While the v1.20.0 release is officially hosted in the InjectiveFoundation/injective-core repository [2][3], technical documentation and governance records identify v1.20.1 as a targeted point release aimed at introducing improvements to the Injective protocol [1]. As of June 29, 2026, development activities related to v1.20.1 have been observed across the ecosystem, including repository-specific preparations [4]. Users and validators are advised to monitor the official InjectiveFoundation/injective-core GitHub repository releases page for the official tag, binary artifacts, and upgrade instructions [2][5]. The legacy InjectiveLabs/injective-chain-releases repository is deprecated and no longer maintained; all current source code and release management have transitioned to the InjectiveFoundation/injective-core repository [5].
Citations:
- 1: https://polkachu.com/gov_proposals/7330
- 2: https://github.com/InjectiveFoundation/injective-core/releases
- 3: https://newreleases.io/project/github/InjectiveFoundation/injective-core/release/v1.20.0-1780128924
- 4: chore: prep for v1.20.1 sdk-go#367
- 5: https://github.com/InjectiveLabs/injective-chain-releases
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== buf.gen.yaml relevant lines =="
sed -n '15,28p' buf.gen.yaml
echo
echo "== remote refs for claimed injective-core location =="
git ls-remote --tags https://github.com/InjectiveLabs/injective-core v1.20.1 || true
echo
echo "== remote refs for current official repository =="
git ls-remote --tags https://github.com/InjectiveFoundation/injective-core v1.20.1 || trueRepository: InjectiveLabs/sdk-python
Length of output: 926
Fix buf.gen.yaml:19-23 to use the current Injective Core upstream — https://github.com/InjectiveLabs/injective-core no longer resolves, so this input will break generation until it points at the live repository.
🤖 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 `@buf.gen.yaml` around lines 19 - 23, Update the Injective Core dependency
entry in buf.gen.yaml so generation uses the current live upstream instead of
the broken InjectiveLabs/injective-core repository URL. Keep the existing
dependency structure, but replace the git_repo value for the Injective Core
input with the correct active repository reference and verify the tag remains
compatible with the other buf.gen.yaml inputs.
|
|
||
| clone-injective-indexer: | ||
| git clone https://github.com/InjectiveLabs/injective-indexer.git -b v1.20.2 --depth 1 --single-branch | ||
| git clone https://github.com/InjectiveLabs/injective-indexer.git -b v1.20.49 --depth 1 --single-branch |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
repo=https://github.com/InjectiveLabs/injective-indexer.git
git ls-remote --tags "$repo" v1.20.49Repository: InjectiveLabs/sdk-python
Length of output: 282
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Show the relevant Makefile section with line numbers.
sed -n '1,80p' Makefile | cat -nRepository: InjectiveLabs/sdk-python
Length of output: 1701
🌐 Web query:
InjectiveLabs injective-indexer v1.20.49 api/gen/grpc
💡 Result:
The injective-indexer repository maintained by Injective Labs serves as the primary source for the Injective Indexer API, which provides gRPC-based microservices for querying indexed chain data [1][2]. The path api/gen/grpc within the Injective Indexer repository contains the generated Protocol Buffer (protobuf) files for these gRPC services [3]. These files define the service interfaces and message types used for communication between clients and the Indexer service [1][4]. Key points regarding the Injective Indexer and these generated files: 1. Integration and Usage: Injective Labs provides official SDKs (such as @injectivelabs/sdk-ts) that bundle these gRPC clients, allowing developers to interact with the Indexer API without manually managing protobuf files [5][6][7]. The SDKs provide high-level wrappers for querying various modules like accounts, markets, and the explorer [8][9]. 2. Versioning: The Indexer repository follows a versioning scheme that corresponds with Injective chain releases [1]. When using specific versions like v1.20.49, these correspond to the exported gRPC definitions used to generate client code in languages like Go, Python, and TypeScript [1][3]. 3. Repository Role: The injective-proto repository is often used to centralize generated protobufs for the entire Injective ecosystem [1]. It uses automation (e.g., makefile commands like download-indexer-protos) to pull the latest definitions from the injective-indexer repository's api/gen/grpc directory and generate language-specific bindings [1][3]. 4. Documentation: Developers are encouraged to use the official Injective documentation rather than accessing the generated protobuf files directly, as the documentation provides guides for using the SDKs to perform queries and manage real-time data streams [5][2][9]. For developers needing to work with the gRPC layer directly, the injective-indexer repository on GitHub is the source of truth for these definitions [1][4].
Citations:
- 1: https://github.com/InjectiveLabs/injective-proto
- 2: https://docs.injective.network/developers/concepts/indexer-api
- 3: https://github.com/InjectiveLabs/sdk-go/blob/master/Makefile
- 4: https://registry.npmjs.org/%40injectivelabs%2Findexer-proto-ts
- 5: https://docs.injective.network/developers-native/query-indexer/explorer
- 6: https://docs.injective.network/developers-native/query-indexer/account
- 7: https://docs.injective.network/developers-native/query-indexer/derivatives
- 8: https://docs.injective.network/developers-native/query-indexer/index
- 9: https://docs.injective.network/developers-native/query-indexer-stream/index
Fix the indexer clone target
git clone https://github.com/InjectiveLabs/injective-indexer.git -b v1.20.49 --depth 1 --single-branch points at a repository that doesn’t resolve, so clone-all/copy-proto will fail. Update it to a reachable upstream/ref.
🤖 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 `@Makefile` at line 29, The clone target in the Makefile is pointing to an
unreachable Injective indexer repository/ref, which breaks clone-all and
copy-proto. Update the git clone command to use a reachable upstream repository
and valid branch/tag, keeping the existing behavior of cloning injective-indexer
for the downstream targets.
1 participant
Summary by CodeRabbit
New Features
Chores