xver / php-auth-core

2.0.2 2026-10-02 13:19 UTC

Requires

• php: ^8.5
• symfony/form: ^8.1
• symfony/security-bundle: ^8.1
• symfony/translation: ^8.1
• symfony/uid: ^8.1
• symfony/validator: ^8.1
• xver/php-app-core: ^2.0.0

Requires (Dev)

• phpunit/phpunit: ^13.1
• symfony/console: ^8.1
• symfony/flex: ^2.5
• symfony/framework-bundle: ^8.1
• symfony/http-kernel: ^8.1
• symfony/runtime: ^8.1
• symfony/yaml: ^8.1
• vimeo/psalm: ^6.10

AGPL-3.0-or-later

Published on Packagist.org on 2026-10-02 13:20 UTC

README

Continuous Integration

This project uses GitHub Actions for continuous integration.

The main workflow is .github/workflows/ci-orchestrator.yml, which delegates to reusable workflows in this order:

1. .github/workflows/symfony-recipe-check.yml checks whether Symfony Flex recipes are outdated.
2. .github/workflows/application-quality-assurance.yml runs the application quality checks after the recipe check succeeds.

CI runs on pushes and pull requests targeting main, except for documentation-only changes, license updates, and changes under translations/.

The application quality workflow performs:

• Composer validation
• Dependency installation
• PHPUnit test suite execution with coverage output
• Psalm static analysis

Symfony Recipe Maintenance

.github/workflows/symfony-recipe-maintenance.yml keeps Symfony Flex recipes current. It runs on pushes and pull requests targeting main, on a weekly schedule, and by manual dispatch.

When recipe updates are available, it applies composer recipes:update, commits the changes, and opens or updates the automated/symfony-recipe-updates pull request. If a recipe update fails or creates conflicts, the workflow fails so the update can be resolved manually.