Problem/Motivation

#2867757: Improve instructions for updating composer.json and /vendor gets the docs out the door so people don't break their sites.

This issue discusses some finer points, such as whether or not to add --no-dev.

See #2867757-41: Improve instructions for updating composer.json and /vendor:

+++ b/core/UPDATE.txt
@@ -64,15 +64,51 @@ following the instructions in the INTRODUCTION section at the top of this file:
+   Note, if you want to only update drupal/core the following command will
+   probably work:
+
+     /PATH/TO/composer update drupal/core symfony/* --with-all-dependencies

Are we sure that symfony/* is needed here? #36 explains the initial rationale for that, but are we sure those problems weren't a consequence of https://github.com/composer/composer/issues/4795, which is now fixed with --with-all-dependencies as per https://github.com/composer/composer/issues/6661?

and #2867757-42: Improve instructions for updating composer.json and /vendor:

+++ b/core/UPDATE.txt
@@ -64,15 +64,51 @@ following the instructions in the INTRODUCTION section at the top of this file:
+1. On a typical Unix/Linux command line, run the following command from the root
+   directory (replace /PATH/TO/composer with the appropriate location for your
+   system):
+
+     /PATH/TO/composer update

Maybe say --no-dev, or add a comment that it's a good idea to add --no-dev to production for security reasons.

Proposed resolution

Remaining tasks

- Hash out a list of "finer points" to be in scope for the issue.
- Come up with good answers to the points.
- Patch UPDATE.txt
- Review / churn / RTBC
- Commit

User interface changes

API changes

Data model changes

Comments

Mile23 created an issue. See original summary.

dww’s picture

dww
we/he/they
commented
Issue summary: View changes

What other "finer points" are in scope here that need to be hashed out and addressed?

Thanks,
-Derek

mile23’s picture

mile23
Primary language English
Location Seattle, WA
commented
Issue summary: View changes

Updated IS with the comments that gave life to this issue.

cilefen’s picture

cilefen commented
Related issues: +#3012129: Add composer-based install instructions to the Drupal project page

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Issue tags: -Composer +Composer initiative

I think that this is going to need updating once we get more stuff done in 8.8.0

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Active » Closed (outdated)

I think this is outdated. UPDATE.txt has a link to https://www.drupal.org/docs/updating-drupal/updating-drupal-core-via-com... for updating via composer. The goal now would be to keep those instructions correct and up to date.

I am closing this as outdated.