Automate new issue creation when new Polkadot release is published

[p5150j]

As a Polkadot is project major dependency we would like to make sure we are keeping our releases inline with the latest version of Polkadot so that our deployments are running the latest version of Polkadot.

Acceptance criteria:

• when a new version/release has been published on polkadot a new issue should be created in this repo
• the new issue should have the title UPGRADE {version number}
• the new issue should have a description containing Upgrade Priority, Host functions, Database Migrations, Runtime Migrations and a link to the polkadot versioned release

Tasks:

• Research how to dispatch workflow in repo A based on a new release in repo B we don't have access to
• Create workflow to record the latest Polkadot Release
• Merge and Test workflow on main
• Adjust cron schedule to once per day
• Create workflow that would create a new GitHub issues once Polkadot release file has been updated
• Update Frequency CI diagram

[demisx]

There is no conventional way to implement this since we don't have write access to the Polkadot repo. So we'd have to go with a workaround. The idea is to poll the latest release tag and when it changes create a new issue in the Frequency repo. I am still researching this topic, but here is a way to retrieve the latest release tag:

$ curl -sL https://api.github.com/repos/paritytech/polkadot/releases/latest | jq -r ".tag_name"
---------
v0.9.37

[demisx]

@p5150j Just wanted to make sure we are only interested in Polkadot full releases and all release candidates can be skipped.

[demisx]

Please note that for Upgrade Priority, Host functions, Database Migrations, Runtime Migrations I am putting links to the Polkadot Release page where that info is available. Please let me know if this is acceptable.

[p5150j]

@p5150j Just wanted to make sure we are only interested in Polkadot full releases and all release candidates can be skipped.

I think thats fine.