Releases for Automatic Updates

This release drops compatibility with all versions of core older than 11.2, due to a backwards compatibility breaking change in core's Package Manager module.

Early preview of Automatic Updates 4.x, which is identical to Automatic Updates 3.1.x except that it uses core's version of Package Manager. This means you will need to alter your settings.php to use it; see the related documentation for more information.

Fixed a performance issue that could manifest in certain circumstances (#3465155: automatic_updates_modules_installed() significantly slows down module install) and a bug (#3446371: UnknownPathExcluder will exclude base Composer path repos if t

Updates Composer Stager to 2.0.0-rc5 (#3462138: Update Composer Stager to 2.0.0-rc5) and uses the very fast xxHash algorithm for non-cryptographic hashing operations (#3441923: Use xxHash instead of SHA-256 when security is not a concern

This release is a hotfix that updates our dependencies, in order to work around a regression caused by changes in Symfony.

Contributors (7)

phenaproxima, tedbow, TravisCarden, azizos, omkar.podey, Wim Leers, grasmash

This release contains a couple issues that warnings for users using setup that will not longer be support in 3.1.0

Hotfixes a backwards compatibility break by pinning Composer Stager to 2.0.0-beta3.

This is the first stable release of the 3.0.x branch so here are some of the major updates since our last 8.x-2.x release, 8.x-2.7

Our first Beta for 3.0.0. Please test!

So...here we are again! The biggest advancement in this release is that automatic updates are now done under the hood by a new command-line utility. No, not Drush -- there is no Drush dependency here! In addition to everything Automatic Updates already did, you can update your site at the command line super easily:

vendor/bin/auto-update

Yup, that's it. 🤯

Two nice changes in this release.

First, we no longer declare compatibility with Drupal 9.7, which is a fantasy version of Drupal that we made up for internal testing purposes. Nice to remove that little misleading bit of information.

Second, we've introduced an audit log feature to Package Manager. It will now log all the changes that were requested, as well as which changes were actually made, for inspection by privileged users.

First Alpha Release of 3.0.0

Please test!

Major non-test changes since 8.x-2.6

1. #3331310 by kunal.sachdev, tedbow, Wim Leers: Exclude unknown paths in project base: only allow vendor + web root + whatever drupal/core-composer-scaffold allows

Welcome to the latest episode release of Automatic Updates!

This one has a few API changes and deprecations, so read closely if you're integrating with Package Manager's API. (That means you, Project Browser. 😉)

Hello there! Allow me to gift you...a new maintenance and bugfix release of Automatic Updates.

We've been busy. This time around:

Happy August! Here's a new release of Automatic Updates.

We made some modest, but nice, changes:

Another day, another release candidate of Automatic Updates. We're just that slick.

Automatic Updates' requirements and limitations are now documented in our README. Beyond that, the major changes this time around:

Another day, another beta.

This release does a lot of refactoring and fixes several bugs found during beta testing at DrupalCon Portland. Thanks again to all the people who tested it, and submitted excellent bug reports!

We've continued refinining Package Manager's API, especially its boundaries and edge case handling, and strive to make it behave as clearly and consistently as possible. We're excited to see what gets built on top of it! (Looking at you, Project Browser...)

Issues fixed in this release:

Step right up for the second beta of Automatic Updates! This release requires Composer 2.3.5 or later to perform updates.

This release is mostly about clean-up, refactoring, and internal testing improvements. Drush compatibility is slightly improved, although there are still outstanding issues on that front. Some groundwork is also laid for updating contributed modules and themes, rather than just Drupal core, but that functionality is not yet ready for testing, except by the foolhardiestbravest.

Issues fixed in this release:

Major issues since 8.x-2.0-alpha1

• Validate update_fetch_with_http_fallback setting
• Validate some Composer settings
• Remove the ability for post-operation stage events to flag warnings

Dev branch to support composer-based site installs, among other things.

Stable release.

#3088922: Check for updates to polyfills mid December 2019 by heddn
#3100944: Roll new pub key by heddn