Unlike nearly every content entity in core path_alias entities don't store any information about their latest change. That's an issue for all contrib content synchronization modules like default_content_deploy → .
Let PathAlias implement the EntityChangedInterface and add a "changed" base field.
Upgrade path
Upgrade tests
Subsystem review
Code review
No UI changes.
PathAlias implements the EntityChangedInterface.
PathAlias has a "changed" base field.
Needs work
10.1 ✨
It denotes an issue that prevents porting of a contributed project to the stable version of Drupal due to missing APIs, regressions, and so on.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
Moving to NW for the tags in #9, which I agree will need an upgrade path.
Tagging for subsystem review also just in case.