Pin near-openapi-client and near-openapi-types to v0.8.0 commit hash

[Copilot]

Git dependencies without a tag/rev/branch resolve to the default branch tip, making builds non-reproducible and susceptible to unexpected breaking changes.

Changes

• Cargo.toml: Pin both near-openapi-client and near-openapi-types to the v0.8.0 release commit hash using rev =

near-openapi-client = { git = "https://github.com/near/near-openapi-client-rs.git", rev = "0b9c46786934edd274a0ae91ab42c13516f50965" }
near-openapi-types  = { git = "https://github.com/near/near-openapi-client-rs.git", rev = "0b9c46786934edd274a0ae91ab42c13516f50965" }

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[r-near]

@copilot I think it's better to pin to a commit hash

[Copilot]

@copilot I think it's better to pin to a commit hash

Done in 4f13efa — both dependencies are now pinned to the v0.8.0 release commit hash (0b9c46786934edd274a0ae91ab42c13516f50965).

[Copilot]

Pull request overview

This PR pins the near-openapi-client and near-openapi-types git dependencies to a specific commit hash (rev = "0b9c46786934edd274a0ae91ab42c13516f50965"), corresponding to the v0.8.0 release. Without a rev, tag, or branch specifier, Cargo resolves git dependencies to the default branch tip, making builds non-reproducible and vulnerable to upstream breaking changes.

Changes:

• Pin both near-openapi-client and near-openapi-types to a fixed commit hash in the workspace Cargo.toml.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.