The automated release is failing 🚨

[github-actions]

🚨 The automated release from the 2.x branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 2.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 3.0.0 on branch 2.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=2.4.0 <3.0.0 can be published from branch 2.x.

The following commits are responsible for the invalid release:

• build: resolve merge conflicts from master (6e79bf6)
• docs: description updates (docs: description updates #30) (09bc0de)
• test: method without any parameters (99b0819)
• feat: octokit.actions.listDownloadsForSelfHostedRunnerApplication({ owner, repo }) (8f25a16)
• build: endpoints updated (2e345cd)
• docs(README): octokit.actions.listDownloadsForSelfHostedRunnerApplication({ owner, repo }) (813f0a8)
• ci: debug release workflow (f029625)
• build(package): lock file (74322a6)
• chore(package): update @pika/plugin-ts-standard-pkg to version 0.8.1 (49242bc)
• chore(package): update @pika/plugin-build-web to version 0.8.1 (0da697c)
• chore(package): update @pika/plugin-build-node to version 0.8.1 (ff80617)
• test: rename (96749b9)
• fix: map contexts/users/teams etc parameters to data for branch protection endpoints (d48f560)
• test: octokit.repos.addProtectedBranchRequiredStatusChecksContexts() (12e92c2)
• build: mapToData parameter decoriation (23811aa)
• refactor(types): order change (0b9a480)
• docs(README): remove merge conflict (257a3f9)
• build(update-endpoints): cache update for v27.1.0 (81b336d)
• build: remove console.log (04a0fd4)
• test: remove obsolete test for deprecated endpoint methods (3774640)
• test: stop testing in Node 8 (b18cfb2)
• remainging deprecated endpoint methods removed (aacdecf)
• build(update-endpoints): cache update (a340951)
• build(update-endpoints): ignore deprecated endpoint methods (8489b1c)
• docs(README): remainging deprecated endpoint methods removed (26dd8f1)
• legacy endpoint methods removed (4f6941e)
• build(update-endpoints): cache updated (af286e1)
• build(update-endpoints): ignore legacy endpoints (9cc6811)
• docs(README): legacy endpoint methods removed (92c8917)
• refactor: comment out code for deprecations (until we have them again) (591a4c3)
• test: remove obsolete deprecations tests (6f85e31)
• remove all deprecated methods and parameters (5417f3d)
• docs(README): remove all deprecated methods (85a517f)
• build(update-endpoints): cache update (5ff6b9c)
• build(update-endpoints): ignore all changes before 2020-02-01 (7e2e951)
• build(update-endpoints): add octokit.repos.uploadReleaseAsset() workarounds for types generation (d66ddfb)
• build(update-endpoints): cache updated (7982cb4)
• build(update-endpoints): fetch headers.required (ecb79ea)
• build(update-endpoints): handle special case for octokit.repos.uploadReleaseAsset (4abd16e)
• build: correct defaults and types for octokit.repos.uploadReleaseAsset() (6eb4063)
• test: octokit.repos.uploadReleaseAsset with owner, repo and release_id options (d3bd732)
• build(package): lock file (94f78c1)
• build(package): just v25 (7701bee)
• fix(typescript): remove types for obsolete workarounds (c228877)
• build(update-endpoints): remove workarounds from types generation (58a411d)
• feat(typescript): Actions endpoints (7114403)
• build(update-endpoints): cache updated (6fa3fb8)
• build: automatically generated src/generated/types.ts (262bc54)
• style: prettier (80f1ec0)
• build: temporary generate endpoints.json for octokit/routes v26.18.1 as that was the version the last generated/types.ts was built with / copied from (92f003b)
• refactor: src/generated/rest-endpoint-methods-types.ts -> src/generated/types.ts (fe00904)
• remove .registerEndpoints (51a85da)
• build: generate octokit.repos.uploadReleaseAsset endpoint method (7177356)
• build: octokit.issues.updateLabel({ current_name, name}) is now octokit.issues.updateLabel({ name, new_name}) (834d570)
• build: remove obsolete methods (f2e6c6e)
• docs: remove obsolete octokit.pulls.createFromIssue, octokit.git.listRefs, octokit.repos.getCommitRefSha (b7641eb)
• build(update-endpoints): cache updated (7f0530c)
• build: remove workarounds (72a6f31)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 2.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀