chore: update cid

[HuberTRoy]

Description

• Update Cid.

Summary by CodeRabbit

• Chores
  • Updated network deployment configuration.

[coderabbitai]

Walkthrough

The pull request updates the .env file, specifically changing the VITE_NETWORK_DEPLOYMENT_ID environment variable from one IPFS content hash to another. All other environment variables remain unchanged.

Changes

Cohort / File(s)	Summary
Environment Configuration ​.env	Updated VITE_NETWORK_DEPLOYMENT_ID IPFS hash from QmQqqmwwaBben8ncfHo3DMnDxyWFk5QcEdTmbevzKj7DBd to QmZozXZDYWs2sRGCaSUP1F4x2b3hvDYCyWP53NjFRzkqWg

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hash, a change, a new ID in sight,
The network deployment takes flight!
Through IPFS fields we hop and bound,
With this config tweak, all's sound! 🐰✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal and missing critical template sections including ticket reference, test cases, type of change, and UI changes.	Add ticket number, describe test cases, select applicable change type, and include any UI changes per the repository template.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: update cid' directly relates to the main change—updating the VITE_NETWORK_DEPLOYMENT_ID environment variable (CID).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-cid

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.env (1)

8-8: Consider reordering keys to maintain alphabetical consistency.

While the CID update itself is valid, the static analysis tool (dotenv-linter) flagged that VITE_NETWORK_DEPLOYMENT_ID should appear before VITE_QUERY_REGISTRY_PROJECT for alphabetical ordering consistency.

Consider moving line 8 to appear between lines 1–2 to maintain alphabetical order:

  VITE_IPFS_GATEWAY=https://unauthipfs.subquery.network/ipfs/api/v0
+ VITE_NETWORK_DEPLOYMENT_ID=QmZozXZDYWs2sRGCaSUP1F4x2b3hvDYCyWP53NjFRzkqWg
  VITE_QUERY_REGISTRY_PROJECT=https://api.subquery.network/sq/subquery/subquery-mainnet
  VITE_TOP_100_INDEXERS=https://lb-api.subquery.network/graphql
  VITE_CONSUMER_HOST_ENDPOINT=https://chs.subquery.network
  VITE_FORUM_DOMAIN=https://forum.subquery.network
  VITE_NETWORK=mainnet
  VITE_GQL_PROXY=https://gql-proxy.subquery.network
- VITE_NETWORK_DEPLOYMENT_ID=QmZozXZDYWs2sRGCaSUP1F4x2b3hvDYCyWP53NjFRzkqWg
  VITE_PROXYGATEWAY=https://gateway.subquery.network
  VITE_AI_URL=https://ai-reaction-backend.subquery.network/ai-network/v1/chat/completions
  VITE_AI_REACTION_URL=https://ai-reaction-backend.subquery.network
  VITE_CONSUMER_CAMPAIGN_URL=https://consumer-campaign-api.subquery.network
  VITE_GRAPHQL_AGENT=https://graphql-agent.subquery.network

This will resolve the dotenv-linter warning and improve consistency.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between befd7f2 and ce815fd.

📒 Files selected for processing (1)

• .env (1 hunks)

🧰 Additional context used

🪛 dotenv-linter (4.0.0)

.env

[warning] 8-8: [UnorderedKey] The VITE_NETWORK_DEPLOYMENT_ID key should go before the VITE_QUERY_REGISTRY_PROJECT key

(UnorderedKey)