Skip to content
Just a test site
HTML
Branch: master
Clone or download
Latest commit cb1af6f Aug 14, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
content Adjustments May 6, 2019
layouts Work Jul 22, 2019
themes/in-themesdir/data Add a component below /in-themesdir May 28, 2019
.gitignore Add the _vendor dir May 29, 2019
README.md Add some v2 notes May 28, 2019
config.toml Use Hyde Aug 14, 2019
go.mod Use Hyde Aug 14, 2019
go.sum Use Hyde Aug 14, 2019

README.md

Some notes

Add or update a module

  • TODO(bep) imports

The following will add or update a module:

hugo mod get -u  github.com/bep/my-theme

Update all modules

The following will update all modules to their latest minor or patch version:

hugo mod get -u

Local development

Add a replace directive:

replace github.com/bep/hugotestmods/mypartials => /Users/bep/sites/hugomod/hugotestmods/mypartials

Major versions

The simplest is to stick with v1 and increment minor and patch versions, e.g. v1.0.0, v1.0.1, v1.1.0 and so on.

If you really need to release a new (breaking) major version, you can do this:

Edit your module's go.mod file and add the major version at the end of the path, e.g

module github.com/bep/hugotestmods/myv2/v2

Then tag a new release version, e.g. myv2/v2.0.0.

Note: Hugo will currently only use one version of a given module (the first), so if you have a dependency that is depending on the v1 version of that same module, but you really want to try out v2, then you must insert the v2-path higher up. The command hugo mod graph is useful in debugging these issues.

TODOS:

You can’t perform that action at this time.