[ci] release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

• #1717 335530c Thanks @kerwanp! - Ignore configuration files in published package

• #1717 335530c Thanks @kerwanp! - Create own client type for easier reusability

• Updated dependencies [335530c]:

  • [email protected]

[email protected]

Patch Changes

• #1717 335530c Thanks @kerwanp! - Initial release

• Updated dependencies [335530c, 335530c]:

  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• #1717 335530c Thanks @kerwanp! - Ignore configuration files in published package

[email protected]

Patch Changes

• #1717 335530c Thanks @kerwanp! - Ignore configuration files in published package

[cloudflare-workers-and-pages]

Deploying openapi-ts with    Cloudflare Pages

Latest commit:	f3d2b0e
Status:	✅  Deploy successful!
Preview URL:	https://d0f853bc.openapi-ts.pages.dev
Branch Preview URL:	https://changeset-release-main.openapi-ts.pages.dev

View logs

[kerwanp]

@drwpow need review for release

[drwpow]

@kerwanp Ah so with [ci] release PRs, you have to force merge.

What to loon for:

1. Versions make sense (e.g. you’re publishing a patch version, not a major version
2. Quickly verify that all meaningful changes are accounted for in changelogs (that’s why I ask people to write changesets ad a prereq to mergr, but sometimes things can slip past and it’s helpful to quickly review the PRs merged since the last release

If all that looks good, then we’ll override the merge to deploy. Reason is I just need to fix the permissions. By default bots can’t run GitHub Actions jobs. No job runs, no passing statuses. So we either need to bypass required status checks for this one bot. Or perhaps there’s another way (some PRs have “bot user” accounts set up where it’s an actual login, which can run actions but it’s a headache to set up and maintain).

So all that said, happy to release, and we’ll work to fix the issue so any maintainer can (while still requiring passing status checks)