Prevent main Caddy module from upgrading from adding a plugin #93
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #54
For example:
The key being that the
go get
to add thecloudflare
plugin also specifies the Caddy module, which puts a constraint that the Caddy module should not upgrade past that version from pulling in the plugin.This means that some builds that would have previously worked might fail now, but I think this is least-surprise, because it's weird that if you specify a version of Caddy that it would get upgraded higher because of a plugin.
This can be solved by specifying a version of the plugin that does build with the older version of Caddy specified: