Once T228352 is actioned I'll test this out on the beta cluster and upload a patch. Also potentialy related: T218110

@ifried tagging Community-Tech on this since you all are working on Page Triage

Change 532833 had a related patch set uploaded (by DannyS712; owner: DannyS712):
[mediawiki/extensions/PageTriage@master] Publish TagCopyvio log entries with pagetriage tag

https://gerrit.wikimedia.org/r/532833

Change 532833 merged by jenkins-bot:
[mediawiki/extensions/PageTriage@master] Publish TagCopyvio log entries with pagetriage tag

https://gerrit.wikimedia.org/r/532833

The changes above bring copyright violation logging in alignment with how we log other PageTriage actions.

One side effect of this is that copyright violation events are logged in Special:RecentChanges. For example, see entry for 28th August here.

In the past, it appears that the code was deliberately changed to prevent this (T204455#4616674). But, I can see no explanation as to why this was done. Perhaps @kostajh (who made the change) can comment.

For what it is worth, I don't see any problems with logging to Special:RecentChanges. Other PageTriage actions are logged there (e.g. when an article is reviewed). The Potential copyright violation log is already publicly viewable.

In the past, it appears that the code was deliberately changed to prevent this (T204455#4616674). But, I can see no explanation as to why this was done. Perhaps @kostajh (who made the change) can comment.

I wish I could remember, and unfortunately I didn't capture that in the commit or in phab. No doubt the reasoning is somewhere in my team's internal chat logs or standup notes.

For what it is worth, I don't see any problems with logging to Special:RecentChanges. Other PageTriage actions are logged there (e.g. when an article is reviewed). The Potential copyright violation log is already publicly viewable.

Yeah based on that, publishing seems correct.