ci: setup release notifications via https://github.com/apps/openapi-release-notifier

[gr2m]

No description provided.

[gr2m]

@zeke @xuorig this is ready from my side, what's left is

• update description of https://github.com/apps/openapi-release-notifier
• add secrets OPENAPI_RELEASE_NOTIFIER_PRIVATE_KEY, OPENAPI_RELEASE_NOTIFIER_APP_ID

[zeke]

I just added the secrets. Looks good to me! 🐑

[gr2m]

I just realized this won't work unless we add a package.json and package-lock.json to the project.

As a simple workaround, we could replace this with

Suggested change

	- run: npm ci
	- run: npm install @octokit/auth-app @octokit/core @octokit/plugin-paginate-rest

The more elegant solution will be to encapsulate the code from release-notifier into a reusable action itself, something I planned on doing for a long time now anyway, can as well do it now

[gr2m]

@xuorig I greatly simplified the action by using https://github.com/gr2m/release-notifier-action

But this will not work until we add a personal access token with the Create Release step, otherwise the release workflow will not be triggered

rest-api-description/.github/workflows/release.yml

Lines 19 to 28 in eb38dd3

	- name: Create Release
	id: create_release
	uses: actions/create-release@v1
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	with:
	tag_name: ${{ github.ref }}
	release_name: ${{ github.ref }}
	draft: false
	prerelease: false

[gr2m]

@xuorig @imwiss this is becoming a blocker for migrating Octokit to consume the new OpenAPI spec

[imwiss]

@xuorig @imwiss this is becoming a blocker for migrating Octokit to consume the new OpenAPI spec

Thanks @gr2m. We'll look into this on Thursday as tomorrow is a holiday 👍

[xuorig]

@gr2m I'm not sure if i understand this comment: #34 (comment)

Is this PR safe to ship in its current state?

[xuorig]

Chatted with Gregor, this is good to go. Thanks @gr2m !

[xuorig]

Updated the token to a PAT a37684d