Test targeted releases

[rtyley]

@jonathonherbert & I are trying out the techniques discussed here:

• feature for library authors: testing library updates using Scala Steward to raise draft PRs with specified library updates scala-steward-org/scala-steward#3612

Upcoming steps

• Get a parameterised workflow dispatch working...!
• Write a custom configuration for scala-steward
• See it working
• Permit setting a unique group for the workflow (perhaps derived from a PR name), to namespace PRs generated in this way, so they are not affected by other PRs
• Get Draft working

See also

• https://github.com/scala-steward-org/scala-steward/blob/main/docs/repo-specific-configuration.md

[rtyley]

We got the 1 PR we expected! job

• [TEST - please ignore]: Update redirect-resolver from 0.0.35 to 0.0.44 google-search-indexing-observatory#64

...now I'm going to change the version to 0.45 to get two PRs...

[rtyley]

Couple of points about trying to update two repos there:

• https://github.com/guardian/mobile-apps-api is private, so running the public-repo job didn't even attempt to update it... 🙃

• The old google-search-indexing-observatory PR was automatically closed as 'Superseded' when the new one was opened - sometimes, we might not want this to happen (eg if we have two different preview PRs on Panda, both of which want to try out update PRs on consumer repos...) :
  

  • [TEST - please ignore]: Update redirect-resolver from 0.0.35 to 0.0.45 google-search-indexing-observatory#65
  • https://github.com/scala-steward-org/scala-steward/blob/4ff8908610ea92677a37a8c0fe614e7054435602/modules/core/src/main/scala/org/scalasteward/core/nurture/NurtureAlg.scala#L131-L141