v1.10.0

What's Changed

Add App\Services\CacheHelper — enhanced caching utilities:

• Namespaced cache keys (key()) with composite param serialization
• TTL jitter (ttlWithJitter()) to prevent cache stampede / thundering herd
• remember() / forget() patterns
• Batch getMany() / putMany()

Ported from the lairner project.

Full Changelog: https://github.com/timanthonyalexander/baseapi-template/compare/v1.9.5...v1.10.0

v1.9.5

chore: bump baseapi to v1.9.5

v1.9.4.1

Patch on top of v1.9.4

Test maintenance follow-up to v1.9.4. No runtime/behavior changes.

Fixed

• Example & health Feature tests now pass on a clean checkout. The template ships response.wrap_data=false (the new default), but the bundled tests still asserted the legacy { data } envelope, so all 8 failed out of the box. Their assertions now target the actual top-level response shape (ok, db, cache.working), and the full suite is green (19 tests, 53 assertions).

Note

• response.wrap_data stays false — only the tests were adapted.

All v1.9.4 auth fixes (session persistence, password-hash leak, /me Bearer auth, unknown-email 401) and the baseapi/baseapi v1.9.4 upgrade are included.

v1.9.4

Auth fixes for fresh installations

This release fixes four auth bugs that every new project scaffolded from this template inherited, and upgrades the framework to baseapi/baseapi v1.9.4.

Fixed

• Session login never persisted. LoginController/SignupController wrote $this->request->session['user_id'] — a by-value copy of $_SESSION that PHP never persists — so a successful login was silently dropped on the very next request. They now write $_SESSION directly.
• Login crashed on an unknown email. User::firstWhere() returns null for an unknown email, and checkPassword() was called on it, causing a fatal null-method error instead of a 401. Now guarded with instanceof User.
• Password hash leaked in responses. BaseModel::jsonSerialize() serializes every public property, including the bcrypt password — exposed in login/signup/me responses and the $request->user payload. User now overrides jsonSerialize() to strip it.
• /me rejected API-token auth. MeController read $_SESSION only, returning 401 for valid Bearer token requests (the SPA path). It now reads $request->user set by CombinedAuthMiddleware, working for both session and token auth.

Changed

• Upgraded baseapi/baseapi v1.9.0 → v1.9.4.

Known issue

• The bundled example/health Feature tests assume a { data } response envelope while the template ships response.wrap_data=false. These failures are pre-existing and unrelated to this release.

v1.9.0.1

Fix

v1.9.0

Update

1.7.5: Sync

Update

v1.7.4.1: TranslationService update

Update transserv

v1.7.4: Sync

Upgrade baseapi template

v1.6.6: Sync

Update baseapi template