Skip to content

fix(deps): update getgrav/grav 2.2.28 → 2.2.29 - #4636

Merged
truecharts-admin merged 1 commit into
mainfrom
renovate/getgrav-grav-2.2.x
Nov 11, 2026
Merged

truecharts-admin merged 1 commit into
mainfrom
renovate/getgrav-grav-2.2.x

Conversation

@truecharts-admin

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
getgrav/grav patch 2.2.28 → 2.2.29

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

getgrav/grav

v2.2.29

Compare Source

11/10/2026

    • Log files in logs/ now rotate when they reach 10 MB: grav.log becomes grav.log.1, older copies are gzipped (grav.log.2.gz and on), and five are kept. grav.log, security.log and scheduler.log rotate as they are written, an hourly log-rotate scheduler job catches plugin logs, and bin/grav logrotate runs it by hand. Change or turn it off under system.log.rotate (Configuration → System → Error handler)
    • A page can unpublish everything below it along with itself. Set cascade_unpublish: true on a page (Options → "Unpublish child pages too"), and while that page is unpublished, by published: false or by its publish_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 own published setting, so they are back as they were once the parent is published again, and a section given a publish_date goes 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 page
    • A backup profile's Scheduled Backup switch now decides on its own whether the backup runs. An old Enabled or Disabled entry for the backup job in user/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 #​4397
    • A scheduler job that fails now keeps what it printed to standard output as well as its error output, so the reason shows in the job's history, user/data/scheduler/status.yaml and 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
    • A page with a link or image whose address is longer than any file path, such as an inline image written as /data:image/png;base64,..., no longer turns into an error page on servers with open_basedir set
    • Several Grav sites on one server no longer try to load each other's files. The class loader's APCu cache is now kept separate for each site, so a class found in one site's vendor/ folder is never looked up at another site's path #​4392
    • The Page IDs option and the GFM and table Markdown options in Configuration → System use translation keys instead of English written into the blueprint, so they can be translated. The English comes from Admin2 2.2.13 and Admin 1.10.63

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@coderabbitai

coderabbitai Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Chores
    • Updated the Grav Docker image from version 2.2.28 to 2.2.29. This change updates the version used when building the image; the pull request summary does not indicate any other changes. The update is limited to the packaged image version and does not describe changes to Grav’s features or behavior.

The Grav Docker image VERSION default changes from 2.2.28 to 2.2.29.

Changes: Grav version update

Layer / File(s) Summary
Update Grav version default
apps/grav/docker-bake.hcl
The default VERSION changes from 2.2.28 to 2.2.29.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Possibly related issues

  • Issue 1 tracks Dockerfile dependency updates, including the Grav release version updated here.
Merge Risk: Minimal · up to 2b6d0

Grav builds now default to 2.2.29. No merge-blocking issue is established.

Architecture risk: Low · up to 2b6d0

The change affects 1 system.

Changed systems: apps/grav

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — apps/grav (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in apps/grav/docker-bake.hcl: The VERSION default changes from 2.2.28 to 2.2.29.
Pre-merge checks: Passed 5

Check name Status Explanation
Title check Passed The title clearly identifies the Grav dependency update from 2.2.28 to 2.2.29.
Description check Passed The description explains the Grav version update and includes related release notes.
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: e54b3a21-bdad-48ce-b2f8-f33ce6d75720
Commits

Reviewing files that changed from the base of the PR and between e252a79 and 2b6d0ad.

Files selected for processing: 1

  • apps/grav/docker-bake.hcl

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 1 remain after this review.

@trueforge-bot

trueforge-bot Bot commented Nov 11, 2026

Copy link
Copy Markdown

📦 App Size Analysis

Note

Comparing ghcr.io/trueforge-org/grav:rolling ➔ ghcr.io/trueforge-org/grav:sandbox

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 486.85 MB 486.89 MB +45.33 kB (+0.01%) 🔼
linux/arm64 185.22 MB 185.27 MB +47.5 kB (+0.03%) 🔼

@Crow-Control Crow-Control left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved automated PR

@truecharts-admin
truecharts-admin merged commit 6d54631 into main Nov 11, 2026
15 checks passed
@truecharts-admin
truecharts-admin deleted the renovate/getgrav-grav-2.2.x branch November 11, 2026 01:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants