Please change version number

[gteigland]

This is related to an issue on our side: https://github.com/gantry/gantry5/issues/3334

We've taken over the maintenance of the Gantry5 plugin from RocketTheme and have released a new version (5.5.22).

Plugin URL: https://github.com/gantry/gantry5/releases/download/5.5.22/grav-pkg_gantry5_v5.5.22.zip
Changelog: https://github.com/gantry/gantry5/blob/5.5.22/CHANGELOG.md
New Maintainer: Tiger12
Version in blueprints.yaml: 5.5.22

However, the Grav plugin site still lists version 5.5.19.

Could you please trigger an update so GPM reflects the latest version?

Please let me know if any additional information is needed.

Thank you!

[rhukster]

Everything comes from the release and blueprints.yaml, The version number specifically comes from the blueprints.yaml and has to match the released version in github.

Gantry is a special case though, and as it's blueprint is not in the root folder, it's being looked for here:

  gantry5:
    git: gantry/gantry5
    blueprints: platforms/grav/gantry5/blueprints.yaml
    branch: master
    zipball_url: https://github.com/gantry/gantry5/releases/download/{{version}}/grav-pkg_gantry5_v{{version}}.zip

Also notice the zipball URL has to have this very specific syntax.

Good luck!

[w00fz]

Resources, including Gantry's plugin, maintain their own versions and changelog updates that Grav then automatically picks up. You only need to open a ticket for the first time submission. Any subsequent updates are automatic and depend on a conformed release.

You don’t need to worry about updating your blueprints.yaml for Grav because Gantry has a template that automatically replaces those @version@ placeholders whenever you release. This is tied to the CICD workflow, and the version is determined by the tag name. Your release looks great, though, there is one issue with the changelog.

Your latest release is 5.5.22, but the latest release from the Grav side is version 5.5.19. So I checked version 5.5.20, and I noticed that the changelog doesn’t follow Grav’s expected format. For instance, the line for the date 5.5.20 includes additional text, which is probably the reason why the release is being skipped by the Grav parser.

• https://github.com/gantry/gantry5/blob/5.5.20/CHANGELOG.md

# 5.5.20
-## 07/23/2025 (Set for release - This list has been marked from prior dev changelog (March 2025)
+## 07/23/2025
1. [Common](#common)
    1. [](#new)
...

For gantry the CHANGELOG is read from the master branch, so if you update it there or do a new release, hopefully this would solve the problem for you.

[pmoreno-rodriguez]

Well, after the latest Gantry update to version 5.5.23, its changelog now appears fixed on the master branch. However, the Official Grav Repository still shows version 5.5.19, and its Download button points to https://getgrav.org/download/plugins/gantry5/5.5.19. You can see https://getgrav.org/downloads/plugins.json I manually installed the latest version of Gantry, and now in the Grav admin panel, clicking the View Changelog button shows the changes since version 5.5.15. It's very strange.

[Xoriander]

The file https://getgrav.org/downloads/plugins.json used by gravs GPM command to index the plugins shows:

"gantry5": {
    "name": "Gantry 5 Framework",
    "version": "5.5.19",
    "description": "Gantry 5 Theme framework",
    "description_html": "<p>Gantry 5 Theme framework</p>",
    "description_plain": "Gantry 5 Theme framework",
    "icon": "gantry",
    "author": {
      "name": "Tiger12",
      "url": "http://tiger12.com",
      "email": "[email protected]"
    },
    "dependencies": [
      "grav",
      "admin"
    ],
    "homepage": "http://gantry.org",
    "keywords": "gantry, gantry5, theme, framework",
    "bugs": "https://github.com/gantry/gantry5/issues",
    "license": "MIT",
    "tag_name": "5.5.23",
    "date": "2025-08-11T06:59:10Z",
    "release_type": "stable",
    "zipball_url": "https://getgrav.org/download/plugins/gantry5/5.5.19",
    "repository": "https://github.com/gantry/gantry5",
    "slug": "gantry5",
    "install_path": "user/plugins/gantry5",
    "changelog": {
      "5.5.15": {
        "date": "09/05/2022",
        "content": ...

Author is correct, tag_name is correct (5.5.23) and change date also (2025-08-11T06:59:10Z). Why does the file in the root folder of Gantry with the name VERSION contains 5.5.20 and not 5.5.23 and why it was changed from @version@ to 5.5.20?

[gteigland]

@rhukster Here is what we found. Let me know if there is something else we need to adjust if this is on our end. Thanks for your help:

After releasing the new version (which includes fixes suggested by the Grav maintainer: https://github.com/getgrav/grav/issues/3937#issuecomment-3148603776), I noticed that on the Grav plugin repository (https://getgrav.org/downloads/plugins ), GPM (Grav Package Manager) was run and the branding name was updated. However, the version and changelog are still showing as 5.5.19.

The suggested changes have been implemented and the new version has been released, but the repository is still displaying the old version.

Please review the attached screenshot.

[rhukster]

As @w00fz mentioned above, your 'master' branch is the source of truth.. However your master branch has a mix of versions:

Changelog has 5.5.23 VERSION file has 5.5.20 platforms/grav/gantry5/blueprints.yamld has 5.5.19

There's a bin/build script that should be updating these versions I think. They need to all be insync and all the correct latest version.

[gteigland]

@rhukster here what we found -perhaps you could provide some more insight into this:

In the develop branch, the version number and release date are defined as variables (@version@ and @versiondate@). When the build is created by pushing code to the develop branch or releasing a tag, these variables are automatically updated. In the generated zip files, you can see the correct version number and release date.

I checked the commits on the master branch and found that in versions 5.5.16 and 5.5.19, the version number and release date were updated directly in the blueprints.yaml file (i.e., the variable was replaced with a static version and date). Here are two example commits where this was done:

Release 5.5.16 - Automatic Version Number Updates(Attempt 2) · gantry/gantry5@a7e5de4

Release 5.5.19 - Automatic Version Number Updates · gantry/gantry5@5172eb4

However, in versions 5.5.17 and 5.5.18, I couldn’t find any static version update. So, I’m not entirely sure how the version number is being handled in the master branch—whether the version variable is being replaced with a static value or not.

Should we manually updating the correct version number in the master branch and pushing it to see if the Grav CMS plugin system correctly picks up the updated version.