-
Notifications
You must be signed in to change notification settings - Fork 949
Description
With the project changing home from the Mozilla Foundation to the CNCF, it is necessary to update the Go module path to reflect this change. This proposal suggests renaming the Go module from go.mozilla.org/sops/v3
to github.com/getsops/sops/v3
while maintaining the current major version.
Motivation
- Alignment with new stewardship: As the project transitions from the Mozilla Foundation to being a CNCF Sandbox project, it is important to reflect this change in the module's naming and ownership. Updating the module path to
github.com/getsops/sops/v3
ensures that it accurately represents the current stewardship. - Avoiding a major version bump: By preserving the existing major version, we can minimize the impact on the consumers of the module. A major version change often implies breaking changes and requires (more) significant adjustments from the users. Renaming the module without bumping the major version allows for a smoother transition.
- "Ripping off the bandage": The current (upcoming) changes are already causing disruption and difficulties for users. By renaming the module and addressing related updates simultaneously, we aim to minimize additional pain and provide a clear path forward.
Impact
To end-users (users of the sops
binary), the impact should be minimal and/or non-existent.
SDK users
Transitioning to the new Go module name, github.com/getsops/sops/v3
, involves a few steps for dependents of the module, who want to upgrade from <= v3.7.3
to a newer version (>= v3.8.0
).
- Update Go module dependency: In your project's
go.mod
file, update the path for the modulego.mozilla.org/sops/v3
to the new module pathg.yxqyang.asia/getsops/sops/v3
. - Update import statements: In your project's Go files, update the
import
statements related to the module. Replace occurrences ofimport "go.mozilla.org/sops/v3"
withimport "github.com/getsops/sops/v3"
.
Feedback
We highly value your feedback! If you have any thoughts and concerns around the proposed rename, please share them. Any comments will be carefully considered as we move forward.