Skip to content

Releases

1.0.0-beta.4 - PHP 8.6 CI coverage and standardized quality checks

Choose a tag to compare

@allanmcarvalho allanmcarvalho released this 20 Nov 23:40

Changed

  • CI now uses Maintainer’s strict, non-interactive quality command in place of standalone PHP analysis, lint, and unit-test steps and frontend check and test steps, while keeping PHP type tests and the frontend build separate.
  • Vue type checking is no longer part of Maintainer’s default checks.

Documentation

  • AGENTS.md now documents the expanded PHP coverage.

Testing

  • Laravel 13 CI now tests PHP 8.6 alongside PHP 8.5 on Ubuntu and Windows with both lowest and stable dependencies, without raising Dapter’s runtime PHP requirement.
  • Native database CI now tests both PHP versions without fail-fast, so a failure in one job does not stop the other.
  • composer test now runs PHPStan, Pint, and Pest through Maintainer’s strict quality command before running the separate PHP type tests, and composer quality:check also uses strict mode.
  • Pest defaults to four workers on Unix and serial execution on native Windows, with overrides via MAINTAINER_PEST_PARALLEL and MAINTAINER_PEST_PROCESSES, while Vitest is capped at four workers.

Internal Maintenance

  • The PHP 8.5 native database job keeps the native-backends name, and the new job is named native-backends / PHP 8.6.
  • Both workflows update the Maintainer setup action from 1.14.2 to 1.14.4.
  • New pull request runs cancel older runs for the same workflow and ref, while runs for different commits on other events no longer cancel one another.

1.0.0-beta.3 - Stronger CI verification and clearer beta installation guidance

Choose a tag to compare

@allanmcarvalho allanmcarvalho released this 20 Nov 15:51

Documentation

  • The README now uses composer require 'artisan-toolbox/dapter:@beta' tightenco/ziggy so Composer can select a compatible Dapter beta without relaxing project-wide stability settings.
  • The README replaces the Preview badge with GitHub Releases and Packagist badges, keeps the npm commands unchanged, and points readers to the installation guide for dependency, Vite, and protocol requirements.
  • The README clarifies that authentication is required by default, the example’s public attribute permits guest access, and the public API may change before the first stable release.
  • Contributor standards clarify badge ordering, package-scoped prerelease flags, and installation verification, and favor public Web Awesome Vue controls where they preserve existing wrappers, navigation, and accessibility.
  • Contributor standards require checking every Artisan Toolbox package for confirmed failures or critical runtime defects and recording the result or blocker for each package.

Testing

  • composer test:types now fails if Pest reports less than 100% type coverage or omits any PHP file under src/.
  • Parallel Pest workers isolate configuration publishing and caching; set MAINTAINER_PEST_PARALLEL=false to run tests serially.
  • The npm release build skips the standalone frontend type-only suite, which remains available separately.
  • Distribution checks set Inertia’s form success duration to zero only in the affected test processes, leaving shipped defaults unchanged.

Internal Maintenance

  • The main CI workflow supports manual runs, validates the Git archive before installing dependencies, and separates checks to make failures easier to diagnose.
  • CI retains Ubuntu and Windows coverage with PHP 8.5, Node.js 24, and lowest and stable Composer resolution, now using the project’s declared constraints instead of injecting Laravel and Testbench requirements.
  • Both workflows use the Maintainer 1.14.2 action and disable checkout credential persistence; main and native backend jobs time out after 20 and 10 minutes, respectively, and native backend verification no longer explicitly pins PHP or Composer.
  • The Composer requirement for Maintainer rises to ^1.14.3, with per-task AI model and locale settings and tests.yml configured as the release workflow.
  • The standards manifest and lockfile move to 1.3.0 without changing the schema or skill list.

1.0.0-beta.2 - Synchronize Dapter version with release workflow

Choose a tag to compare

@allanmcarvalho allanmcarvalho released this 18 Nov 22:53

Changed

  • Version synchronization with release workflow: Updated Dapter::VERSION from 1.0.0-beta.1 to 1.0.0-beta.2.
  • Extended versioning lifecycle integration: The Dapter class now participates in the versioning lifecycle by implementing BeforeVersioning (in addition to existing Versionable and WithReadmeHead).
  • Pre-versioning hook executes frontend npm steps: Added a beforeVersioning(string $current, string $next): void hook that:
    • Runs npm version $next --no-git-tag-version --allow-same-version --ignore-scripts from the project root.
    • Then runs npm run release:build.

User-visible impact

  • During versioning/release, the versioning workflow will now automatically trigger the npm commands above to keep the frontend/package version aligned and to rebuild/validate the frontend.

Compatibility and migration

  • Library consumers: No migration required.
  • Maintainers/release operators: Be aware that versioning will execute npm commands; if the npm steps fail, the versioning process may fail as well.

Documentation

  • Aligned README and Boost skill docs with the published beta.1 release line:
    • Updated README references to reflect the move to the beta.1 published behavior/version (including the badge/text and Composer install command).
    • Updated resources/boost/skills/dapter-development/SKILL.md to reference 1.0.0-beta.1, including the stated current version (Dapter::VERSION) and wording around local preview vs. Dapter beta.1.

User-visible impact

  • No runtime/functional changes—documentation consistency only.

Migration

  • None required for users.

1.0.0-beta.1 - Add vector L2 filtering and browser state snapshots

Choose a tag to compare

@allanmcarvalho allanmcarvalho released this 18 Nov 19:10

Added

  • Vector L2 filtering: Introduced support for filtering vectors using an L2-based criterion.
  • Browser state snapshots: Added functionality to capture and store browser state snapshots, enabling state capture for later inspection or restoration.

1.0.0-alpha.1 - Normalize and harden page handling with updated runtime requirements

Choose a tag to compare

@allanmcarvalho allanmcarvalho released this 18 Nov 02:15

Added

  • Preview documentation & contracts (adapter): Added/updated Dapter preview docs, related contracts, and new adapter implementation code to expand the preview surface area and clarify upcoming expectations.
  • AI standards documentation: Introduced an AI standards bundle with related “skills” documentation to formalize repository guidance for agent behavior.
  • Regression coverage: Added tests for query defaults and result counts to guard against regressions in query-building behavior.

Changed

  • Minimum supported dependencies: Bumped the minimum supported Inertia and Vue versions required by the adapter.

Fixed

  • Preserve Eloquent keys for simple-page rows: Normalized simple-page row shape consistently while preserving original Eloquent keys to prevent downstream identity/order/linkage issues after transformation/rehydration.
  • Vite distribution packaging canonicalization: Canonicalized the packed consumer root for Vite distribution handling.
  • Console: preserve non-string name validation/analysis: Updated console validation/analysis to preserve non-string name values rather than implicitly converting/dropping them, improving correctness and diagnostic fidelity.
  • Eloquent paging hardening: Rejected deferred callbacks and sanitized page bounds to prevent inconsistent results and runtime issues from delayed execution paths and invalid pagination parameters.

CI / Internal Maintenance

  • Native backend DB workflow & distribution checks: Added a CI workflow using a native backend database setup and included distribution/package verification checks to improve build/test reliability across expected environments.

Compatibility & Migration

  • Dependency constraints may break older setups: The adapter now requires newer Inertia and Vue versions. If you’re pinned below the new minimums, update your project dependencies before upgrading.
  • No migration required for standard usage:
    • Page handling fixes (normalization, key preservation, bounds sanitation) are intended to correct behavior; normal API usage should remain compatible.
    • If you previously relied on deferred callbacks behavior or passed out-of-range bounds, you’ll need to adjust inputs to match the newly enforced expectations.

Testing

  • Added regression tests covering query defaults and counts to improve confidence in query stability and result accuracy.