I have the same issue. I would like to | Dagger | Page 1

Since Daggerverse is just an index of modules in git that it knows about, Daggerverse will only know about certain versions of the module because of manual publish and publish-on-use behavior. Essentially, if it's not published to Daggerverse, then Daggerverse doesn't know about it today. Typically the git server (github, gitlab, etc) will have the latest version (except for local modules/changes not pushed to git yet or private git modules).

Do you mean something special by "the latest version of a module on Daggerverse" like the latest tagged release published on Daggerverse or just the latest module version that is indexed by Daggerverse (even if it is untagged and not displayed in the UI because tagged releases shadow them) ?

For example, consider these two. Imagine v0.1.7 is the latest tagged release (it's actually v0.1.10 at the moment). In that case, there is a newer untagged (non-release) version indexed by Daggerverse.
There also could be other more recent ("latest") versions that are still only in git and have not been indexed by Daggerverse.
Which module version would you want as "latest"?

{
    "path": "github.com/marcosnils/daggerverse/k3s",
    "version": "833ec36632b2457862f6e3bf1f7107ad65e3e515",
    "git_url": "github.com/marcosnils/daggerverse",
    "git_commit": "833ec36632b2457862f6e3bf1f7107ad65e3e515",
    "subpath": "k3s",
    "browse_url": "https://github.com/marcosnils/daggerverse/tree/833ec36632b2457862f6e3bf1f7107ad65e3e515/k3s",
    "indexed_at": "2025-03-27T16:17:13.625131Z",
    "release": "k3s/v0.1.7"
  }

  {
    "path": "github.com/marcosnils/daggerverse/k3s",
    "version": "ec58b00e9ab7b422f60210249d4c8ce4ca94ec90",
    "git_url": "github.com/marcosnils/daggerverse",
    "git_commit": "ec58b00e9ab7b422f60210249d4c8ce4ca94ec90",
    "subpath": "k3s",
    "browse_url": "https://github.com/marcosnils/daggerverse/tree/ec58b00e9ab7b422f60210249d4c8ce4ca94ec90/k3s",
    "indexed_at": "2025-04-15T16:10:46.489384Z",
    "release": ""
  }

#I have the same issue. I would like to