@sebastian-berlin-wmse and @Vesihiisi have tested it and it works, but in the case of media upload this has the bad side effect of uploading the file twice if the first upload fails because of a bad tag. It would be more efficient if we could avoid this double upload. Note that this would only happen for the first upload in a batch, because OpenRefine keeps using the latest tag that worked afterwards.

One approach would be to upload without tags and then apply the tags manually. Perhaps that would be a better architecture, although it might also have downsides:

• the edit isn't tagged immediately, meaning that it might get consumed in this untagged state by eager consumers (recent changes pollers, or Wikimedia event stream listeners…)
• in general, that would add one HTTP request to each edit made

Also Wikidata-Toolkit doesn't have a wrapper for applying tags to an edit so we'd need to make the request ourselves (but that wouldn't be the first time).

At least we should update the manifests so that new users get the right (unversioned) tag.

Actually, the openrefine-${version} tag we were using so far doesn't seem to be hard-coded in the manifests, so we should be able to let users upgrade seamlessly to the new tag. This should solve the double upload problem for Commons and Wikidata.

I'd merge this next week unless there are any concerns.