Deprecation: Go Module Proxy (Experimental)

Deprecation Summary

The Go module proxy feature in the GitLab Package Registry is deprecated and will be removed in a future milestone. This feature never progressed beyond the experimental phase and lacks the completeness and reliability required for production use. It will be replaced by a planned Go virtual registry, which will provide a more robust, fully integrated experience consistent with GitLab's Unified Artifact Management (UAM) strategy.

Users currently relying on the experimental Go module proxy should plan to migrate to the Go virtual registry once it becomes available.

Documentation on feature being deprecated

Migration guidelines

Migration guidelines will be published alongside the Go virtual registry GA. Users currently using the experimental Go module proxy should transition to the Go virtual registry once available.

• Migration documentation: TBD — will be published alongside Go virtual registry GA

Background

After adding and correcting instrumentation for the Go module proxy, we analyzed usage data and observed 0 Go module pulls across all of GitLab.com in May 2026. This confirms the feature has effectively zero adoption, and we can safely deprecate and remove it with no customer impact.

The feature was experimental, never reached GA, and is being superseded by the Go virtual registry as part of the UAM strategy.

Breaking Change?

Does this deprecation contain a breaking change? No

This is a deprecation and removal of an experimental feature with confirmed zero usage. No customers are impacted.

Affected Customers

Who is affected by this deprecation: GitLab.com users, Self-managed users, or Dedicated users? (choose all that apply)

• GitLab.com
• Self-managed
• Dedicated

What pricing tiers are impacted?

• GitLab Free
• GitLab Premium
• GitLab Ultimate

Deprecation Milestone

This deprecation is being announced in milestone: 19.1

Planned Removal Milestone

The feature / functionality will be removed in milestone: 20.0

Rollout Plan

• DRI Engineers: @trizzi

• DRI Engineering Manager: TBD

• Describe rollout plans on GitLab.com

  • Determine how to migrate users still using the existing functionality (N/A — zero usage confirmed)

Communication Plan

• DRI Product Manager: TBD

Internal Communication Plan

• Support Preparedness issue created
• Guidance for Engineering, Product, Security, Customer Success, and Sales created

External Communication Plan

• Customer announcement plan
  • A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page.
  • Deprecation notice MR: !225793 (merged)
  • Documentation has been updated to mark the feature as deprecated.
• On the major milestone:
  • The deprecated item has been removed.
  • If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.

Links

• Replacement: Go virtual registry epic — #592136
• UAM strategy blueprint: gitlab-org#21052
• Deprecation notice MR: !225793 (merged)