-
Notifications
You must be signed in to change notification settings - Fork 34
[chore] release version for chain v1.20.1 #419
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
Changes from all commits
7a4cb48
ae90813
95cc7d9
a66083a
72333c8
c08388a
c7e3dd7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -16,11 +16,11 @@ inputs: | |
| - git_repo: https://github.com/InjectiveLabs/wasmd | ||
| tag: v0.53.3-inj.3 | ||
| - git_repo: https://github.com/InjectiveLabs/cometbft | ||
| tag: v1.0.1-inj.v1.19.0-rollback | ||
| 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 | ||
|
Comment on lines
+19
to
+23
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🗄️ 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:
💡 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:
🏁 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 🤖 Prompt for AI Agents |
||
| subdir: proto | ||
| # - git_repo: https://github.com/InjectiveLabs/injective-core | ||
| # branch: c-655/add_chainlink_data_streams_oracle | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: InjectiveLabs/sdk-python
Length of output: 282
🏁 Script executed:
Repository: 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:
Fix the indexer clone target
git clone https://github.com/InjectiveLabs/injective-indexer.git -b v1.20.49 --depth 1 --single-branchpoints at a repository that doesn’t resolve, soclone-all/copy-protowill fail. Update it to a reachable upstream/ref.🤖 Prompt for AI Agents