Independent versioning across different packages

[ian-shim]

Right now, the entire repository is versioned together.
If there is a desired patch for one package, but that version has an undesired update on another package, I cannot make an upgrade.
Ideally, each package is versioned separately, so that developers can upgrade specific packages.

[afkbyte]

Hey! Would you want a go.work at root or something to generate a go.work including each of the modules?

This discussion for reference: golang/go#53502

[samlaf]

Good find @afkbyte . Didn't read through the whole issue, still confused as to what exactly is happening with the go.work file. The last message (golang/go#53502 (comment)) is saying it's needed for vscode to be able to identify the different go.mod files in the repo.

Not sure what the exact tradeoffs he's mentioning are, aka what's wrong with checking the go.work file into the repo. Are you aware of this @ian-shim ?