Skip to content

chore: fix module setup and versioning #741

@davidsneighbour

Description

@davidsneighbour

Go (and thus GoHugo) has a system where semver 0 and 1 are loaded with a "normal" require setup and all version numbers from there require a version number in the require setup.

The current README.md module docs will lead to the latest main commit being applied.

Somehow that needs to be fixed and documented so that proper versions can be installed from the release-branches and adding the line without any note set's the latest official release as module.

Metadata

Metadata

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions