Github Release golang submodule

Question

When you do a release on github for a repo you can do "tags" which makes it easier to track in your go.mod

But submodules (or multiple modules) the existing github release method does not work.

The "main" module will be tagged

But the "submodule" can't be referenced via that tag. (Which makes sense bc they should not be required to be lockstep)

My question is how to get Github to tag that submodule with an explicit version?

Note this is for a "private" repo so I can't publish it as a separate package within golang outside of github

prnvbn · Accepted Answer · 2024-01-26 21:07:00Z

2

You can tag versions for each submodule by adding a directory prefix in front of the tag.

So for the following directory structure, you can create this tag submod/subsubmod/v0.0.1

demo/
└── submod
    └── subsubmod
        ├── file.go
        └── go.mod

edited Jan 26, 2024 at 21:07

answered Jan 23, 2024 at 8:01

prnvbn

1,0913 gold badges12 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

dtracers Over a year ago

This is really helpful! So you make "submod/subsubmod v0.0.1" the "tag" name in the github release gui? (just so I am 100% clear)

prnvbn Over a year ago

Yes. You can even do git tag "submod/subsubmod v0.0.1" and then git push --tags from the terminal. This will tag the repo but not create a release on your GitHub repository. (Tagging is enough for Go though)

dtracers Over a year ago

it looks like git tag "submod/subsubmod v0.0.1" is not actually valid but git tag "submod/subsubmod/v0.0.1" is

prnvbn Over a year ago

ahh yes, that's my bad

Collectives™ on Stack Overflow

Github Release golang submodule

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related