+
Skip to content

Submodules not being released with tags #203

@pete-woods

Description

@pete-woods

Dependabot / renovate have trouble with the sub-modules in this module, seemingly because they are not released / tagged.

When you have submodules, usually it's easiest to follow some rules:

  • Have all submodules follow the same major version.
  • Tag all submodules for release at the same time as the main module:
    • e.g. v2.8.0 for the main module
    • and badgerstore/v2.8.0, boltstore/v2.8.0, bunstore/v2.8.0, etc for the sub modules.

See an example of how the tagging is supposed to be done here: https://github.com/hbjydev/go-submods-example/tags

At the moment, the store submodules all appear to be v1 modues, and also not tagged, so it really confuses any tools that want to automatically update them, as those tools want to pull down the latest v1 SCS, which is v1.4.1, and things go wrong.

I don't know what strategy you prefer to employ here, but would really appreciate something being figured out. Also as I'm using this library I'm willing to help out in any way I can.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载