GO-sdk version bump

[ansh-meesho]

🔁 Pull Request Template – BharatMLStack

Please fill out the following sections to help us review your changes efficiently.

Context:

Give a brief overview of the motivation behind this change. Include any relevant discussion links (Slack, documents, tickets, etc.) that help reviewers understand the background and the issue being addressed.

Describe your changes:

Mention the changes made in the codebase.

Testing:

Please describe how you tested the code. If manual tests were performed - please explain how. If automatic tests were added or existing ones cover the change - please explain how did you run them.

Monitoring:

Explain how this change will be tracked after deployment. Indicate whether current dashboards, alerts, and logs are enough, or if additional instrumentation is required.

Rollback plan

Explain rollback plan in case of issues.

Checklist before requesting a review

• I have reviewed my own changes?
• Relevant or critical functionality is covered by tests?
• Monitoring needs have been evaluated?
• Any necessary documentation updates have been considered?

📂 Modules Affected

• horizon (Real-time systems / networking)
• online-feature-store (Feature serving infra)
• trufflebox-ui (Admin panel / UI)
• infra (Docker, CI/CD, GCP/AWS setup)
• docs (Documentation updates)
• Other: ___________

---

✅ Type of Change

• Feature addition
• Bug fix
• Infra / build system change
• Performance improvement
• Refactor
• Documentation
• Other: ___________

---

📊 Benchmark / Metrics (if applicable)

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)

• develop

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[semgrep-sast-meesho]

Semgrep found 23 generic_uri_string findings:

• docs/online-feature-store/v1.0.0/index.html
  • L6 - Triage
• docs/numerix/v1.0.0/release-notes/index.html
  • L6 - Triage
• docs/numerix/v1.0.0/index.html
  • L6 - Triage
• docs/numerix/v1.0.0/functionalities/index.html
  • L6 - Triage
• docs/numerix/v1.0.0/benchmarks/index.html
  • L6 - Triage
• docs/numerix/v1.0.0/architecture/index.html
  • L6 - Triage
• docs/inferflow/v1.0.0/release-notes/index.html
  • L6 - Triage
• docs/inferflow/v1.0.0/index.html
  • L6 - Triage
• docs/inferflow/v1.0.0/functionalities/index.html
  • L6 - Triage
• docs/inferflow/v1.0.0/configuration/index.html
  • L6 - Triage
• docs/inferflow/v1.0.0/architecture/index.html
  • L6 - Triage
• docs/category/v100/index.html
  • L6 - Triage
• docs/category/numerix/index.html
  • L6 - Triage
• docs/category/inferflow/index.html
  • L6 - Triage
• docs/blog/post-two/index.html
  • L6 - Triage
• docs/blog/post-three/index.html
  • L6 - Triage
• docs/blog/post-one/index.html
  • L6 - Triage
• docs/blog/post-five/index.html
  • L6 - Triage
• docs/blog/index.html
  • L6 - Triage
• docs/assets/js/7518.9525ffbe.js
  • L1 - Triage
  • L1 - Triage
• docs/assets/js/01a85c17.9618aedf.js
  • L1 - Triage
  • L1 - Triage

Hardcoded sensitive data leaked

Semgrep has detected a leak of sensitive data in this code. This secret data could be used by internal or external malicious actors. We highly recommend you change, reset, or rotate the sensitive data.

A secret is hard-coded in the application. Secrets stored in source code, such as credentials, identifiers, and other types of sensitive data, can be leaked and used by internal or external malicious actors. It is recommended to rotate the secret and retrieve them from a secure secret vault or Hardware Security Module (HSM), alternatively environment variables can be used if allowed by your company policy.