…eckers)

This PR was merged into the 6.3 branch.

Discussion
----------

[Validator] LuhnValidator code optimization

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Tickets       |
| License       | MIT
| Doc PR        |

Just a minor code optimization. This way it get's a little bit more performance.

Commits
-------

7c99a1f [Validator] LuhnValidator code optimization

This PR was merged into the 6.3 branch.

Discussion
----------

Use xxh128 instead of md5

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | -
| Tickets       | -
| License       | MIT
| Doc PR        | -

`xxh128` is a hash algorithm available in PHP 8.1 that is ~15 times faster than `md5`.

Let's use it where it doesn't change anything functionally to improve the performance.

Commits
-------

d840ec2 Use xxh128 instead of md5

…amesStamp`

…n array in `TransportNamesStamp` (alexandre-daubois)

This PR was merged into the 6.3 branch.

Discussion
----------

[Messenger] Allow passing a string instead of an array in `TransportNamesStamp`

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| Tickets       | _NA_
| License       | MIT
| Doc PR        | Todo

This PR aims to improve a bit the DX when using `TransportNamesStamp` by allowing passing a string as the only argument of the stamp when only one transport is provided by the developer.

Also, I fixed the property name to match getter's name. I did not changed constructor argument's name as I'm afraid it would be a BC if it is used with named arguments 🤔

Commits
-------

ff86922 [Messenger] Allow passing a string instead of an array in `TransportNamesStamp`

…for MessageInterface implementations (fabpot)

This PR was merged into the 6.3 branch.

Discussion
----------

[Notifier] Introduce FromNotificationInterface for MessageInterface implementations

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | yes <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | n/a
| License       | MIT
| Doc PR        |

Make things more consistent and discoverable.

Commits
-------

2ebb181 [Notifier] Introduce FromNotificationInterface

This PR was squashed before being merged into the 6.3 branch.

Discussion
----------

Smsapi - Make "from" optional

Smsapi.com API have option to send "eco" messages, default with drawn phone number instead of "from" name defined in Smsapi.com User Panel.

So, when from is not set in body of request, in default message is send as "eco". My changes make it possible.

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| Tickets       |
| License       | MIT
| Doc PR        |

Commits
-------

8b14052 Smsapi - Make "from" optional

* 6.2:
  Fix merge
  Fix merge
  [FrameworkBundle] Improve error message in MicroKernelTrait when using deprecated configureRoutes(RouteCollectionBuilder) with symfony/routing >= 6.0
  Add warning about Symfony 5.2 changing pcntl_async_signals
  [Tests] Fix static calls and Mock var annotation
  [FrameworkBundle] Fix checkboxes check assertions
  [Notifier][WebProfilerBundle] Ignore messages whose `getNotification` returns `null`
  [HttpClient] Fix over-encoding of URL parts to match browser's behavior
  Fix Psalm job
  Revert "[HttpClient] Add support for "friendsofphp/well-known-implementations""
  [HttpClient] Fix data collector
  [Tests] Migrate tests to static data providers
  [Semaphore] Fix test
  Fix: Split and clean up tests
  Remove unused data provider
  [Form] Check for `RepeatedType` child in `PasswordHasherListener`
  add Sender to the list of bypassed headers

* 6.2:
  fix test
  fix test
  fix tests

* 6.2:
  fix test

* 6.2:
  Fix test

This PR was merged into the 6.3 branch.

Discussion
----------

Add many missing PHPdoc return types

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | yes
| Tickets       | Ref symfony#47551, continues symfony#49342
| License       | MIT
| Doc PR        | -

This PR adds lots of ``@return`` PHPdoc that we missed in the 5.4 branch. These will produce new deprecation warnings, if applications override one of these methods. It will not break backwards compatibility.
Adding these PHPdoc in 6.3 already allow the community to test all these annotations for 6 months in stable version, before committing to adding them as PHP types in 7.0. This way, I hope we patch out any wrong type.

This PR is done using a slightly modified Psalter script, based on Psalm's type inference. See symfony#49348 for the counter PR adding real PHP types to private, final or internal methods.

Commits
-------

e23d8be Add missing PHPdoc return types

…lopin)

This PR was merged into the 6.3 branch.

Discussion
----------

[HtmlSanitizer] Remove experimental status

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Tickets       | -
| License       | MIT
| Doc PR        | -

The HtmlSanitizer component was introduced in May 2022 and the overall API seems stable (I don't anticipate any BC break needed any time soon).

I suggest we remove its experimental status for 6.3. I removed it in the code, I didn't find other places where it could be referenced as experimental but if I forgot some, please let me know :) !

Commits
-------

13114ec [HtmlSanitizer] Remove experimental status

…outerj)

This PR was merged into the 6.3 branch.

Discussion
----------

Add PHP types to private methods and functions

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | yes
| Tickets       | Ref symfony#47551, continues symfony#49342
| License       | MIT
| Doc PR        | -

This PR adds real PHP types to private, internal or final (excluding ``@final``) methods based on Psalm's type inference. Many more return types are missing still, but let's do them in other contributions.

This change can result in BC breaks in multiple ways, so we should carefully review the changes:

* A method may wrongly be considered "safe" by Psalter. If the method is unsafe (e.g. ``@final``, but not yet real `final`), we should instead add a PHPdoc return type (see symfony#49349)
* Psalm may not infer the correct set of return types. If an unexpected type is returned, this will result in a PHP error.

Commits
-------

384c9a6 Add PHP types to private methods and functions

* 6.2:
  Fix some phpdoc
  [ErrorHandler] Do not patch return statements in closures
  [DI] keep `proxy` tag on original definition when decorating

This PR was merged into the 6.3 branch.

Discussion
----------

Add void (PHPdoc) return types

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Tickets       | Ref symfony#47551, continues symfony#49342
| License       | MIT
| Doc PR        | -

This introduces lots of void return types to the codebase, following our policy:

* Adding ``@return` void` to any methods that return void is OK
* Adding `void` PHP return type is only OK if the method is internal, private or final (excluding ``@final``).

The changes in this PR are automated through a modified Psalter script. We should particularly review if ``@final`` classes/methods didn't get real PHP void return types, as this is a BC break.

Commits
-------

508ed81 Add void return types

…ault)

This PR was merged into the 6.3 branch.

Discussion
----------

[Filesystem] Remove always true condition

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exists, explain below instead -->
| License       | MIT
| Doc PR        | symfony/symfony-docs#... <!-- required for new features -->

`$mode` is type hinted `int $mode`, so this condition is always true.

Commits
-------

d2cf15d [Filesystem] Remove always true condition

* 6.2:
  [Tests] Migrate tests to static data providers
  [Cache] Only validate dbindex parameter when applicable

* 6.2:
  Speed up Psalm tests
  [GHA] Improve workflow titles
  [GHA] Improve workflow titles
  Fix fix
  [Notifier] Fix notifier profiler when transport name is null
  [HttpKernel] Fix setting the session on the main request when it's started by a subrequest

…d deprecate httplugs use like psr18 client (simonberger)

This PR was squashed before being merged into the 6.3 branch.

Discussion
----------

[FrameworkBundle] Add scoped httplug clients and deprecate httplugs use like psr18 client

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | yes
| Tickets       | Fix symfony#49644
| License       | MIT
| Doc PR        | symfony/symfony-docs#18064

This MR does 2 closely related things to try to fully integrate the HttplugClient with the unique features it brings and on the other hand deprecate its use like a psr18 client which it is in a pending deprecation state since a long time.

- Added a new services `httplug.http_client` and alias `Http\Client\HttpAsyncClient` to inject the the `HttplugClient`.
- Make the available service `Http\Client\HttpClient` a deprecated alias of it
- Create httplug.<scoped_client_id> services for all scoped clients like it is done with the psr18 ClientInterface

Commits
-------

20ab567 [FrameworkBundle] Add scoped httplug clients and deprecate httplugs use like psr18 client

This PR was merged into the 6.3 branch.

Discussion
----------

[Validator] Add PHPDoc void return types

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Tickets       | contribution to symfony#47551
| License       | MIT
| Doc PR        | -

Add missing void PHPdoc return types for the Validator component

Commits
-------

e70241d [Validator] Add PHPDoc void return types

…olas-grekas)

This PR was merged into the 6.3 branch.

Discussion
----------

[Config] Improve performance of GlobResource

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Tickets       | Fix symfony#49668
| License       | MIT
| Doc PR        | -

When using an extended glob pattern that contains `/**/`, we skip using the native `glob()` function and we fallback to using the Finder component.

For a pattern like `./{apps,src}/**/*Controller.php`, the way finder works in `GlobResource` is that we list all files *recursively* in the directory before the pattern starts (`./` here) and we filter the paths using a regexp.

This PR ensures that we scan only the `apps` and `src` directories when presented with such a pattern.

Commits
-------

1771262 [Config] Improve performance of GlobResource

This PR was merged into the 6.3 branch.

Discussion
----------

[ErrorHandler] Fixed tests

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Tickets       |
| License       | MIT
| Doc PR        |

Commits
-------

bb8b73e [ErrorHandler] Fixed tests

…bpot)

This PR was merged into the 6.3 branch.

Discussion
----------

[Messenger] Add a scheduler component

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| Tickets       | no
| License       | MIT
| Doc PR        | TBD

### Introdution

There is no easy way to schedule periodical tasks. There are few useful tools which I touched:

- https://github.com/Guikingone/SchedulerBundle
- https://github.com/Cron/Symfony-Bundle
- https://github.com/zenstruck/schedule-bundle
- https://github.com/lavary/crunz

They are complicated. They doesn't allow to set time with precision in seconds (at least it isn't easy). They require difficult tricks to set not linear periods (like on sunset in Tokyo). ~They are~ Part of them inefficient with infrequent tasks because resources are needed on every run (e.g. Kubernetes [CronJob](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/) creates and destroes an entire container).

### Proposal

I use a custom transport of Messenger that **generates** messages periodically. It's a simple solution to run periodical jobs without external software. It's especially helpful in environments where additional runners are impossible or very painful (like Kubernetes). Configuration is very flexible and accurate, it's possible to configure any rules when to run or not to run.

Compared to `crond`: there is no need to install something external, precision of schedule in microseconds instead of *minutes*, it's possible to set any periods.

#### Simple example

```yaml
# messenger.yaml
framework:
  messenger:
    transports:
      schedule_default: 'schedule://default'
```

Few types of messages:
```php
class SomeJob {}
class OtherJob {}
```

A handlers:
```php
#[AsMessageHandler]
class SomeJobHandler {
    public function __invoke(SomeJob $job) {
        // do job or delegate it to other service
    }
}

#[AsMessageHandler]
class OtherJobHandler {
    public function __invoke(OtherJob $job) {
        // do job or delegate it to other service
    }
}
```

A schedules are provided by locators. It's possible to create many locators and/or provide many schedules by the same locator:

```php
class ExampleLocator implements ScheduleLocatorInterface
{
    public function get(string $id): ScheduleConfig
    {
        // once after an hour from now
        $deferForAnHour = new \DatePeriod(
            new \DateTimeImmutable('now'),
            new \DateInterval('PT1H'),
            1,
            \DatePeriod::EXCLUDE_START_DATE
        );

        return (new ScheduleConfig())
            ->add(new OnceTrigger(new \DateTimeImmutable()), new WarmUpJob()) // once on every worker's start
            ->add(PeriodicalTrigger::create('P1D', '2022-01-01T03:00:00Z'), new SomeJob()) // every night at 3 a.m. (UTC)
            ->add(PeriodicalTrigger::fromPeriod($deferForAnHour), new OtherJob())
        ;
    }

    public function has(string $id): bool
    {
        return 'default' === $id;
    }
}
```

To run schedule:

```sh
bin/console messenger:consume schedule_default
```

It's easy to run jobs manually:

```php
#[AsCommand(name: 'some', description: 'Manually runs SomeJob')]
class SomeCommand extends Command {
    public function __construct(private MessageBusInterface $bus) {
    }

    protected function execute(InputInterface $input, OutputInterface $output): int {
        $this->bus->dispatch(new SomeJob());
    }
}
```

#### Example with returning a result

```php
class GoodJob {
    public function __construct(public readonly ?LoggerInterface $logger) {
    }
}
```

```php
#[AsMessageHandler]
class GoodHandler {
    public function __construct(private readonly LoggerInterface $logger) {
    }

    public function __invoke(GoodJob $job){
        // compute $result
        ($job->logger ?? $this->logger)->info('The result is: {result}', ['result' => $result])
    }
}
```

```php
#[AsCommand(name: 'job', description: 'Manually runs job')]
class SomeCommand extends Command {
    public function __construct(private MessageBusInterface $bus) {
    }

    protected function execute(InputInterface $input, OutputInterface $output): int {
        $this->bus->dispatch(new GoodJob(new ConsoleLogger($output))); // result will be printed in console
    }
}
```

#### Configuring

A minimal configuration:

```yaml
# messenger.yaml
framework:
  messenger:
    transports:
      schedule_default: 'schedule://default'
```

More complex example:

```yaml
# messenger.yaml
framework:
  messenger:
    transports:
      schedule_default:
        dsn: 'schedule://default'
        options:
          cache: 'app.cache'
          lock: 'default'
```

Example HA configuration with redis:

```yaml
framework:
  cache:
    default_redis_provider: '%env(REDIS_DSN)%'
  lock:
    redis: '%env(REDIS_DSN)%'
  messenger:
    transports:
      schedule_default:
        dsn: 'schedule://default'
        options:
          cache: 'cache.redis'
          lock:
            resource: 'redis'
            ttl: 60
            auto_release: true
```

### Deprecations

None

### Implementation

This PR contains an implementation.

### ToDo

- [x] Remove obsolete code
- [x] Add a configuration to the Framework
- [x] Specialize exceptions and improve messages
- [x] Cover with tests
- [ ] Add acceptance tests for HA
- [x] Fix `CHANGELOG`s & `README`s
- [ ] Add documentation

Commits
-------

a18127b [Scheduler] Rework the component
6d9311f Add the Scheduler component

* 6.2:
  explicitly set the HTTP method override option to false

…MessengerPass (onEXHovia)

This PR was merged into the 6.3 branch.

Discussion
----------

[Scheduler] Remove unused variable in AddScheduleMessengerPass

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | n/a
| License       | MIT
| Doc PR        | n/a

Commits
-------

09df772 [Scheduler] Remove unused variable in AddScheduleMessengerPass

…shover bridge (vlepeule)

This PR was squashed before being merged into the 6.3 branch.

Discussion
----------

[Notifier] Add "retry" and "expire" options to Pushover bridge

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | -
| License       | MIT
| Doc PR        | -

Add "retry" and "expire" options to handle "Emergency Priority", according to  [Pushover API documentation](https://pushover.net/api#priority) :

> To send an emergency-priority notification, the priority parameter must be set to 2 and the retry and expire parameters must be supplied.

Commits
-------

2feabc6 [Notifier] Add "retry" and "expire" options to Pushover bridge

This PR was merged into the 6.3 branch.

Discussion
----------

[Scheduler] Fix some minor bugs

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | yes
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | n/a
| License       | MIT
| Doc PR        | n/a

Commits
-------

9fc7cf5 [Scheduler] Fix some minor bugs

…rializer.html.twig (k0d3r1s)

This PR was merged into the 6.3 branch.

Discussion
----------

[WebProfilerBundle] replace helper with _self in serializer.html.twig

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | Fix symfony#49686
| License       | MIT

While waiting for reply, here is a fix for bug in symfony#49686.
As`helper` was removed, now `_self` must be used, these looks like forgotten places

Commits
-------

b27aab9 [WebProfilerBundle] replace helper with _self in serializer.html.twig

…nMemoryTransport (fabpot)

This PR was merged into the 6.3 branch.

Discussion
----------

[Messenger] Add support for the DelayStamp in InMemoryTransport

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | yes <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | n/a
| License       | MIT
| Doc PR        | n/a

Commits
-------

1025f35 [Messenger] Add support for the DelayStamp in InMemoryTransport

…ed standalone

…en the component is used standalone (fabpot)

This PR was merged into the 6.3 branch.

Discussion
----------

[Scheduler] Add a simple Scheduler class for when the component is used standalone

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | no
| New feature?  | yes <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | n/a
| License       | MIT
| Doc PR        | -

```
$handler = new SomeHandler();
$scheduler = new Scheduler([SomeJob::class => new SomeHandler()], [$someProvider->getSchedule(), $anotherSchedule]);
$scheduler->run();
```

Commits
-------

0f5422c [Scheduler] Add a simple Scheduler class for when the component is used standalone

… component (fabpot)

This PR was squashed before being merged into the 6.3 branch.

Discussion
----------

[FrameworkBundle] Fix registration of the Scheduler component

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | yes
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | n/a
| License       | MIT
| Doc PR        | n/a

Commits
-------

251ed12 [Scheduler] Fix usage without a Lock
313644f [FrameworkBundle] Fix registration of the Scheduler component