Problem/Motivation

While working on updating the Packages.org description text for the drupal/recommended-project project page in #3354453: Add Drupal 'keywords' to Recommended Drupal project composer.json, and update description I see that the default versions on https://github.com/drupal are quite old for most repositories.

It is best practice to make the latest official release (10.0) or dev-release (10.1) the default branch on Github and Gitlab, for many different reasons:

  • To show the latest updated README.md and relevant information
  • To make sure services which pull data from those repos get the right info
  • For better SEO
  • To make it clear which repos are outdated, and point to the relevant repos

Steps to reproduce

Proposed resolution

  • Update the default version to the current official release for relevant repos at every minor version release of Drupal 10.1, 10.2, etc.
  • Update or add README file, stating prominently at the top if the repo is outdated, and link to the relevant replacement repo

Remaining tasks

  • ✅ done - Update http://drupal.org/ to https://drupal.org/ on https://github.com/drupal
  • ✅ done - Update the default versions to the latest release, or dev-release
  • Update README file, stating at the top if the repo is deprecated, possibly link to relevant replacement
  • Make sure the default version of relevant repositories are updated to the current official release, by adding this task to the checklist when minor versions of Drupal (10.1, 10.2, etc.) are released every half year or so

User interface changes

API changes

Data model changes

Comments

ressa created an issue. See original summary.

ressa’s picture

Title: Set default version to latest official release on github.com/drupal » Set default repo version to latest official release on github.com/drupal
drumm’s picture

Issue summary: View changes
drumm’s picture

It looks like we could update the default branch automatically with GitHub’s API https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#update.... (I don't see a way to do this with Git commands.)

drumm’s picture

ressa’s picture

Title: Set default repo version to latest official release on github.com/drupal » Set default github.com/drupal repo versions to latest official release, update README
Issue summary: View changes

Add extra task about updating deprecated repo README's:

  • Update README file if the repo is deprecated, link to relevant replacement repo
ressa’s picture

Issue summary: View changes
ressa’s picture

Thanks for looking into this @drumm, updating the relevant repos via API would be nice. Most of the still used, recently updated repos have defaults on 8.x: https://github.com/orgs/drupal/repositories?type=all

I just looked at the Drupal Composer Scaffold, which is still on the old version. These are some important differences in the README displayed (8.x) and 11.x:

233c236
<   "drupal/core",
---
>   "example/assets",
384c387
<     "composer/installers": "^1.2",
---
>     "composer/installers": "^2.0",
395,397d397
<       "allowed-packages": [
<         "drupal/core"
<       ],
402d401
<       "overwrite": true,
drumm’s picture

I’ve updated the default branches to 11.x

ressa’s picture

Issue summary: View changes
Status: Active » Fixed

Beautiful, thanks @drumm!

Maybe it would be worth adding to a checklist, to remember to repeat the process, when the Drupal 12 branch is created? Anyway, the main tasks here are solved, so changing status. (Unless you think the "Update README file with deprecated text" item is relevant ...)

Status: Fixed » Closed (fixed)

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