1.0.0-beta.1 - Promote Front Awesome 1.x beta in documentation and align versioning

Changed

• Documentation updated to reflect beta status: The documentation and related metadata were updated to promote Front Awesome 1.x from an “unreleased/source preview” state to an explicit beta.
• Unreleased messaging clarified: Added/updated Unreleased notes explaining that Front Awesome 1.x is now a beta, and instructing consumers to install using the package-scoped beta stability flag. It also reiterates that release version metadata should remain managed by the Maintainer.
• README release badge updated: The GitHub releases badge label was changed from “Release-in development” to a beta-themed badge (e.g., Release-beta-yellow).
• Composer install guidance tightened: Composer installation instructions were updated to require the beta constraint explicitly (e.g., using :^1.0@beta) instead of leaving stability unpinned.
• Pre-stable compatibility expectations: README language now clearly states that the 1.x API may change before the first stable release, setting expectations for potential pre-stable compatibility risk.
• Front Awesome 1.x docs refreshed: The 1.x documentation was revised for beta framing, including updated wording around completeness, updated links (such as a Popover doc link target rename), and terminology adjustments (e.g., Theme → Appearance) while keeping the described replacements aligned.

Changed (Version Alignment)

• Version bump to match the beta release: package.json and FrontAwesome::VERSION were updated from 1.0.0-alpha.2 to 1.0.0-beta.1 so the code-visible version matches the new documented beta.

Testing

• Unit test expectation updated: Test cases validating README head badge URLs were updated to match the new beta badge styling.

Compatibility / Migration Notes

• No automated migrations indicated.
• Users should follow the documented Composer beta constraint to install the intended beta (:^1.0@beta as described) and review the beta notes acknowledging that the 1.x API may still change before a stable release.

1.0.0-alpha.2 - Request-aware preferences and printing localization

Added

• Request-aware preferences & printing localization (breaking)
  • Introduces request-aware preferences so preference resolution can vary based on the current request context.
  • Adds printing localization so printing-related content is localized appropriately.
  • Breaking change: this is marked as feat!, so integrations or any wiring that previously assumed global/static preference or localization behavior may need adjustment.

Changed

• Theme preview API renamed to Appearance
  • Renames the “Theme preview” API to Appearance.
  • Adds WebAwesome wrappers to support standardized usage patterns.
  • Breaking/refactor-risk: developers must update references from the old Theme preview API to the new Appearance naming/contract, and ensure wrapper usage matches the updated expectations.

Fixed

• Frontend browser tests: improved dynamic import + viewport parity reliability

  • Updates the browser test strategy to better handle asynchronous dynamic imports and to ensure viewport parity.
  • User impact: CI/test reliability improvement; reduced flaky timing/viewport-related failures.

• Frontend browser tests: grant clipboard permissions and verify copy behavior

  • Grants Playwright clipboard permissions in the test setup.
  • Strengthens assertions to verify copy-to-clipboard behavior.
  • User impact: more trustworthy verification of copy UI flows; production behavior is not changed.

• Translation exports: validate raw Symfony input

  • Validates raw Symfony input before generating translation export outputs.
  • User impact: more reliable translation export results and fewer localization regressions when input is malformed/unexpected.

• Localization exports: wait for aborted export to finish on close

  • Ensures export shutdown/close waits for the export process to complete cleanly.
  • User impact: prevents partial/locked state and incomplete export artifacts.

• Tooling: align Vite Plus/Vitest and PHPStan Carbon stubs

  • Aligns local stubs so Vite Plus/Vitest and PHPStan Carbon type expectations match.
  • Impact: reduces type-check/tooling drift and CI failures; no runtime behavior changes.

Documentation

• Add documentation adoption audit and verification docs
  • Adds documentation-only guidance for auditing adoption of “public Front Awesome components,” including adoption planning, definition-of-done, constraints to avoid workaround patterns, and a verification approach with explicit adoption levels/evidence boundaries.

Migration / Compatibility Notes

• Breaking: request-aware preferences & printing localization require reviewing how preference resolution and printing/localization are integrated.
• Breaking/refactor: update integrations from the old Theme preview API name to Appearance, and adjust any related integration to use the new WebAwesome wrappers as intended.

1.0.0-alpha.1 - Introduce Tailwind-backed shared theming with Vue/PrimeVue components and toast integration

Added

• Shared Tailwind-backed theming foundation

  • Introduces a new shared theme system backed by Tailwind.
  • Adds a PrimeVue adapter layer to bridge PrimeVue theming with the shared Tailwind-based branding.
  • Provides theme consumers so UI components can consistently pull theme tokens/styles from the shared theme system.

• Vue theme UI components

  • Adds Vue theme-related components that integrate with the shared theme foundation.
  • Adds a button group component to standardize grouped UI actions/controls.

• Laravel + Vue toast integration

  • Adds a toast/notification integration intended for Laravel backends and Vue frontends (“Web Awesome toast integration”).

• Initial Front Awesome Laravel package

  • Initializes the Front Awesome Laravel package, establishing the baseline package structure.

• Documentation for agent/skill frontend design

  • Adds Anthropic frontend design guidance under agents/skills.
  • Adds Vue skill references and Inertia guidance under agents/skills.

Changed

• README badge standardization

  • Standardizes README badges for release status, compatibility, and CI indicators.

• README header management

  • Adds support to manage the README header, including badges and a logo.

Internal Maintenance

• Tooling dependency update
  • Bumps the artisan-toolbox maintainer dependency.

Compatibility / Migration Notes (User-visible)

• Theme adoption changes

  • Existing UI/theme integrations should move toward using the new theme consumer(s) and the PrimeVue adapter approach so styling comes from the shared theme system.
  • Any custom styling that previously bypassed the shared theme may need to be updated to consume the shared theme instead.

• Button grouping

  • Projects with bespoke button-group/theme wrappers may refactor to use the new button group component for consistency.

• Toast integration

  • Consuming apps should wire the new toast integration according to the added integration conventions.
  • If an app already has a toast/notification system configured, adjust to avoid duplicate notification handling.

Documentation

• Added agent/skill frontend guidance for Anthropic and Vue/Inertia to improve consistency of generated frontend output.