Drupal 8.3.2 installed via composer reports version 8.3.3-dev in UI

Hello
Same bug !

I update with composer.

Composer say : 8.3.1 --> 8.3.2
but it's 8.3.3-DEV after !!!

https://www.drupal.org/node/2875451

Thanks.
Didier

I don't think it's a Composer cache problem
because Composer say

- Updating drupal/core (8.3.1 => 8.3.2): Downloading (100%)

but after, Drush and Drupal say : 8.3.3-dev

Probably a drupal.org server error on the files downloaded... ?

See: #2352091-56: Create (and maintain) a subtree split of Drupal core

It's because drush uses \Drupal::VERSION.

I don't think so.

Where Drush would be able to find a 8.3.3-dev version?

And Drupal status page also say 8.3.3-dev...

Exact issue exists in 8.2.8 as well.

This is not what I experienced upgrading 8.3.1 to 8.3.2 with Composer. \Drupal::VERSION = 8.3.2 and the UI agrees. I am, I hope you understand, confused and a little nervous because I released it.

There are tags missing from https://github.com/drupal/core/releases.

I made backup before "Composer update..."

So I restore all the folders and site is up in D 8.3.1.

So, not urgent
But I wait to understand before try again.
Thanks.
Didier

Oh, that's just sorting, but the dates of the releases and tags are weird for what it's worth.

I just did composer create-project drupal-composer/drupal-project:8.x-dev SOME_DIR--stability dev --no-interaction and looking at core/lib/Drupal.php this is what I see:

  const VERSION = '8.3.2';

This was a bug with the way the subtree splits handled the new tag. I've since modified the splits such that they *should* be more likely to not push 8.3.x-dev as the 8.3.2 tag.

I had deleted the tag that had the incorrect hash from drupal/core and resplit and reposted. This was fixed around 1pm pst.

Thank you mixologic.

I will try again this evening.
Thanks you mixologic and celifen.
;-)

@Mixologic is this fixed so that it'll never happen again?

@alexpott : well, thats the hope. The former code was reusing HEAD over and over to re-tag, and reusing the same repo. Now when new tags get split, they only exist as their tag name and do not collide in HEAD: https://bitbucket.org/drupalorg-infrastructure/subtree-splitter/commits/...

When I reran the splitter, it rebuilt the tags properly.

Yesterday I restore the D8.3.1 site.
Today I try again

composer update --with-dependencies

and ALL is ok !
Site is now in D8.3.2

Thanks

Hi,

Since update Drupal 8.3.1 to 8.3.2, I have an error : The website encountered an unexpected error. Please try again later. on the page www.example.net/update.php

And on the rest of the website, I have a redirection on www.example.net/core/install.php

I had the same issued when I was installed Drupal 8.3.0.

Someone can help me ?

Thx

#2884479: Composer create-project does not install core