Skip to content

Release: health checks info-only connection count, drop OptimizedApp - #128

Merged
StanBarrows merged 3 commits into
productionfrom
main
Oct 23, 2026
Merged

StanBarrows merged 3 commits into
productionfrom
main

Conversation

@StanBarrows

Copy link
Copy Markdown
Contributor

Release of two health check fixes from `main`:

  • drop `OptimizedAppCheck`: the caches built by the Cloud deploy command never reach the running containers, so it failed on every Cloud environment
  • `DatabaseConnectionCountCheck` is informational only: reports `N connections`, never warns or fails; on PostgreSQL it counts only the current database

🤖 Generated with Claude Code

Sebastian BURGIN-FIX (ext) and others added 3 commits October 23, 2026 16:09
…y-time caches

The config, route and event caches built by the Cloud deploy command never
reach the running containers, so OptimizedAppCheck failed on every Cloud
environment. php artisan optimize stays in the deploy script.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DatabaseConnectionCountCheck no longer warns or fails; it reports
"N connections" with the count in meta. On PostgreSQL it counts only
pg_stat_activity rows of the current database, because the Neon servers
are shared between apps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Larastan analyses tests in this repo; the Mockery partial and the chained
connectionName()->count() calls were reported as untyped. Use an
anonymous subclass instead, as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@StanBarrows
StanBarrows merged commit 7c9a602 into production Oct 23, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant