jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-30 12:02:01 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #20477 from github/repo-sync

Browse Source 
repo sync
This commit is contained in:
Octomerger Bot
2022-09-07 20:44:31 -04:00
committed by GitHub
parent ace11713dd 2144d47256
commit 018ed392a4
7 changed files with 186 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

169
content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
View File

@@ -30,7 +30,9 @@ topics:
Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup.
For more detailed information on features, requirements, and advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme).
Major releases and version numbers for {% data variables.product.prodname_enterprise_backup_utilities %} align with feature releases of {% data variables.product.product_name %}. We support the four most recent versions of both products. For more information, see "[{% data variables.product.product_name %} releases](/admin/all-releases)."
For more detailed information on features, requirements, and advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
## Prerequisites
@@ -50,67 +52,174 @@ Physical storage requirements will vary based on Git repository disk usage and e
More resources may be required depending on your usage, such as user activity and selected integrations.
For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %} requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
## Installing {% data variables.product.prodname_enterprise_backup_utilities %}
To install {% data variables.product.prodname_enterprise_backup_utilities %} on your backup host, we recommend cloning the project's Git repository. This approach allows you to fetch new releases directly using Git, and your existing backup configuration file, `backup.config`, will be preserved when installing a new version.
Alternatively, if the host machine can't access the internet, you can download each {% data variables.product.prodname_enterprise_backup_utilities %} release as a compressed archive, then extract and install the contents. For more information, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
Backup snapshots are written to the disk path set by the `GHE_DATA_DIR` data directory variable in your `backup.config` file. Snapshots need to be stored on a filesystem which supports symbolic and hard links.
{% note %}
**Note:** To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a Geo-replication configuration.
**Note:** We recommend ensuring your snapshots are not kept in a subdirectory of the {% data variables.product.prodname_enterprise_backup_utilities %} installation directory, to avoid inadvertently overwriting your data directory when upgrading {% data variables.product.prodname_enterprise_backup_utilities %} versions.
{% endnote %}
1. Download the latest [{% data variables.product.prodname_enterprise_backup_utilities %} release](https://github.com/github/backup-utils/releases) and extract the file with the `tar` command.
```shell
$ tar -xzvf /path/to/github-backup-utils-v<em>MAJOR.MINOR.PATCH</em>.tar.gz
```
2. Copy the included `backup.config-example` file to `backup.config` and open in an editor.
3. Set the `GHE_HOSTNAME` value to your primary {% data variables.product.prodname_ghe_server %} instance's hostname or IP address.
1. To clone the [{% data variables.product.prodname_enterprise_backup_utilities %} project repository](https://github.com/github/backup-utils/) to a local directory on your backup host, run the following command.
```
$ git clone https://github.com/github/backup-utils.git /path/to/target/directory/backup-utils
```
1. To change into the local repository directory, run the following command.
```
cd backup-utils
```
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
1. To copy the included `backup.config-example` file to `backup.config`, run the following command.
```shell
cp backup.config-example backup.config
```
1. To customize your configuration, edit `backup.config` in a text editor.
1. Set the `GHE_HOSTNAME` value to your primary {% data variables.product.prodname_ghe_server %} instance's hostname or IP address.
{% note %}
**Note:** If {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}.
To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a geo-replication configuration.
{% endnote %}
1. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots. We recommend choosing a location on the same filesystem as your backup host, but outside of where you cloned the Git repository in step 1.
1. To grant your backup host access to your instance, open your primary instance's settings page at `http(s)://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)."
1. On your backup host, verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command.
```shell
./bin/ghe-host-check
```
1. To create an initial full backup, run the following command.
```shell
./bin/ghe-backup
```
For more information on advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
## Upgrading {% data variables.product.prodname_enterprise_backup_utilities %}
When upgrading {% data variables.product.prodname_enterprise_backup_utilities %}, you must choose a release that will work with your current version of {% data variables.product.product_name %}. Your installation of {% data variables.product.prodname_enterprise_backup_utilities %} must be at least the same version as {% data variables.product.product_location %}, and cannot be more than two versions ahead. For more information, see [{% data variables.product.prodname_ghe_server %} version requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
You can upgrade {% data variables.product.prodname_enterprise_backup_utilities %} in a Git repository by fetching and checking out the latest changes.
Alternatively, if you don't use a Git repository for your installation, you can extract a new archive into place, or you can change your approach to use a Git repository instead.
### Verifying the installation type
You can verify the installation method for {% data variables.product.prodname_enterprise_backup_utilities %} and determine the best way to upgrade your installation.
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
1. To check if a valid working directory exists inside a Git repository, run the following command.
```
git rev-parse --is-inside-work-tree
```
If the output is `true`, {% data variables.product.prodname_enterprise_backup_utilities %} was installed by cloning the project's Git repository. If the output includes `fatal: not a git repository (or any of the parent directories)`, {% data variables.product.prodname_enterprise_backup_utilities %} was likely installed by extracting a compressed archive file.
If your installation is in a Git repository, you can install the latest version using Git. If the installation is from a compressed archive file, you can either download and extract the latest version, or you can reinstall {% data variables.product.prodname_enterprise_backup_utilities %} using Git to simplify future upgrades.
- [Upgrading an installation in a Git repository](#upgrading-an-installation-in-a-git-repository)
- [Using Git instead of compressed archives for upgrades](#using-git-instead-of-compressed-archives-for-upgrades)
### Upgrading an installation in a Git repository
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
{% note %}
**Note:** If your {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}.
**Note:** We recommend creating a copy of your existing `backup.config` file in a temporary location, like `$HOME/backup.config`, before upgrading {% data variables.product.prodname_enterprise_backup_utilities %}.
{% endnote %}
4. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots.
5. Open your primary instance's settings page at `https://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see [Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/).
6. Verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command.
1. Download the latest project updates by running the `git fetch` command.
```shell
$ bin/ghe-host-check
```
7. To create an initial full backup, run the `ghe-backup` command.
```shell
$ bin/ghe-backup
git fetch
```
For more information on advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme).
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
### Using Git instead of compressed archives for upgrades
If your backup host has internet connectivity and you previously used a compressed archive (`.tar.gz`) to install or upgrade {% data variables.product.prodname_enterprise_backup_utilities %}, we recommend using a Git repository for your installation instead. Upgrading using Git requires less work and preserves your backup configuration.
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
1. To back up your existing {% data variables.product.prodname_enterprise_backup_utilities %} configuration, copy your current `backup.config` file to a safe location, such as your home directory.
```
$ cp backup.config $HOME/backup.config.saved-$(date +%Y%m%d-%H%M%S)
```
1. Change to the local directory on your backup host where you want to install the {% data variables.product.prodname_enterprise_backup_utilities %} Git repository.
1. To clone the [project repository](https://github.com/github/backup-utils/) to the directory on your backup host, run the following command.
```
git clone https://github.com/github/backup-utils.git
```
1. To change into the cloned repository, run the following command.
```
cd backup-utils
```
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
1. To restore your backup configuration from earlier, copy your existing backup configuration file to the local repository directory. Replace the path in the command with the location of the file saved in step 2.
```
$ cp PATH/TO/BACKUP/FROM/STEP/2 backup.config
```
{% note %}
**Note:** You can choose where to restore your backup configuration file to after cloning. For more information about where configuration files can be located, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
{% endnote %}
1. To confirm that the paths to directories or scripts in your backup configuration file are correct, review the file in a text editor.
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
1. Delete your old GitHub Enterprise Server Backup Utilities directory from step 1 (where the compressed archive installation was located).
## Scheduling a backup
You can schedule regular backups on the backup host using the `cron(8)` command or a similar command scheduling service. The configured backup frequency will dictate the worst case recovery point objective (RPO) in your recovery plan. For example, if you have scheduled the backup to run every day at midnight, you could lose up to 24 hours of data in a disaster scenario. We recommend starting with an hourly backup schedule, guaranteeing a worst case maximum of one hour of data loss if the primary site data is destroyed.
If backup attempts overlap, the `ghe-backup` command will abort with an error message, indicating the existence of a simultaneous backup. If this occurs, we recommended decreasing the frequency of your scheduled backups. For more information, see the "Scheduling backups" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#scheduling-backups).
If backup attempts overlap, the `ghe-backup` command will abort with an error message, indicating the existence of a simultaneous backup. If this occurs, we recommended decreasing the frequency of your scheduled backups. For more information, see the "Scheduling backups" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#scheduling-backups) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
## Restoring a backup
In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance.
{% ifversion ghes %}
{% note %}
**Note:** If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance before running the `ghe-restore` command. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
{% endnote %}
{% endif %}
{% note %}
**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind.
For example, if you take a backup from GHES 3.0.x, you can restore it into a GHES 3.2.x instance. But, you cannot restore data from a backup of GHES 2.22.x onto 3.2.x, because that would be three jumps between versions (2.22 > 3.0 > 3.1 > 3.2). You would first need to restore onto a 3.1.x instance, and then upgrade to 3.2.x.
For example, if you take a backup from {% data variables.product.product_name %} 3.0.x, you can restore the backup to a {% data variables.product.product_name %} 3.2.x instance. You cannot restore data from a backup of {% data variables.product.product_name %} 2.22.x to an instance running 3.2.x, because that would be three jumps between versions (2.22 to 3.0 to 3.1 to 3.2). You would first need to restore to an instance running 3.1.x, and then upgrade to 3.2.x.
{% endnote %}
To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command. You should see output similar to this:
To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command.
{% note %}
**Note:** Prior to restoring a backup, ensure:
- Maintenance mode is enabled on the primary instance and all active processes have completed. For more information, see "[Enabling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)."
- Replication is stopped on all replicas in high availability configurations. For more information, see the `ghe-repl-stop` command in "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)."
- If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
{% endnote %}
When running the `ghe-restore` command, you should see output similar to this:
```shell
$ ghe-restore -c 169.154.1.1
@@ -140,5 +249,5 @@ Optionally, to validate the restore, configure an IP exception list to allow acc
{% endnote %}
You can use these additional options with `ghe-restore` command:
- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
- The `-s` flag allows you to select a different backup snapshot.

11
content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
View File

@@ -27,8 +27,15 @@ shortTitle: Upgrading GHES
## Preparing to upgrade
1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
1. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme).
1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
1. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [README.md file](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
{% note %}
**Note:** Your {% data variables.product.prodname_enterprise_backup_utilities %} version needs to be the same version as, or at most two versions ahead of, {% data variables.product.product_location %}. For more information, see "[Upgrading GitHub Enterprise Server Backup Utilities](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance#upgrading-github-enterprise-server-backup-utilities)."
{% endnote %}
1. If {% data variables.product.product_location %} uses ephemeral self-hosted runners for {% data variables.product.prodname_actions %} and you've disabled automatic updates, upgrade your runners to the version of the runner application that your upgraded instance will run.
1. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required.

1
data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md Normal file
View File

@@ -0,0 +1 @@
1. On your backup host, navigate to your {% data variables.product.prodname_enterprise_backup_utilities %} directory, usually `backup-utils`.

11
data/reusables/enterprise_backup_utilities/enterprise-backup-utils-update-repo.md Normal file
View File

@@ -0,0 +1,11 @@
1. To update to the latest project release version, use the `stable` branch by running the `git checkout stable` command.
```shell
git checkout stable
```
Alternatively, to use a specific project version, run the following command, replacing `X.Y.Z` with the desired release version.
```shell
$ git checkout vX.Y.Z
```

10
data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md Normal file
View File

@@ -0,0 +1,10 @@
1. To verify you have successfully upgraded, run the following command.
```shell
./bin/ghe-backup --version
```
1. To verify SSH connectivity between your configured {% data variables.product.prodname_ghe_server %}, run the following command.
```shell
./bin/ghe-host-check
```

12
lib/rest/static/decorated/api.github.com.json
View File

@@ -409371,7 +409371,7 @@
"serverUrl": "https://api.github.com",
"verb": "get",
"requestPath": "/orgs/{org}/packages/{package_type}/{package_name}/versions",
"title": "Get all package versions for a package owned by an organization",
"title": "List package versions for a package owned by an organization",
"category": "packages",
"parameters": [
{
@@ -409623,7 +409623,7 @@
}
],
"previews": [],
"descriptionHTML": "<p>Returns all package versions for a package owned by an organization.</p>\n<p>To use this endpoint, you must authenticate using an access token with the <code>packages:read</code> scope.\nIf <code>package_type</code> is not <code>container</code>, your token must also include the <code>repo</code> scope.</p>",
"descriptionHTML": "<p>Lists package versions for a package owned by an organization.</p>\n<p>To use this endpoint, you must authenticate using an access token with the <code>packages:read</code> scope.\nIf <code>package_type</code> is not <code>container</code>, your token must also include the <code>repo</code> scope.</p>",
"statusCodes": [
{
"httpStatusCode": "200",
@@ -415456,7 +415456,7 @@
"serverUrl": "https://api.github.com",
"verb": "get",
"requestPath": "/user/packages/{package_type}/{package_name}/versions",
"title": "Get all package versions for a package owned by the authenticated user",
"title": "List package versions for a package owned by the authenticated user",
"category": "packages",
"parameters": [
{
@@ -415706,7 +415706,7 @@
}
],
"previews": [],
"descriptionHTML": "<p>Returns all package versions for a package owned by the authenticated user.</p>\n<p>To use this endpoint, you must authenticate using an access token with the <code>packages:read</code> scope.\nIf <code>package_type</code> is not <code>container</code>, your token must also include the <code>repo</code> scope.</p>",
"descriptionHTML": "<p>Lists package versions for a package owned by the authenticated user.</p>\n<p>To use this endpoint, you must authenticate using an access token with the <code>packages:read</code> scope.\nIf <code>package_type</code> is not <code>container</code>, your token must also include the <code>repo</code> scope.</p>",
"statusCodes": [
{
"httpStatusCode": "200",
@@ -421559,7 +421559,7 @@
"serverUrl": "https://api.github.com",
"verb": "get",
"requestPath": "/users/{username}/packages/{package_type}/{package_name}/versions",
"title": "Get all package versions for a package owned by a user",
"title": "List package versions for a package owned by a user",
"category": "packages",
"parameters": [
{
@@ -421796,7 +421796,7 @@
}
],
"previews": [],
"descriptionHTML": "<p>Returns all package versions for a public package owned by a specified user.</p>\n<p>To use this endpoint, you must authenticate using an access token with the <code>packages:read</code> scope.\nIf <code>package_type</code> is not <code>container</code>, your token must also include the <code>repo</code> scope.</p>",
"descriptionHTML": "<p>Lists package versions for a public package owned by a specified user.</p>\n<p>To use this endpoint, you must authenticate using an access token with the <code>packages:read</code> scope.\nIf <code>package_type</code> is not <code>container</code>, your token must also include the <code>repo</code> scope.</p>",
"statusCodes": [
{
"httpStatusCode": "200",

20
lib/rest/static/dereferenced/api.github.com.deref.json
View File

@@ -119449,15 +119449,15 @@
},
"/orgs/{org}/packages/{package_type}/{package_name}/versions": {
"get": {
"summary": "Get all package versions for a package owned by an organization",
"description": "Returns all package versions for a package owned by an organization.\n\nTo use this endpoint, you must authenticate using an access token with the `packages:read` scope.\nIf `package_type` is not `container`, your token must also include the `repo` scope.",
"summary": "List package versions for a package owned by an organization",
"description": "Lists package versions for a package owned by an organization.\n\nTo use this endpoint, you must authenticate using an access token with the `packages:read` scope.\nIf `package_type` is not `container`, your token must also include the `repo` scope.",
"tags": [
"packages"
],
"operationId": "packages/get-all-package-versions-for-package-owned-by-org",
"externalDocs": {
"description": "API method documentation",
"url": "https://docs.github.com/rest/reference/packages#get-all-package-versions-for-a-package-owned-by-an-organization"
"url": "https://docs.github.com/rest/packages#get-all-package-versions-for-a-package-owned-by-an-organization"
},
"parameters": [
{
@@ -557521,15 +557521,15 @@
},
"/user/packages/{package_type}/{package_name}/versions": {
"get": {
"summary": "Get all package versions for a package owned by the authenticated user",
"description": "Returns all package versions for a package owned by the authenticated user.\n\nTo use this endpoint, you must authenticate using an access token with the `packages:read` scope.\nIf `package_type` is not `container`, your token must also include the `repo` scope.",
"summary": "List package versions for a package owned by the authenticated user",
"description": "Lists package versions for a package owned by the authenticated user.\n\nTo use this endpoint, you must authenticate using an access token with the `packages:read` scope.\nIf `package_type` is not `container`, your token must also include the `repo` scope.",
"tags": [
"packages"
],
"operationId": "packages/get-all-package-versions-for-package-owned-by-authenticated-user",
"externalDocs": {
"description": "API method documentation",
"url": "https://docs.github.com/rest/reference/packages#get-all-package-versions-for-a-package-owned-by-the-authenticated-user"
"url": "https://docs.github.com/rest/packages#get-all-package-versions-for-a-package-owned-by-the-authenticated-user"
},
"parameters": [
{
@@ -566243,7 +566243,7 @@
"key": {
"description": "The public SSH key to add to your GitHub account. For more information, see \"[Checking for existing SSH keys](https://docs.github.com/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys).\"",
"type": "string",
"pattern": "^ssh-(rsa|dss|ed25519) |^ecdsa-sha2-nistp(256|384|521) "
"pattern": "^ssh-(rsa|dss|ed25519) |^ecdsa-sha2-nistp(256|384|521) |^(sk-ssh-ed25519|sk-ecdsa-sha2-nistp256)@openssh.com "
}
},
"required": [
@@ -595265,15 +595265,15 @@
},
"/users/{username}/packages/{package_type}/{package_name}/versions": {
"get": {
"summary": "Get all package versions for a package owned by a user",
"description": "Returns all package versions for a public package owned by a specified user.\n\nTo use this endpoint, you must authenticate using an access token with the `packages:read` scope.\nIf `package_type` is not `container`, your token must also include the `repo` scope.",
"summary": "List package versions for a package owned by a user",
"description": "Lists package versions for a public package owned by a specified user.\n\nTo use this endpoint, you must authenticate using an access token with the `packages:read` scope.\nIf `package_type` is not `container`, your token must also include the `repo` scope.",
"tags": [
"packages"
],
"operationId": "packages/get-all-package-versions-for-package-owned-by-user",
"externalDocs": {
"description": "API method documentation",
"url": "https://docs.github.com/rest/reference/packages#get-all-package-versions-for-a-package-owned-by-a-user"
"url": "https://docs.github.com/rest/packages#get-all-package-versions-for-a-package-owned-by-a-user"
},
"parameters": [
{