I am currently using 3.0.0-rc2...

editorially_module-showing_v_3.0.0-rc2

When I attempt to update to the full release via composer, I so no changes...

composer require "drupal/editoria11y:^3.0"
./composer.json has been updated
Running composer update drupal/editoria11y
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Writing lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove

...and so my installed version stays on 3.0.0-rc2

What I doing wrong here?

CommentFileSizeAuthor
editorially_module-showing_v_3.0.0-rc2.png35.08 KBsirclickalot

Comments

sirclickalot created an issue. See original summary.

agoradesign’s picture

agoradesign commented

nothing, there's something wrong with the 3.0.0 release:

drupal/editoria11y 3.0.0 requires drupal/core ~8.0 -> satisfiable by drupal/core[8.0.x-dev, ..., 8.9.x-dev].

itmaybejj’s picture

itmaybejj commented

I'm looking into this. @agoradesign I'm not sure what could be triggering that; the module requirements have been fixed since early in the beta.

@sirclickalot -- you don't need to worry; 3.0.0 is exactly the same as 3.0.0-rc2, with the sole exception of being "blessed" as the final release. So you are on the current code. It's possible the lack of changes is the "problem."

itmaybejj’s picture

itmaybejj commented
Assigned: Unassigned » itmaybejj
itmaybejj’s picture

itmaybejj commented
Category: Support request » Bug report
Priority: Normal » Major

@agoradesign you are correct. Something happened in the Drupal packaging system, and the packaged version of the release does not reflect my codebase. I'm going to chat with Drupal infra about this and then cut a new release to force the Drupal packaging system to run again once they confirm it is working.

In the interim, just stick to RC2. It is the same code.

itmaybejj’s picture

itmaybejj commented
Title: Updating to 3.0.0 via composer » Drupal packaging script did not run correctly for 3.0.0 release
Status: Active » Fixed

@agoradesign and @sirclickalot -- @drumm re-ran Drupal's packaging script (...and taught me how: just open and re-save the release notes...), and on this run it updated correctly. The packaged version of 3.0.0 now matches my codebase again, and I can confirm it installs without problem again. It's possible you may need to refresh your composer cache if it does not pick up the new metadata.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

agoradesign’s picture

agoradesign commented

thank you!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.