-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backdrop 1.29.2 Release checklist #6757
Comments
Release notes draft: Security release for Backdrop CMS. This release fixes 2 security vulnerabilities: Notes for updating
Changes since 1.29.1This release contains the additional bug fixes and changes: Bug fixes
Miscellaneous changes
|
The tag is cut for https://github.com/backdrop/backdrop/releases/tag/1.29.2 |
Release notes look great now! |
This link is giving an Access Denied: BACKDROP-SA-CORE-2024-002 |
@argiepiano Yep, we're still putting the announcement together, it will be ready in 5-10 minutes. |
The SA is not published until the release goes out :) |
All releases are out 🎉 |
I went ahead and updated the Demo Sandboxes since I believe @klonos is traveling. |
I've updated the Pantheon upstream. |
CVE has been requested. |
Release scheduled for November 20, 2024 10am - 4pm PT
Pre-release tasks
Fix
orFixed
,Add
orAdded
.**Notes for updating**
core
directory, for example:- No changes have been made to the `.htaccess`, `robots.txt` or default `settings.php` files in this release. Updating customized versions of those files is not necessary.
.htaccess
settings.php
The database update script does **not** need to be run.
**It will be necessary to run the update script** (located at /core/update.php) for this release.
ls -1 core/modules/*/*.install | while read filename; do echo "$(git log -1 --pretty="format:%ad %f" --date=format:"%F %R" -- $filename)" $filename; done|sort
**Changes since version 1.xx.x** are listed below.
release-notes
artifact attached to the generator.Release tasks
Immediate Post-release tasks
Backdrop's Website updates
See Also
The text was updated successfully, but these errors were encountered: