Placeholder issue for any tasks related to Backdrop CMS for https://github.com/mbaynton/cms-autoupdate-design with task list to be eventually formed for any actionable things specific to us.
Everyone's opinion is welcomed, but we specifically seek opinions from the PMC members.
Respective/related issue in d.org: https://www.drupal.org/node/2367319 (efforts moved to contrib in https://www.drupal.org/project/automatic_updates)
- [ ] #414: The automatic part
- [x] #1911: Improve update experience
- [ ] #1992: Include digital signatures on packages
- [ ] #2024: Improve security of updates
- [x] #2555: Move
/profilesunder/core/profiles - [x] #3105: Add ability to update Backdrop core via UI
- [ ] #3208: Remove/deprecate authorize.php
- [x] #3271: Expose the Backdrop core update via the UI by default
- [ ] #3714: Installer should check digital signatures.
- [x] #3008: Symlink to document root causing module update issues
June 2021 update
From the Drupal 9.2 release announcement blog post:
The Automated Updates Initiative has been very active in the repositories under https://github.com/php-tuf building a PHP implementation of The Update Framework (TUF) with Typo3 and Joomla developers to provide signing and verification for secure PHP application updates. Results will be included with later Drupal releases.
Recent comments
Sorry - it is the field_group module. However, last night I switched off proxying to the site and proved to Cloudflare Support that it was NOT a Backdrop issue. After a thorough...
Cloudflare specific advice needed [SOLVED]
@ian I am getting lost what module are you using that is version 1.x-1.6.0 and 1.x-1.7.0 ?
Cloudflare specific advice needed [SOLVED]
I'm also now getting a 403 when trying to access admin/reports/updates - it seems to be Backdrop generated but there is nothing in the Recent Log messages other than my login as admin...
Cloudflare specific advice needed [SOLVED]