Some modules appear to be not up-to-date

[schu (Michael Schubert)]

Hi. My caddy version is v2.2.0 h1:sMUFqTbVIRlmA8NkFnNt9l7s0e+0gw+7GPIrhty905A= with two modules added:

• GitHub - greenpau/caddy-authorize: Authorization Plugin for Caddy v2 (JWT/PASETO) (latest release is v1.1.2)
• GitHub - greenpau/caddy-auth-portal: Authentication Plugin for Caddy v2 implementing Form-Based, Basic, Local, LDAP, OpenID Connect, OAuth 2.0 (Github, Google, Facebook, Okta, etc.), SAML Authentication. MFA with App Authenticators and Yubico. (latest release is v1.2.1)

I expected to get a binary which includes the latest releases of the modules, but both modules are not up-to-date:

$ ./caddy list-modules --versions | grep auth
...
http.authentication.providers.jwt v1.0.17
http.handlers.auth_portal v1.1.7
...

Is this expected? What is the policy around modules with regards to updates?

The used download link was: https://caddyserver.com/api/download?os=linux&arch=amd64&p=github.com%2Fgreenpau%2Fcaddy-auth-jwt&p=github.com%2Fgreenpau%2Fcaddy-auth-portal&idempotency=89687534029280

[francislavoie]

You can grab it with this link:

https://caddyserver.com/api/download?os=linux&arch=amd64&p=github.com%2Fgreenpau%2Fcaddy-auth-jwt%40v1.1.2&p=github.com%2Fgreenpau%2Fcaddy-auth-portal%40v1.2.1&idempotency=12001203781447

Basically, you can fill in the version in the text box next to each plugin in the table on the download page. It adds @v1.1.2 to the end of the plugin reference.

But I think @greenpau may need to tell the Caddy site to use the latest tag of his plugins… or there might be a bug that @matt needs to look into.

[schu (Michael Schubert)]

Basically, you can fill in the version in the text box next to each plugin in the table on the download page. It adds @v1.1.2 to the end of the plugin reference.

Thanks, didn’t realize that it is an input field and not just a label, that works as a workaround.

[matt (Matt Holt)]

I bet I know what is happening. The build server keeps a cache of each build to reduce load and wait times for common builds.

However I was not able to figure out how to make it version-aware (unless the user specifies a version). It’s basically a glorified wrapper over go build, which just uses the the latest version of each module. But I don’t know a good way to know yet whether any of the direct dependencies have any updates from the prior build that was cached.