Update any-sync to v0.12.14

[requilence]

Summary

• Update github.com/anyproto/any-sync v0.11.20 → v0.12.14
• Bump go directive to 1.26.4
• go mod tidy (go.mod + go.sum only; no code changes; go build ./... passes)

Context

Baselined on main. Previous main-line release: v0.11.1.
Planned release after merge: v0.11.2 (patch bump on the last main-line release).

[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/​anyproto/​any-sync@​v0.11.20 ⏵ v0.12.14	+1
	golang.org/​x/​net@​v0.52.0 ⏵ v0.56.0		+2
	storj.io/​drpc@​v0.0.34 ⏵ v1.0.0	+1
	golang.org/​x/​exp@​v0.0.0-20260212183809-81e46e3db34a ⏵ v0.0.0-20260603202125-055de637280b	+1
	go.uber.org/​zap@​v1.27.1 ⏵ v1.28.0	+1
	github.com/​anyproto/​any-store@​v0.4.6 ⏵ v0.4.7	+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		Obfuscated code: golang github.com/libp2p/go-libp2p is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → golang/github.com/anyproto/any-sync@v0.12.14 → golang/github.com/libp2p/go-libp2p@v0.48.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/libp2p/go-libp2p@v0.48.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.
Warn		Obfuscated code: golang golang.org/x/tools is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → golang/golang.org/x/exp@v0.0.0-20260603202125-055de637280b → golang/golang.org/x/net@v0.56.0 → golang/github.com/anyproto/any-store@v0.4.7 → golang/github.com/anyproto/any-sync@v0.12.14 → golang/go.uber.org/mock@v0.6.0 → golang/golang.org/x/tools@v0.47.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/tools@v0.47.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

[github-actions]

New Coverage	50.9% of statements
Patch Coverage	0.0% of changed statements (0/0)

---

^{Coverage provided by https://github.com/seriousben/go-patch-cover-action}