7.3.0

New Features

• In the conditions, it is now possible to use the list of an attribute of all the commits. This can be done with the condition formatted like this: commits[*].<attribute>, with <attribute> being one of the available attribute of a commit. For example, commits[*].commit_message will return the list of the commit message of all the commits. You can refer to the conditions/#attributes page on the documentation for more information.
• A new endpoint /healthcheck allows checking the status of the application.
• It is now possible to set a minimum merge date on a pull request with the Merge-After header, to place in the body of the desired pull request. Here are the possible formats:
• Year-Month-Day, eg: Merge-After: 2023-04-18
• Year-Month-Day[Timezone], eg: Merge-After: 2023-04-18[Australia/Sydney]
• Year-Month-Day Hours:Minutes, eg: Merge-After: 2023-04-18 18:20
• Year-Month-Day Hours:Minutes[Timezone], eg: Merge-After: 2023-04-18 18:20[Australia/Sydney]

If used with the merge action, the pull request will be merged after the specified date and time have passed. If used with the queue action, the pull request will be queued after the specified date and time have passed.

For the list of available time zones, see IANA format <https://www.iana.org/time-zones>.

• Added a new statistics endpoint that returns the queue_checks_outcome data for every partition and queues of the repository. The endpoint path is /v1/repos/{repository_owner}/{repository_name}/stats/queue_checks_outcome.
• Added a new statistics endpoint that returns the time_to_merge data for every partition and queues of the repository. The endpoint path is /v1/repos/{repository_owner}/{repository_name}/stats/time_to_merge.
• Partition rules have been added that allow Mergify to support mono-repositories. For more information refer to the queue action on our documentation website.
• When doing inplace checks with update_method: rebase in the queue, it is now possible to also specify if you want to autosquash commits or not with the queue action options : autosquash. It is enabled by default, and can be disabled by specifying autosquash: False in the queue rules or queue action options.
• Mergify now allows you to define routing_conditions in the queue_rules configuration. routing_conditions allows you to define and validate the routing of a pull request in a queue before it is queued.

Deprecation Notes

• The deprecated rebase_fallback configuration option has been removed.
• The priority configuration option of the queue action is deprecated and planned for removal. It is now replaced by priority_rules.