#Publishing Modules | Dagger
quiet creek
Ahh I think I see a potential issue. Repository name == subdir name in another repository.
Repository: https://github.com/mjb141/sem-rel
(Old module): https://github.com/Mjb141/daggerverse/tree/main/sem-rel
I still haven't figured out if I should be keeping all of these in one repository or not...
lean fern
Actually, it's because Daggerverse is not at v0.14 yet. I'm going to check on that now.
cc @sonic granite @weary lily
quiet creek
Ah makes sense. No issues with modules sharing names then presumably?
Is there any updated guidance on monorepo vs repo-per-module? No actual technical difference between organisation?
lean fern
Ah makes sense. No issues with modules sharing names then presumably?
No issues, namespaced by all the rest of the ref prefix and such.
And...we're updated 🙂
https://daggerverse.dev/mod/github.com/mjb141/sem-rel@b3583bda583de37c780a511fb0c59594665fc3a6
Thanks so much for letting us know!
lean fern
Is there any updated guidance on monorepo vs repo-per-module? No actual technica...
Both are still supported, yes.
quiet creek
Following up on this, and perhaps one for expanding this (https://docs.dagger.io/api/publish#semantic-versioning) page: tags/releases in that repository aren't showing in daggerverse? I recall some discussion previously about how to version in a megarepo of modules (subdir/vx.y.z), is there something else I need to do?
