• Resolved pivic


    My automatic upgrade failed:


    WordPress 5.2-alpha-44986
    Updating to WordPress 5.2-alpha-44986
    Downloading update from https://wordpress.org/nightly-builds/wordpress-latest.zip…
    Installation Failed
    Error: [signature_verification_no_signature] The authenticity of <span class=”code”>wordpress-latest.zip</span> could not be verified as no signature was found.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Marius L. J.



    Last second, before rolling out WordPress 5.2-beta1, a problem was discovered with the new package signing system intended to improve security for updates.

    You can find the preliminary details at https://make.wordpress.org/core/2019/03/23/wordpress-5-2-beta-1-status-update-take-two/

    I’m going to mark this as resolved as it has a core ticket and a core post about why it happens just to make it easier to keep tabs on what happens with the alpha and beta.

    Thread Starter pivic


    Thanks! I can mention that my latest automatic upgrade worked without a hitch.

    My site failed to install the automatic update sometime later in the day on 22 March 2019 EDT. I’m currently on WordPress 5.2-alpha-44976. I’ve attempted the update several times since but every time it fails.

    Also the “date of last check” is stuck on the beginning of Unix time “Last checked on December 31, 1969 at 8:00 pm”.

    I have tried to install the wp-cli on my Mac OS X server, but am out of my depth trying to get it to run – I get a parse error message

    Parse error: parse error in phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/IncludeFrameworkAutoloader.php on line 34


    Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Advisor and Activist

    @thekiwi You’ll have to do it manually if you can’t use wp-cli (which is on your web server, not your laptop normally).

    Everyone, I’m closing this because we have a policy to resolve alpha/beta posts when there’s a ticket. In this case, we have a make post – https://make.wordpress.org/core/2019/03/23/wordpress-5-2-beta-1-status-update-take-two/

    That lets mods and volunteers know we don’t have to jump in and find an issue. And yes, if you’re running WP Beta or Alpha, we do expect you to be able to manually update WordPress: https://codex.wordpress.org/Updating_WordPress#Manual_Update

    You’re going to want to know how to do that, as debugging betas is always a bit more hands on.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Failed update, 5.2 alpha’ is closed to new replies.