Dave Verwer

### SPIReadmeProcessor As [mentioned here](https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/issues/857#issuecomment-748882521) the best solution for making this less brittle is to pass down two URLs to the readme processor, but still to do the actual URL...

Apart from also testing the actual posting of tweets, wouldn't a query on `released_at` in `recent_releases` be the same?

Then this is the perfect solution! 🚀

> It doesn't solve or replace this, but I wondered if we could provide a JSON schema for the supported values in the spi YAML file? That's interesting, but I...

A checker page is 👍 with some examples linked to maybe in the docs.

Compatibility is also being negatively affected by our downscaling here: https://swiftpackageindex.com/builds/E9F3E71B-BEEE-40B3-8D53-51401E38EA57

The trick is not to look at the Update Issue error: But the Validate JSON error: I'll re-open this as I'm keeping this as a list of packages to merge...

Hi Laszlo, and thanks for the submission! I'm afraid we don't support packages that *require* 5.7 yet but we will get this merged as soon as we do! I'll leave...

Hello 👋 I was about to log this same bug when I did a search and found this thread. I am in the process of upgrading a project from Parcel...

> @daveverwer That sounds a bit like the situation that #6072 fixed. Can you try the latest nightly (`parcel@nightly`)? > > Also, what do you mean by "save"? Do you...