Problem/Motivation
On the Available Updates page (by URL: domain.tld/admin/reports/updates/update) under the Contrib section in the Core section there's a message saying: "Updates of Drupal core are not supported at this time." In my opinion this sounds misleading, because this is only about automatically performed updates, not in general. A novice admin user may misunderstands whether their core is ready to be updated or not? Of course it's ready, but only manually.
Here on localize.drupal.org you can see that this string with ID#354960 is quite old, has been used since D7.x first alpha release.
Proposed resolution
Insert the missing word "Automatic" (or any synonym) into the beginning of the string forming "Automatic updates of Drupal core are not supported at this time." This would became into a new string on l.d.o.
Remaining tasks
AFAIK this string occurs in core/modules/update/src/Form/UpdateManagerUpdate.php at line #281:

if (!empty($projects['manual'])) {
$prefix = '<h2>' . $this->t('Manual updates required') . '</h2>';
$prefix .= '<p>' . $this->t('Updates of Drupal core are not supported at this time.') . '</p>';
$form['manual_updates'] = [
'#type' => 'table',
'#header' => $headers,
'#rows' => $projects['manual'],
'#prefix' => $prefix,
'#weight' => 120,
];
}User interface changes
Only intentional UI string change.
API changes
No.
Data model changes
No.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 2887114-4.patch | 789 bytes | alauzon |
Comments
Comment #2
cilefen commentedGood point! We cannot change translatable strings in patch releases so this goes in 8.4.x.
Comment #3
alauzon commentedI'm working on it from DrupalCampMontréal2017 sprint.
Comment #4
alauzon commentedHere is a patch doing exactly that.
Comment #5
maxocub commentedComment #6
naveenvalechaRTBC +1
This is a string change. However, we are too much far from 8.4.0 so that
shouldn'tshould be fine.//Naveen
Comment #8
xjmThat improved string makes more sense to me as well. Committed and pushed to 8.4.s at DrupalCamp Montréal. Thanks @alauzon!
Comment #11
xjmOops, committed it to the wrong branch by mistake. Revert and recommit is me fixing that.