The devDependency semantic-release was updated from 15.13.20 to 15.13.21.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This issue contains a list of Renovate updates and their statuses.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to ignore the schedule.

• fix(deps): lock file maintenance

• Check this box to trigger a request for Renovate to run again on this repository

There are already GHE 3.1 and 3.2, but this plugin contains only 3.0.

Please add missing GHE versions.

Note:

I tried to open a PR instead, but failed to do so. The code in this repo is not executable; I've set VERSION to 5.2.2, even removed deprecated versions 220 and 221 from ghe-versions.js, but it is still failing on /app/hook/config for GHE 2.22:

Cannot read property 'deprecationDate' of undefined

at

    deprecationDate: definition["x-github"].deprecationDate,

Is there any trick to run it?

There is new GitHub Enterprise Server 3.x, but no types are generated in this repository.

After #38 was merged the library stopped working with my old code ([email protected], @octokit/[email protected], @octokit/[email protected]). The URLs are not formatted correctly:

DEBUG github: GitHub request: GET https://<github.ee.dns>/api/v3/repos/<org>/<repo> ↴
/pulls//reviews?number=50 - 404 (installation=5)

It results to 404 on half of our requests. Seems that the aliases don't work.

Hey,
I'm using Github Enterprise and my use case is to get metrics using GitHub API. As part of this effort, I've a list of users to go against and fetch the necessary data for reporting and analysis.

I'm trying to get all the Organizations(public & private) each user belongs to and get all repositories within those organizations and get stats for each repository.

I tried using this method: octokit.orgs.listForUser({ username, per_page, page }); which results in only public orgs. Since it is enterprise GitHub server, all orgs are private and I'm unable user organizations.

Can you recommend/suggest if there is a way to fetch this data.

P.S: There seems to be an GitHub endpoint for this ask but this is only for an authenticated user.
https://developer.github.com/enterprise/2.20/v3/orgs/#list-your-organizations

Just double checking that this was intended: a5cb8b5 - since it also added i, I'm wondering it this was a typo npm i npm i or something?

Although the octokit/routes update workflow is triggered, no pull requests are being created, although there have been plenty method name changes.

This is a follow up issue to octokit/plugin-paginate-rest.js#124 (comment)

We need to add @octokit/core as a peerDependency to address a problem with yarn 2. It is something I planned to do anyway, but wanted to figure out automated testing to assure compatibility of the plugins with the latest @octokit/core.

I only want to define compatibility with the lowest version, in this case v3. Compare pull request https://github.com/octokit/plugin-paginate-rest.js/pull/130/files.

I would appreciate help, this is a great issue for a first-time contributor

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

• 🙋 Claim this issue: Comment below.

  More than one person can work on this issue, don't worry if it's already claimed.

• 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

@@ -17,12 +17,12 @@ Besides the admin-specific endpoints, there are differences between `api.github.
 Browsers
 </th><td width=100%>
 
-Load `@octokit/plugin-enterprise-server` and [`@octokit/core`](https://github.com/octokit/core.js) (or core-compatible module) directly from [cdn.pika.dev](https://cdn.pika.dev)
+Load `@octokit/plugin-enterprise-server` and [`@octokit/core`](https://github.com/octokit/core.js) (or core-compatible module) directly from [cdn.skypack.dev](https://cdn.skypack.dev)
 
 ```html
 <script type="module">
-  import { Octokit } from "https://cdn.pika.dev/@octokit/core";
-  import { enterpriseServer220Admin } from "https://cdn.pika.dev/@octokit/plugin-enterprise-server";
+  import { Octokit } from "https://cdn.skypack.dev/@octokit/core";
+  import { enterpriseServer220Admin } from "https://cdn.skypack.dev/@octokit/plugin-enterprise-server";
 </script>
 ```
 

• 💾 Commit your changes

• 🔀 Start a Pull Request. There are two ways how you can start a pull request:

  1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
  2. You can edit files directly in your browser

• 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

Compare https://github.com/octokit/plugin-rest-endpoint-methods.js/blob/a03773361b32f05dea9dc4ba44cf54dc2e9652d7/scripts/update-endpoints/typescript.js

I see that pagination information is coming in the headers but, do we have an API method that was built to easily navigate through pages or get all pages info in one call?

also, any pointers to documentation to understand the API better.?

What happened?

I'm upgrading to newer plugin-enterprise-server.js (from 10.6.4 to 15.1.3) and realized that endpoints that I used and are still part of GitHub ES 3.9 are missing:

• https://docs.github.com/en/[email protected]/rest/actions/self-hosted-runner-groups?apiVersion=2022-11-28#list-self-hosted-runner-groups-for-an-organization
• https://docs.github.com/en/[email protected]/rest/actions/self-hosted-runner-groups?apiVersion=2022-11-28#create-a-self-hosted-runner-group-for-an-organization
• https://docs.github.com/en/[email protected]/rest/actions/self-hosted-runner-groups?apiVersion=2022-11-28#get-a-self-hosted-runner-group-for-an-organization
• https://docs.github.com/en/[email protected]/rest/actions/self-hosted-runner-groups?apiVersion=2022-11-28#update-a-self-hosted-runner-group-for-an-organization
• https://docs.github.com/en/[email protected]/rest/actions/self-hosted-runner-groups?apiVersion=2022-11-28#delete-a-self-hosted-runner-group-from-an-organization
• etc. basically all action runner groups endpoints for organization, I didn't use the ones for enterprise.

Before that I used these without issues.

Versions

"@octokit/plugin-enterprise-server": "^15.1.3",
"probot": "^13.0.0-beta.2",

NodeJS 20.9.0

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

What happened?

I upgraded to latest library version 15.2.1 and realized that some teams endpoints are missing. After some digging I realized there was a PR #625 that removed these from all GHES versions and stated that it was due to deprecation. Now I don't understand why this happened. In @octokit/types the definition still exist and in GH docs for even latest GHES 3.12 there is nothing about deprecation of these APIs.

It is even a buggy update cause the project.deleteCard method points to a method that removes repo from team.

Versions

[email protected]

Relevant log output

TypeError: Failed to add team @<my team slug> to list of repository collaborators in repository `<my repo>`.

Original error: t.teams.addOrUpdateRepoPermissionsInOrg is not a function
    at /home/bot/bot.cjs:525:61736
    at /home/bot/bot.cjs:1:2852064

Code of Conduct

• I agree to follow this project's Code of Conduct

Description

Node v10 has been deprecated so there is no need to keep giving support to it in our CI.

Context

You can find more details here

I see the project is using this dependency in this file which makes me think it should be installed as a dependency instead of a devDependency:

While trying to call get Orgs endpoint as per the documentation, internally it's not forming right url.

This is the URL that being called internally : https://github.companyurl.com/api/v3orgname when I execute the below code. Please advise.

const { Octokit } = require("@octokit/core");
const {
  enterpriseServer219
} = require("@octokit/plugin-enterprise-server");


const OctokitEnterprise = Octokit.plugin(enterpriseServer219);
const octokit = new OctokitEnterprise({
  auth: "secret123",
  baseUrl: "https://github.companyurl.com/api/v3"
});

octokit.orgs.get("orgname").then(function(response){
 console.log(response)
}, (error) => {
  console.log(error);
});

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Configuration option 'packageRules[0].npm' should be a json object, Invalid configuration option: @pika/pack, Invalid configuration option: author, Invalid configuration option: jest, Invalid configuration option: keywords, Invalid configuration option: license, Invalid configuration option: name, Invalid configuration option: packageRules[0].@octokit/types, Invalid configuration option: packageRules[0].i, Invalid configuration option: packageRules[1].@octokit/core, Invalid configuration option: packageRules[2].@octokit/core, Invalid configuration option: packageRules[2].@octokit/graphql, Invalid configuration option: packageRules[2].@pika/pack, Invalid configuration option: packageRules[2].@pika/plugin-build-node, Invalid configuration option: packageRules[2].@pika/plugin-build-web, Invalid configuration option: packageRules[2].@pika/plugin-ts-standard-pkg, Invalid configuration option: packageRules[2].@types/fetch-mock, Invalid configuration option: packageRules[2].@types/jest, Invalid configuration option: packageRules[2].@types/node, Invalid configuration option: packageRules[2].fetch-mock, Invalid configuration option: packageRules[2].jest, Invalid configuration option: packageRules[2].npm-run-all, Invalid configuration option: packageRules[2].prettier, Invalid configuration option: packageRules[2].semantic-release, Invalid configuration option: packageRules[2].semantic-release-plugin-update-version-in-files, Invalid configuration option: packageRules[2].sort-keys, Invalid configuration option: packageRules[2].ts-jest, Invalid configuration option: packageRules[2].typescript, Invalid configuration option: publishConfig, Invalid configuration option: release, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: version, The "npm" object can only be configured at the top level of a config but was found inside "packageRules[0]"

🚨 The automated release from the master 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 master 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.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://x-access-token:[secure]@github.com/octokit/plugin-enterprise-server.js.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀