Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No versions in Wordpress plugin repo #478

Closed
Floppy opened this issue Jun 6, 2018 · 4 comments
Closed

No versions in Wordpress plugin repo #478

Floppy opened this issue Jun 6, 2018 · 4 comments
Assignees
Milestone

Comments

@Floppy
Copy link

Floppy commented Jun 6, 2018

DISCLAIMER: I'm not 100% sure where the root cause of this problem is - I think it's here, but it might not be.

We use composer to manage our Wordpress plugins, including Auth0. We are using it via wpackagist in order to do so. The plugin is listed here: https://wpackagist.org/search?q=auth0&type=any&search=

Our composer lockfile specifies 3.5.2 - we'll upgrade to 3.6.0 in time, but when we've tested it properly with our setup.

The composer lockfile specifies this:

        {
            "name": "wpackagist-plugin/auth0",
            "version": "3.5.2",
            "source": {
                "type": "svn",
                "url": "https://plugins.svn.wordpress.org/auth0/",
                "reference": "trunk"
            },
            "dist": {
                "type": "zip",
                "url": "https://downloads.wordpress.org/plugin/auth0.zip?timestamp=1523639413",
                "reference": null,
                "shasum": null
            },
            "require": {
                "composer/installers": "~1.0"
            },
            "type": "wordpress-plugin",
            "homepage": "https://wordpress.org/plugins/auth0/"
        },

As you can see, while the lock mentions 3.5.2, the actual URLs don't include any version information. If I use the dist URL, I get 3.6.0, not 3.5.2. The timestamp has no effect.

wpackagist builds its packages from the information at https://plugins.svn.wordpress.org/. The auth0 plugin release in there just includes trunk, no tag information.

This means that it's impossible to download older versions of the plugin, either from Wordpress itself or via wpackagist.

Would it be possible to push release tags into the wordpress plugins svn repo so that versions can be properly managed through it?

This is pretty critical for us; currently we cannot deploy our service as we can't rely on which version of the auth0 plugin we are going to get.

@Floppy
Copy link
Author

Floppy commented Jun 6, 2018

I've resolved this in our case by referencing the git repository directly in my composer.json, but this will still affect anyone trying to use it via the official plugin repository.

@joshcanhelp
Copy link
Contributor

@Floppy - Thanks for bringing this up. I noticed a while back that the WP.org repo listing doesn't have older versions listed and have it on my list to check that. We use a Jenkins script to deploy from master on this repo and we should be able to adjust that to push the release tag as well. I have a fixit release that needs to come out here soon so I'll see if I can add tags to the deployment process before that happens.

@joshcanhelp joshcanhelp self-assigned this Jun 6, 2018
@joshcanhelp joshcanhelp added this to the v3-next milestone Jun 6, 2018
@joshcanhelp
Copy link
Contributor

This didn't require any changes to the plugin code at all. I just pushed all 3.x tags to the WP.org SVN repo and you can now see them listed here:

https://wordpress.org/plugins/auth0/advanced/

One-liner bash script if anyone else out there wants to do the same:

https://gist.github.com/joshcanhelp/2120f1b7abf5e170fb7d1a001ed73dd8

@Floppy
Copy link
Author

Floppy commented Jun 6, 2018

Great stuff! It was a bit of a surprise, certainly made my day more interesting :)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants