The robot @Luke081515Bot uses deprecated API entry points and accounts for roughly half of all the deprecation warning we log.
An example on enwiki: https://en.wikipedia.org/wiki/Special:ApiFeatureUsage?wpagent=User%3ALuke081515Bot&wpstartdate=2019-05-20&wpenddate=2019-05-20
| Feature | Date | Uses |
|---|---|---|
| action=query&prop=revisions&rvcontentformat | 2019-05-20 | 2,728,980 |
| action=query&prop=revisions&!rvslots | 2019-05-20 | 2,728,962 |
According to the user agent being received, that would be due to Cygnus-Framework V2.1 alpha used by at least those scripts/bots:
| Script | 7 days hits |
|---|---|
| CTT | 28 millions |
| AutoQSDeleteUnwanted | 28 millions |
| Queue | 10 millions |
| AutoQSCheckURV | 1138 |
| SEODetector | 1064 |
| URVAddNew | 22 |
I would guess it is just about updating the Cygnus Framework?
It seems both deprecations are due to mediawiki/core change 07842be379ca3d4d0bc0608c217dd0e8cd7cbe4b T200568 which states in the release notes:
- action=query&prop=revisions now takes a rvslots parameter to indicate the multi-content revision slots for which content should be returned. It also has a new rvprop, 'roles', to indicate which roles have slots. A deprecation warning will be issued if rvprop=content or rvprop=contentmodel are used without rvslots.
- The rvcontentformat parameter to action=query&prop=revisions has been deprecated. Clients should be prepared to deal with the default format for relevant models.
