Moving go modules to v1+

[princjef]

Feature Request

Is there any plan as part of #14387 to move the inner packages to v1+ versions? We make use of multiple packages in this repo both directly and indirectly that have had multiple breaking releases on their v0.x releases. Any time we have to update one of them it creates immense pain because we have to try to find or force the various dependencies in our system to use the exact same major version of the underlying packages. This is difficult enough to test and verify when we control the dependencies but even more painful when they are subdependencies of other packages we use.

The semantic path versioning of major versions of go modules is built specifically to make this a non-issue by allowing multiple major versions to be used in the same project. However, that benefit only applies once a module has moved past v0.x versioning, which isn't the case for anything that we currently use within this repo. Is there any plan/roadmap for doing this? It would be a huge operational/maintenance benefit going forward.

[jhendrixMSFT]

The modules under the /sdk directory will indeed go to v1.0.0 and follow semver rules once they're out of beta status. I can't comment on when this will happen and will defer to others.

[jhendrixMSFT]

Our modules have hit v1.0.0 and will follow SemVer rules going forward.

[ghost]

Hi @princjef. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[ghost]

Hi @princjef. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[princjef]

Thanks!