Release v20260413

[chowbao]

Summary

• Set contract_code_hash to nil for all Soroban operation types (invoke contract, create contract, create contract v2, upload wasm, extend footprint TTL, restore footprint) — removes unreliable hash extraction from transaction envelope footprints
• Upgrade Go module dependencies
• Add Dependabot configuration for automated weekly dependency updates (gomod, GitHub Actions, Docker)

Test plan

• Unit tests updated to expect nil for contract_code_hash
• Verify go test ./internal/transform passes
• Verify integration tests pass

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	github.com/​stretchr/​testify@​v1.10.0 ⏵ v1.11.1	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		High CVE: OpenTelemetry-Go: multi-value baggage header extraction causes excessive allocations (remote dos amplification) in golang `go.opentelemetry.io/otel` CVE: GHSA-mh2q-q3fh-2475 OpenTelemetry-Go: multi-value baggage header extraction causes excessive allocations (remote dos amplification) (HIGH) Affected versions: >= 1.36.0 < 1.41.0; >= 1.36.0 < 1.41.0 Patched version: 1.41.0 From: ? → golang/github.com/stellar/go-stellar-sdk@v0.0.0-20251211085638-ba09a6a91775 → golang/github.com/spf13/viper@v1.17.0 → golang/github.com/xitongsys/parquet-go-source@v0.0.0-20240122235623-d6294584ab18 → golang/cloud.google.com/go/storage@v1.42.0 → golang/go.opentelemetry.io/otel@v1.39.0 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/go.opentelemetry.io/otel@v1.39.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[Copilot]

Pull request overview

Release PR that removes unreliable Soroban contract_code_hash extraction (now emitted as nil) and refreshes dependency management.

Changes:

• Set contract_code_hash to nil for Soroban-related operation types and remove the footprint-based hash extraction helpers.
• Update Go module dependencies (go.mod / go.sum).
• Add Dependabot configuration for weekly updates across Go modules, GitHub Actions, and Docker.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
internal/transform/operation.go	Sets contract_code_hash to nil for Soroban ops and removes hash-extraction helpers.
internal/transform/operation_test.go	Updates unit test expectations to nil for contract_code_hash.
go.mod	Bumps Go dependencies (direct + indirect).
go.sum	Updates dependency checksums to match module upgrades.
.github/dependabot.yml	Adds Dependabot config for automated weekly dependency updates.

---

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

[Copilot]

The Docker Dependabot update is configured to scan directory "/", but this repo’s Dockerfiles are under "/docker" (e.g., docker/Dockerfile, docker/Dockerfile.test). As-is, Dependabot is likely to miss Dockerfile base-image updates in that folder. Consider changing the docker entry’s directory to "/docker" or adding an additional docker update entry for "/docker" (and keep "/" only if you also want to update docker-compose.yaml at the repo root).