Repository navigation
fix(deps): update getgrav/grav 2.2.28 → 2.2.29 - #4636
Merged
Merged
Conversation
truecharts-admin
requested review from
Crow-Control and
alfi0812
as code owners
November 11, 2026 01:11
truecharts-admin
enabled auto-merge (squash)
November 11, 2026 01:11
📦 App Size AnalysisNote Comparing 📈 Size Comparison Table
|
Crow-Control
approved these changes
Nov 11, 2026
Crow-Control
left a comment
Member
There was a problem hiding this comment.
Auto approved automated PR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.2.28→2.2.29Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
getgrav/grav
v2.2.29Compare Source
11/10/2026
logs/now rotate when they reach 10 MB:grav.logbecomesgrav.log.1, older copies are gzipped (grav.log.2.gzand on), and five are kept.grav.log,security.logandscheduler.logrotate as they are written, an hourlylog-rotatescheduler job catches plugin logs, andbin/grav logrotateruns it by hand. Change or turn it off undersystem.log.rotate(Configuration → System → Error handler)cascade_unpublish: trueon a page (Options → "Unpublish child pages too"), and while that page is unpublished, bypublished: falseor by itspublish_date/unpublish_date, every page below it is unpublished too: left out of menus, collections, the sitemap and search, and not served. The pages below keep their ownpublishedsetting, so they are back as they were once the parent is published again, and a section given apublish_dategoes live all at once.system.pages.cascade_unpublish(Configuration → System → Content) sets the default for every page, and is off.$page->unpublishedBy()returns the route of the page that hides a pageuser/config/scheduler.yaml, which classic admin wrote whenever its Scheduler page was saved, used to override it, so backups could stop with the switch on #4397user/data/scheduler/status.yamland the output file. Most console commands print their errors to standard output, so a failed run used to be recorded with no output at all/data:image/png;base64,..., no longer turns into an error page on servers withopen_basedirsetvendor/folder is never looked up at another site's path #4392Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.