When you develop modules for use by other developers, you can follow a workflow| go.dev
Documentation| go.dev
When you want to make a module available for other developers, you publish it so| go.dev
When you’re developing modules to publish for others to use, you can help ensure| go.dev
You must update to a major version when changes you’re making in a potential new| go.dev
How to keep your modules compatible with prior minor/patch versions.| go.dev
Managing dependencies| go.dev
A proposal for an additional level of name uniqueness for Postgres extension packaging and distribution, based on URIs.| ❖ Just a Theory
The Go package ecosystem uses distributed publishing to release modules without authentication or uploads. Could we do something similar for Postgres extensions?| ❖ Just a Theory
How to release major version 2 of your module.| go.dev
How to write and publish modules for use as dependencies.| go.dev