Skip to content

Dev - #7

Merged
Fabien83560 merged 8 commits into
mainfrom
dev
Jul 8, 2026
Merged

Dev#7
Fabien83560 merged 8 commits into
mainfrom
dev

Conversation

@Fabien83560

Copy link
Copy Markdown
Member

Summary

Type of change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation
  • CI / tooling

Related issue

Closes #

Changes

Testing

  • Existing tests pass
  • New tests added (if applicable)
  • Tested manually — steps described below

Checklist

  • My code follows the project's style and conventions
  • I have updated the documentation if needed
  • I have updated CHANGELOG.md
  • No sensitive data is exposed (no tokens, no real user data, no private URLs)

composer install --no-security-blocking is not a valid Composer 2.x
flag, so every CI and release run failed at the install step.
HTML_B64 was empty, so PHP SDK users only ever saw the fallback
message instead of the real dashboard. The sync-dashboard workflow
never ran successfully, so the UI is embedded manually here from the
current dashboard-ui source until the workflow issue is resolved.
…rity advisories

The whole laravel/framework ^11.0 line is caught by security advisories
with no 11.x fix (PKSA-m5cs-t1y6-qpcs, PKSA-3r5d-mb8f-1qw9,
PKSA-mdq4-51ck-6kdq), which blocked composer install once the invalid
--no-security-blocking CI flag was removed. Bumped to laravel/framework
^12.55 and orchestra/testbench ^10.0 (require-dev only, no impact on
the package's own runtime requirements). composer audit is now clean
and the test suite still passes (24/24).
No linter was configured in this repo. Added friendsofphp/php-cs-fixer
as a dev dependency with the @psr12 ruleset, and a dedicated lint job
in ci.yml running it in --dry-run mode.
Brace style for single-line control structures, fn () / new class ()
spacing, and similar PSR-12 conformance fixes with no behavior change.
24/24 tests still pass.
Matches the saas-api header rename (CDC section 8.4.1). Breaking
change for cloud mode users — must ship together with the saas-api
and other SDKs' companion renames.

Verified end-to-end: CloudTransport::writeRoutes() against a local
saas-api test instance registers the route correctly with the new
header. 24/24 tests still pass.
Guard against silently shortening the send cadence: no public path
forwards the internal $flushInterval constructor parameter (both call
sites in the service provider pass three arguments), so a reflection
test pins its default to 60s.
Ship the breaking cloud header rename (X-API-Key -> X-APIForge-Key).
The published 2.x sends the old header and is rejected with 401 by the
current API; 3.0.0 is required for cloud mode.
@Fabien83560
Fabien83560 merged commit 54b594e into main Jul 8, 2026
6 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