зеркало из https://github.com/github/docs.git
Merge branch 'main' into patch-1
This commit is contained in:
Janice
GitHub
Коммит
e5af5eb553
|
|
@ -0,0 +1,129 @@
|
|||
intro: GitHub is excited to present GitHub Enterprise Server 2.22.0.
|
||||
date: '2020-09-23'
|
||||
sections:
|
||||
features:
|
||||
- heading: GitHub Actions Beta
|
||||
notes:
|
||||
- |
|
||||
[GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out.
|
||||
|
||||
You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %}
|
||||
|
||||
- heading: GitHub Packages Beta
|
||||
notes:
|
||||
- |
|
||||
[GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions.
|
||||
|
||||
Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %}
|
||||
|
||||
- heading: Advanced Security Code Scanning Beta
|
||||
notes:
|
||||
- |
|
||||
[GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL.
|
||||
|
||||
Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %}
|
||||
|
||||
- heading: Pull Request Retargeting
|
||||
notes:
|
||||
- |
|
||||
When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %}
|
||||
|
||||
- heading: Suspend and Unsuspend an App Installation
|
||||
notes:
|
||||
- |
|
||||
Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}''
|
||||
|
||||
- heading: Improved Large Scale Performance
|
||||
notes:
|
||||
- |
|
||||
We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github.com/github/git-protocols/issues/94 {% endcomment %}''
|
||||
|
||||
Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %}
|
||||
|
||||
- heading: View All of Your Users
|
||||
notes:
|
||||
- |
|
||||
For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}''
|
||||
|
||||
changes:
|
||||
- heading: Administration Changes
|
||||
notes:
|
||||
- Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %}
|
||||
- The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %}
|
||||
- It's now possible to [manage global announcements and expiration dates through the enterprise account settings](https://docs.github.com/en/enterprise/2.22/admin/installation/command-line-utilities#ghe-announce). {% comment %} https://github.com/github/releases/issues/945, https://github.com/github/github/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %}
|
||||
- You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %}
|
||||
- Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %}
|
||||
- A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% comment %} https://github.com/github/releases/issues/946, https://github.com/github/github/pull/150595, https://github.com/github/github/pull/150520, https://github.com/github/github/pull/151121, https://github.com/github/hydro-schemas/pull/1244 {% endcomment %}
|
||||
- The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %}
|
||||
- The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %}
|
||||
- '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% comment %} https://github.com/github/github/pull/140433, https://github.com/github/help-docs/pull/14853, https://github.com/github/customer-feedback/issues/174, https://github.com/github/supportability/issues/14 {% endcomment %}'
|
||||
|
||||
- heading: Security Changes
|
||||
notes:
|
||||
- Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %}
|
||||
- When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility). {% comment %} https://github.com/github/releases/issues/872 {% endcomment %}
|
||||
- Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %}
|
||||
|
||||
- heading: Developer Changes
|
||||
notes:
|
||||
- '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}'
|
||||
- In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %}
|
||||
- Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}
|
||||
- Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %}
|
||||
- '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}'
|
||||
|
||||
- heading: Users and organizations can add Twitter usernames to their GitHub profiles
|
||||
notes:
|
||||
- '[Developers and organizations can now add their Twitter username to their profile](https://github.blog/changelog/2020-07-22-users-and-organizations-can-now-add-twitter-usernames-to-their-github-profiles/) {% comment %} https://github.com/github/github/pull/145127 {% endcomment %}'
|
||||
|
||||
- heading: API Changes
|
||||
notes:
|
||||
- |
|
||||
#### Graduated Previews
|
||||
|
||||
The following previews are now an official part of the API:
|
||||
* The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %}
|
||||
* To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %}
|
||||
|
||||
- |
|
||||
#### GraphQL Schema Changes
|
||||
|
||||
* [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes.
|
||||
|
||||
bugs:
|
||||
- The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %}
|
||||
- The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %}
|
||||
- A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %}
|
||||
- If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %}
|
||||
- Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %}
|
||||
|
||||
deprecations:
|
||||
- heading: Upcoming Deprecation of GitHub Enterprise Server 2.19
|
||||
notes:
|
||||
- '**GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020** That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.'
|
||||
- heading: Deprecation of Legacy GitHub App Webhook Events
|
||||
notes:
|
||||
- Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}
|
||||
- heading: Deprecation of Legacy GitHub Apps Endpoint
|
||||
notes:
|
||||
- Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}
|
||||
- heading: Deprecation of OAuth Application API
|
||||
notes:
|
||||
- GitHub [no longer supports the OAuth application endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/) and have replaced them with a version that moves the access token to the request body for improved security. Brownouts will start in March 2021 and all calls to the old version of the OAuth application endpoints will return a status code of 404 starting on May 5, 2021 at 16:00 UTC.
|
||||
|
||||
# - type: Backup and Disaster recovery
|
||||
# note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/).
|
||||
|
||||
known_issues:
|
||||
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}
|
||||
- Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}
|
||||
- The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %}
|
||||
- The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %}
|
||||
- Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %}
|
||||
- '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a GitHub App](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app). {% comment %} https://github.com/github/enterprise2/issues/22849 {% endcomment %}'
|
||||
- GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %}
|
||||
- On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}
|
||||
- Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}
|
||||
|
|
@ -0,0 +1,73 @@
|
|||
date: '2020-10-09'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}'
|
||||
- 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}'
|
||||
- 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}'
|
||||
- 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}'
|
||||
|
||||
bugs:
|
||||
- |
|
||||
The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}
|
||||
- |
|
||||
Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %}
|
||||
- |
|
||||
Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %}
|
||||
- |
|
||||
System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %}
|
||||
- |
|
||||
The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %}
|
||||
- |
|
||||
`ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %}
|
||||
- |
|
||||
Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %}
|
||||
- |
|
||||
Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %}
|
||||
- |
|
||||
Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %}
|
||||
- |
|
||||
When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %}
|
||||
- |
|
||||
The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %}
|
||||
- |
|
||||
OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %}
|
||||
- |
|
||||
Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %}
|
||||
- |
|
||||
On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %}
|
||||
- |
|
||||
When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %}
|
||||
- |
|
||||
When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %}
|
||||
- |
|
||||
Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %}
|
||||
- |
|
||||
Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %}
|
||||
- |
|
||||
The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %}
|
||||
- |
|
||||
Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %}
|
||||
- |
|
||||
A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %}
|
||||
- |
|
||||
When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %}
|
||||
- |
|
||||
[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %}
|
||||
- |
|
||||
GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management Console. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %}
|
||||
|
||||
changes:
|
||||
- Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %}
|
||||
- Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %}
|
||||
- GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}
|
||||
|
||||
known_issues:
|
||||
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}
|
||||
- Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}
|
||||
- Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %}
|
||||
- GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}
|
||||
- On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}
|
||||
- Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}
|
||||
|
|
@ -0,0 +1,30 @@
|
|||
date: '2020-10-20'
|
||||
sections:
|
||||
security_fixes:
|
||||
- Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %}
|
||||
|
||||
bugs:
|
||||
- |
|
||||
If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %}
|
||||
- |
|
||||
A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %}
|
||||
- |
|
||||
On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %}
|
||||
- |
|
||||
When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %}
|
||||
- |
|
||||
Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %}
|
||||
- |
|
||||
The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %}
|
||||
- |
|
||||
On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %}
|
||||
|
||||
known_issues:
|
||||
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}
|
||||
- Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}
|
||||
- GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}
|
||||
- On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}
|
||||
- Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}
|
||||
|
|
@ -0,0 +1,24 @@
|
|||
date: '2020-11-03'
|
||||
sections:
|
||||
security_fixes:
|
||||
- |
|
||||
**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %}
|
||||
- |
|
||||
**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %}
|
||||
- |
|
||||
Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23540, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23693, https://github.com/github/enterprise2/pull/23677 {% endcomment %}
|
||||
|
||||
bugs:
|
||||
- GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %}
|
||||
- Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %}
|
||||
- On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %}
|
||||
- Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %}
|
||||
- A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}
|
||||
|
||||
known_issues:
|
||||
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}
|
||||
- Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}
|
||||
- Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
date: '2020-11-17'
|
||||
sections:
|
||||
security_fixes:
|
||||
- Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %}
|
||||
|
||||
bugs:
|
||||
- The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %}
|
||||
- After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %}
|
||||
- When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %}
|
||||
- Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %}
|
||||
|
||||
known_issues:
|
||||
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}
|
||||
- Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}
|
||||
|
|
@ -1,12 +1,25 @@
|
|||
{% assign sectionTitle = section.title | default: 'Misc' %}
|
||||
|
||||
{% case sectionTitle %}
|
||||
{% when "New Feature" %}
|
||||
{% assign colors = "bg-orange text-white" %}
|
||||
{% when "Bugs" %}
|
||||
{% assign colors = "bg-purple text-white" %}
|
||||
{% case section[0] %}
|
||||
{% when "features" %}
|
||||
{% assign colors = "bg-gradient-aquamarine-mauve text-white" %}
|
||||
{% assign text = "Features" %}
|
||||
{% when "bugs" %}
|
||||
{% assign colors = "bg-gradient-red-orange text-white" %}
|
||||
{% assign text = "Bug fixes" %}
|
||||
{% when "known_issues" %}
|
||||
{% assign colors = "bg-gradient-dark-mint text-white" %}
|
||||
{% assign text = "Known issues" %}
|
||||
{% when "security_fixes" %}
|
||||
{% assign colors = "bg-gradient-coral-yellow text-white" %}
|
||||
{% assign text = "Security fixes" %}
|
||||
{% when "changes" %}
|
||||
{% assign colors = "bg-gradient-blue-purple text-white" %}
|
||||
{% assign text = "Changes" %}
|
||||
{% when "deprecations" %}
|
||||
{% assign colors = "bg-gradient-mint-blue text-white" %}
|
||||
{% assign text = "Deprecations" %}
|
||||
{% else %}
|
||||
{% assign colors = "bg-blue text-white" %}
|
||||
{% assign text = "INVALID SECTION" %}
|
||||
{% endcase %}
|
||||
|
||||
<span class="{{ colors }} px-3 py-2 f5 text-uppercase text-mono">{{ sectionTitle }}</span>
|
||||
<span class="{{ colors }} px-3 py-2 f5 text-uppercase text-mono">{{ text }}</span>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,18 @@
|
|||
{% case section[0] %}
|
||||
{% when "features" %}
|
||||
{% assign colors = "text-gradient-aquamarine-mauve" %}
|
||||
{% when "bugs" %}
|
||||
{% assign colors = "text-gradient-red-orange" %}
|
||||
{% when "known_issues" %}
|
||||
{% assign colors = "text-gradient-dark-mint" %}
|
||||
{% when "security_fixes" %}
|
||||
{% assign colors = "text-gradient-coral-yellow-dark" %}
|
||||
{% when "changes" %}
|
||||
{% assign colors = "text-gradient-blue-purple" %}
|
||||
{% when "deprecations" %}
|
||||
{% assign colors = "text-gradient-dark-mint" %}
|
||||
{% else %}
|
||||
{% assign colors = "text-gradient-aquamarine-mauve" %}
|
||||
{% endcase %}
|
||||
|
||||
<h4 class="{{ colors }} text-uppercase text-bold">{{ note.heading }}</h4>
|
||||
|
|
@ -11,83 +11,133 @@
|
|||
{% include header %}
|
||||
{% include deprecation-banner %}
|
||||
|
||||
<div class="container-xl px-3 px-md-6 my-4 my-lg-4 markdown-body">
|
||||
<div class="d-lg-flex flex-justify-between">
|
||||
<div class="d-block d-lg-none">{% include article-version-switcher %}</div>
|
||||
<div class="d-flex flex-items-center" style="height: 39px;">
|
||||
{% include breadcrumbs %}
|
||||
<div class="d-flex flex-items-stretch">
|
||||
<article class="flex-auto">
|
||||
<div class="d-flex flex-items-center flex-justify-between bg-white text-bold py-4 px-5">
|
||||
{% if prevRelease %}
|
||||
<a
|
||||
class="btn btn-outline"
|
||||
href="/{{ currentLanguage }}/{{ allVersions[currentVersion].plan }}@{{ prevRelease }}/{{ currentProduct }}/release-notes">
|
||||
{% octicon "chevron-left" %} {{ prevRelease }}
|
||||
</a>
|
||||
{% else %}
|
||||
<div></div>
|
||||
{% endif %}
|
||||
|
||||
<h1 class="f4 p-0 m-0">{{ currentVersion | version_num }} Release notes</h1>
|
||||
|
||||
{% if nextRelease %}
|
||||
<a
|
||||
class="btn btn-outline"
|
||||
href="/{{ currentLanguage }}/{{ allVersions[currentVersion].plan }}@{{ nextRelease }}/{{ currentProduct }}/release-notes">
|
||||
{{ nextRelease }} {% octicon "chevron-right" %}
|
||||
</a>
|
||||
{% else %}
|
||||
<div></div>
|
||||
{% endif %}
|
||||
</div>
|
||||
<div class="d-none d-lg-block">{% include article-version-switcher %}</div>
|
||||
</div>
|
||||
|
||||
<article class="mt-2 d-flex gutter">
|
||||
<div class="col-12 col-md-10">
|
||||
<header>
|
||||
<h1>{{ allVersions[currentVersion].versionTitle }}</h1>
|
||||
</header>
|
||||
|
||||
<div class="markdown-body">
|
||||
{% for patch in releaseNotes %}
|
||||
<details id="{{ patch.version }}" class="details-reset mb-3" {% if forloop.first %}open{% endif %}>
|
||||
<summary class="position-sticky top-0 bg-white pb-2 d-flex flex-items-center flex-justify-between border-bottom">
|
||||
<h2 class="d-flex flex-items-center border-bottom-0">
|
||||
{{ patch.version }}
|
||||
<div id="{{ patch.version }}" class="mb-10 bg-gray-light px-3 py-6 border-bottom border-top">
|
||||
<header class="container-xl position-sticky top-0 bg-gray-light border-bottom pb-2">
|
||||
<div class="d-flex flex-items-baseline">
|
||||
<h2 class="d-flex flex-items-center border-bottom-0 mr-3 mb-0">
|
||||
{{ allVersions[currentVersion].versionTitle }}.{{ patch.patchVersion }}
|
||||
|
||||
{% if patch.release_candidate %}
|
||||
<span class="IssueLabel bg-orange text-white mx-2">Release Candidate</span>
|
||||
{% endif %}
|
||||
</h2>
|
||||
{% if patch.release_candidate %}
|
||||
<span class="IssueLabel bg-orange text-white mx-2">Release Candidate</span>
|
||||
{% endif %}
|
||||
</h2>
|
||||
|
||||
<div>
|
||||
<span class="text-gray-light text-mono text-small" style="margin-left: auto">{{ patch.date | date: "%B %d, %Y" }}</span>
|
||||
<a href="https://enterprise.github.com/releases/{{ patch.version }}/download" class="f5">
|
||||
Download
|
||||
</a>
|
||||
|
||||
<div class="mt-1 d-flex flex-items-center f5">
|
||||
<a href="https://enterprise.github.com/releases/{{ patch.version }}/download">
|
||||
Download GHES {{ patch.version }}
|
||||
</a>
|
||||
|
||||
<button class="js-print btn-link ml-6">
|
||||
Print
|
||||
</button>
|
||||
</div>
|
||||
<button class="js-print btn-link ml-3 f5">
|
||||
Print
|
||||
</button>
|
||||
</div>
|
||||
</summary>
|
||||
|
||||
<p>{{ patch.intro }}</p>
|
||||
<p class="text-gray mt-1">{{ patch.date | date: "%B %d, %Y" }}</p>
|
||||
</header>
|
||||
|
||||
{% for section in patch.sortedNotes %}
|
||||
<div class="py-6 border-bottom d-block d-md-flex flex-items-baseline">
|
||||
<div class="mr-2 flex-shrink-0 mb-3">
|
||||
{% include 'release-notes-category-label' %}
|
||||
</div>
|
||||
<div class="container-xl">
|
||||
<p class="mt-3">{{ patch.intro }}</p>
|
||||
|
||||
<ul class="flex-auto container-xl">
|
||||
{% for note in section.notes %}
|
||||
{% if note.note and note.note != '<p>n/a</p>' %}
|
||||
<li>
|
||||
{{ note.note }}
|
||||
{% for section in patch.sections %}
|
||||
<div class="py-6 d-block d-xl-flex flex-items-baseline {% unless forloop.last %}border-bottom{% endunless %}">
|
||||
<div class="mr-2 flex-shrink-0 mb-5 col-12 col-xl-3">
|
||||
{% include 'release-notes-category-label' %}
|
||||
</div>
|
||||
|
||||
<ul class="flex-auto pl-3 pl-xl-0 release-notes-list">
|
||||
{% for note in section[1] %}
|
||||
<li class="release-notes-list-item {% if note.heading %}list-style-none{% endif %}">
|
||||
{% if note.heading %}
|
||||
{% include 'release-notes-heading' %}
|
||||
<ul class="pl-3 pb-4 mt-2 release-notes-list">
|
||||
{% for subNote in note.notes %}
|
||||
<li class="release-notes-list-item">{{ subNote }}</li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
{% else %}
|
||||
{{ note }}
|
||||
{% endif %}
|
||||
</li>
|
||||
{% endif %}
|
||||
{% endfor %}
|
||||
</ul>
|
||||
</div>
|
||||
{% endfor %}
|
||||
</details>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
</div>
|
||||
{% endfor %}
|
||||
</div>
|
||||
</div>
|
||||
{% endfor %}
|
||||
</div>
|
||||
</article>
|
||||
|
||||
<aside class="col-2 d-none d-md-block no-print">
|
||||
<h3 class="f5">Patch versions</h3>
|
||||
<ul>
|
||||
{% for patch in releaseNotes %}
|
||||
<li><a href="#{{ patch.version }}">{{ patch.version }}</a></li>
|
||||
<aside class="markdown-body d-none d-md-block border-left no-print bg-white flex-shrink-0" style="width: 300px">
|
||||
<nav class="position-sticky top-0">
|
||||
<ul class="list-style-none pl-0 text-bold">
|
||||
{% for release in releases %}
|
||||
<li class="border-bottom">
|
||||
{% if release.patches %}
|
||||
<details class="my-0 details-reset release-notes-version-picker" aria-current="page" {% if release.version == allVersions[currentVersion].currentRelease %}open{% endif %}>
|
||||
<summary class="px-3 py-4 my-0 d-flex flex-items-center flex-justify-between">
|
||||
{{ release.version }}
|
||||
<div class="d-flex">
|
||||
<span class="text-gray-light text-mono text-small text-normal mr-1">{{ release.patches | size }} releases</span>
|
||||
{% octicon "chevron-down" %}
|
||||
</div>
|
||||
</summary>
|
||||
<ul class="bg-gray border-top list-style-none px-3 py-4 my-0">
|
||||
{% for patch in release.patches %}
|
||||
<li>
|
||||
<a
|
||||
href="/{{ currentLanguage }}/{{ allVersions[currentVersion].plan }}@{{ release.version }}/{{ currentProduct }}/release-notes#{{ patch.version }}"
|
||||
class="d-flex flex-items-center flex-justify-between">
|
||||
{{ patch.version }}
|
||||
<span class="text-gray-light text-mono text-small text-normal">{{ patch.date | date: "%B %d, %Y" }}</span>
|
||||
</a>
|
||||
</li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
</details>
|
||||
{% else %}
|
||||
<a href="/{{ currentLanguage }}/{{ allVersions[currentVersion].plan }}@{{ release.version }}/{{ currentProduct }}/release-notes" class="link-gray-dark no-underline px-3 py-4 my-0 d-flex flex-items-center flex-justify-between">
|
||||
{{ release.version }}
|
||||
{% octicon "link-external" %}
|
||||
</a>
|
||||
{% endif %}
|
||||
</li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
</aside>
|
||||
</article>
|
||||
</nav>
|
||||
</aside>
|
||||
</div>
|
||||
|
||||
{% include support %}
|
||||
{% include small-footer %}
|
||||
<div class="border-top">
|
||||
{% include small-footer %}
|
||||
</div>
|
||||
</main>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -1,8 +1,32 @@
|
|||
const section = {
|
||||
anyOf: [
|
||||
{
|
||||
type: 'array',
|
||||
items: { type: 'string' },
|
||||
minItems: 1
|
||||
},
|
||||
{
|
||||
type: 'object',
|
||||
properties: {
|
||||
heading: {
|
||||
type: 'string',
|
||||
required: true
|
||||
},
|
||||
notes: {
|
||||
type: 'array',
|
||||
items: { type: 'string' },
|
||||
required: true,
|
||||
minItems: 1
|
||||
}
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
module.exports = {
|
||||
properties: {
|
||||
intro: {
|
||||
type: 'string',
|
||||
required: true
|
||||
type: 'string'
|
||||
},
|
||||
date: {
|
||||
type: 'string',
|
||||
|
|
@ -13,22 +37,18 @@ module.exports = {
|
|||
type: 'boolean',
|
||||
default: false
|
||||
},
|
||||
notes: {
|
||||
sections: {
|
||||
required: true,
|
||||
type: 'array',
|
||||
items: {
|
||||
type: 'object',
|
||||
properties: {
|
||||
note: {
|
||||
type: 'string',
|
||||
required: true
|
||||
},
|
||||
type: {
|
||||
type: 'string',
|
||||
required: true
|
||||
}
|
||||
}
|
||||
}
|
||||
type: 'object',
|
||||
minProperties: 1,
|
||||
properties: [
|
||||
'bugs',
|
||||
'known_issues',
|
||||
'features',
|
||||
'changes',
|
||||
'deprecations',
|
||||
'security_fixes'
|
||||
].reduce((prev, curr) => ({ ...prev, [curr]: section }), {})
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -49098,11 +49098,11 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
},
|
||||
|
|
@ -49302,11 +49302,11 @@
|
|||
},
|
||||
{
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
]
|
||||
|
|
@ -80855,7 +80855,7 @@
|
|||
"httpStatusCode": "200",
|
||||
"httpStatusMessage": "OK",
|
||||
"description": "Default response",
|
||||
"payload": "<pre><code class=\"hljs language-json\">[\n {\n <span class=\"hljs-attr\">\"billing_cycle\"</span>: <span class=\"hljs-string\">\"monthly\"</span>,\n <span class=\"hljs-attr\">\"next_billing_date\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n <span class=\"hljs-attr\">\"unit_count\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"on_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n <span class=\"hljs-attr\">\"free_trial_ends_on\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n <span class=\"hljs-attr\">\"updated_at\"</span>: <span class=\"hljs-string\">\"2017-11-02T01:12:12Z\"</span>,\n <span class=\"hljs-attr\">\"account\"</span>: {\n <span class=\"hljs-attr\">\"login\"</span>: <span class=\"hljs-string\">\"github\"</span>,\n <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">4</span>,\n <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/orgs/github\"</span>,\n <span class=\"hljs-attr\">\"email\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"organization_billing_email\"</span>: <span class=\"hljs-string\">\"billing@github.com\"</span>,\n <span class=\"hljs-attr\">\"type\"</span>: <span class=\"hljs-string\">\"Organization\"</span>\n },\n <span class=\"hljs-attr\">\"plan\"</span>: {\n <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313\"</span>,\n <span class=\"hljs-attr\">\"accounts_url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313/accounts\"</span>,\n <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">1313</span>,\n <span class=\"hljs-attr\">\"number\"</span>: <span class=\"hljs-number\">3</span>,\n <span class=\"hljs-attr\">\"name\"</span>: <span class=\"hljs-string\">\"Pro\"</span>,\n <span class=\"hljs-attr\">\"description\"</span>: <span class=\"hljs-string\">\"A professional-grade CI solution\"</span>,\n <span class=\"hljs-attr\">\"monthly_price_in_cents\"</span>: <span class=\"hljs-number\">1099</span>,\n <span class=\"hljs-attr\">\"yearly_price_in_cents\"</span>: <span class=\"hljs-number\">11870</span>,\n <span class=\"hljs-attr\">\"price_model\"</span>: <span class=\"hljs-string\">\"flat-rate\"</span>,\n <span class=\"hljs-attr\">\"has_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n <span class=\"hljs-attr\">\"unit_name\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"state\"</span>: <span class=\"hljs-string\">\"published\"</span>,\n <span class=\"hljs-attr\">\"bullets\"</span>: [\n <span class=\"hljs-string\">\"Up to 25 private repositories\"</span>,\n <span class=\"hljs-string\">\"11 concurrent builds\"</span>\n ]\n }\n }\n]\n</code></pre>"
|
||||
"payload": "<pre><code class=\"hljs language-json\">[\n {\n <span class=\"hljs-attr\">\"billing_cycle\"</span>: <span class=\"hljs-string\">\"monthly\"</span>,\n <span class=\"hljs-attr\">\"next_billing_date\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n <span class=\"hljs-attr\">\"unit_count\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"on_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n <span class=\"hljs-attr\">\"free_trial_ends_on\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n <span class=\"hljs-attr\">\"updated_at\"</span>: <span class=\"hljs-string\">\"2017-11-02T01:12:12Z\"</span>,\n <span class=\"hljs-attr\">\"account\"</span>: {\n <span class=\"hljs-attr\">\"login\"</span>: <span class=\"hljs-string\">\"github\"</span>,\n <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">4</span>,\n <span class=\"hljs-attr\">\"node_id\"</span>: <span class=\"hljs-string\">\"MDEyOk9yZ2FuaXphdGlvbjE=\"</span>,\n <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/orgs/github\"</span>,\n <span class=\"hljs-attr\">\"email\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"organization_billing_email\"</span>: <span class=\"hljs-string\">\"billing@github.com\"</span>,\n <span class=\"hljs-attr\">\"type\"</span>: <span class=\"hljs-string\">\"Organization\"</span>\n },\n <span class=\"hljs-attr\">\"plan\"</span>: {\n <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313\"</span>,\n <span class=\"hljs-attr\">\"accounts_url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313/accounts\"</span>,\n <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">1313</span>,\n <span class=\"hljs-attr\">\"number\"</span>: <span class=\"hljs-number\">3</span>,\n <span class=\"hljs-attr\">\"name\"</span>: <span class=\"hljs-string\">\"Pro\"</span>,\n <span class=\"hljs-attr\">\"description\"</span>: <span class=\"hljs-string\">\"A professional-grade CI solution\"</span>,\n <span class=\"hljs-attr\">\"monthly_price_in_cents\"</span>: <span class=\"hljs-number\">1099</span>,\n <span class=\"hljs-attr\">\"yearly_price_in_cents\"</span>: <span class=\"hljs-number\">11870</span>,\n <span class=\"hljs-attr\">\"price_model\"</span>: <span class=\"hljs-string\">\"flat-rate\"</span>,\n <span class=\"hljs-attr\">\"has_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n <span class=\"hljs-attr\">\"unit_name\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"state\"</span>: <span class=\"hljs-string\">\"published\"</span>,\n <span class=\"hljs-attr\">\"bullets\"</span>: [\n <span class=\"hljs-string\">\"Up to 25 private repositories\"</span>,\n <span class=\"hljs-string\">\"11 concurrent builds\"</span>\n ]\n }\n }\n]\n</code></pre>"
|
||||
},
|
||||
{
|
||||
"httpStatusCode": "304",
|
||||
|
|
@ -80942,7 +80942,7 @@
|
|||
"httpStatusCode": "200",
|
||||
"httpStatusMessage": "OK",
|
||||
"description": "Default response",
|
||||
"payload": "<pre><code class=\"hljs language-json\">[\n {\n <span class=\"hljs-attr\">\"billing_cycle\"</span>: <span class=\"hljs-string\">\"monthly\"</span>,\n <span class=\"hljs-attr\">\"next_billing_date\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n <span class=\"hljs-attr\">\"unit_count\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"on_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n <span class=\"hljs-attr\">\"free_trial_ends_on\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n <span class=\"hljs-attr\">\"updated_at\"</span>: <span class=\"hljs-string\">\"2017-11-02T01:12:12Z\"</span>,\n <span class=\"hljs-attr\">\"account\"</span>: {\n <span class=\"hljs-attr\">\"login\"</span>: <span class=\"hljs-string\">\"github\"</span>,\n <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">4</span>,\n <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/orgs/github\"</span>,\n <span class=\"hljs-attr\">\"email\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"organization_billing_email\"</span>: <span class=\"hljs-string\">\"billing@github.com\"</span>,\n <span class=\"hljs-attr\">\"type\"</span>: <span class=\"hljs-string\">\"Organization\"</span>\n },\n <span class=\"hljs-attr\">\"plan\"</span>: {\n <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313\"</span>,\n <span class=\"hljs-attr\">\"accounts_url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313/accounts\"</span>,\n <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">1313</span>,\n <span class=\"hljs-attr\">\"number\"</span>: <span class=\"hljs-number\">3</span>,\n <span class=\"hljs-attr\">\"name\"</span>: <span class=\"hljs-string\">\"Pro\"</span>,\n <span class=\"hljs-attr\">\"description\"</span>: <span class=\"hljs-string\">\"A professional-grade CI solution\"</span>,\n <span class=\"hljs-attr\">\"monthly_price_in_cents\"</span>: <span class=\"hljs-number\">1099</span>,\n <span class=\"hljs-attr\">\"yearly_price_in_cents\"</span>: <span class=\"hljs-number\">11870</span>,\n <span class=\"hljs-attr\">\"price_model\"</span>: <span class=\"hljs-string\">\"flat-rate\"</span>,\n <span class=\"hljs-attr\">\"has_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n <span class=\"hljs-attr\">\"unit_name\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"state\"</span>: <span class=\"hljs-string\">\"published\"</span>,\n <span class=\"hljs-attr\">\"bullets\"</span>: [\n <span class=\"hljs-string\">\"Up to 25 private repositories\"</span>,\n <span class=\"hljs-string\">\"11 concurrent builds\"</span>\n ]\n }\n }\n]\n</code></pre>"
|
||||
"payload": "<pre><code class=\"hljs language-json\">[\n {\n <span class=\"hljs-attr\">\"billing_cycle\"</span>: <span class=\"hljs-string\">\"monthly\"</span>,\n <span class=\"hljs-attr\">\"next_billing_date\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n <span class=\"hljs-attr\">\"unit_count\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"on_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n <span class=\"hljs-attr\">\"free_trial_ends_on\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n <span class=\"hljs-attr\">\"updated_at\"</span>: <span class=\"hljs-string\">\"2017-11-02T01:12:12Z\"</span>,\n <span class=\"hljs-attr\">\"account\"</span>: {\n <span class=\"hljs-attr\">\"login\"</span>: <span class=\"hljs-string\">\"github\"</span>,\n <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">4</span>,\n <span class=\"hljs-attr\">\"node_id\"</span>: <span class=\"hljs-string\">\"MDEyOk9yZ2FuaXphdGlvbjE=\"</span>,\n <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/orgs/github\"</span>,\n <span class=\"hljs-attr\">\"email\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"organization_billing_email\"</span>: <span class=\"hljs-string\">\"billing@github.com\"</span>,\n <span class=\"hljs-attr\">\"type\"</span>: <span class=\"hljs-string\">\"Organization\"</span>\n },\n <span class=\"hljs-attr\">\"plan\"</span>: {\n <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313\"</span>,\n <span class=\"hljs-attr\">\"accounts_url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313/accounts\"</span>,\n <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">1313</span>,\n <span class=\"hljs-attr\">\"number\"</span>: <span class=\"hljs-number\">3</span>,\n <span class=\"hljs-attr\">\"name\"</span>: <span class=\"hljs-string\">\"Pro\"</span>,\n <span class=\"hljs-attr\">\"description\"</span>: <span class=\"hljs-string\">\"A professional-grade CI solution\"</span>,\n <span class=\"hljs-attr\">\"monthly_price_in_cents\"</span>: <span class=\"hljs-number\">1099</span>,\n <span class=\"hljs-attr\">\"yearly_price_in_cents\"</span>: <span class=\"hljs-number\">11870</span>,\n <span class=\"hljs-attr\">\"price_model\"</span>: <span class=\"hljs-string\">\"flat-rate\"</span>,\n <span class=\"hljs-attr\">\"has_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n <span class=\"hljs-attr\">\"unit_name\"</span>: <span class=\"hljs-literal\">null</span>,\n <span class=\"hljs-attr\">\"state\"</span>: <span class=\"hljs-string\">\"published\"</span>,\n <span class=\"hljs-attr\">\"bullets\"</span>: [\n <span class=\"hljs-string\">\"Up to 25 private repositories\"</span>,\n <span class=\"hljs-string\">\"11 concurrent builds\"</span>\n ]\n }\n }\n]\n</code></pre>"
|
||||
},
|
||||
{
|
||||
"httpStatusCode": "304",
|
||||
|
|
|
|||
|
|
@ -34324,11 +34324,11 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
},
|
||||
|
|
@ -34528,11 +34528,11 @@
|
|||
},
|
||||
{
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
]
|
||||
|
|
|
|||
|
|
@ -34983,11 +34983,11 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
},
|
||||
|
|
@ -35187,11 +35187,11 @@
|
|||
},
|
||||
{
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
]
|
||||
|
|
|
|||
|
|
@ -35450,11 +35450,11 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
},
|
||||
|
|
@ -35654,11 +35654,11 @@
|
|||
},
|
||||
{
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
]
|
||||
|
|
|
|||
|
|
@ -39099,11 +39099,11 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
},
|
||||
|
|
@ -39303,11 +39303,11 @@
|
|||
},
|
||||
{
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
]
|
||||
|
|
|
|||
|
|
@ -46564,11 +46564,11 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
},
|
||||
|
|
@ -46768,11 +46768,11 @@
|
|||
},
|
||||
{
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
]
|
||||
|
|
|
|||
|
|
@ -36969,11 +36969,11 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
},
|
||||
|
|
@ -37173,11 +37173,11 @@
|
|||
},
|
||||
{
|
||||
"type": "string",
|
||||
"description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
|
||||
"description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
|
||||
"name": "base_tree",
|
||||
"in": "body",
|
||||
"rawType": "string",
|
||||
"rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
|
||||
"rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
|
||||
"childParamsGroups": []
|
||||
}
|
||||
]
|
||||
|
|
|
|||
|
|
@ -155506,7 +155506,7 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
|
||||
"description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
|
||||
}
|
||||
},
|
||||
"required": [
|
||||
|
|
@ -270539,6 +270539,7 @@
|
|||
"account": {
|
||||
"login": "github",
|
||||
"id": 4,
|
||||
"node_id": "MDEyOk9yZ2FuaXphdGlvbjE=",
|
||||
"url": "https://api.github.com/orgs/github",
|
||||
"email": null,
|
||||
"organization_billing_email": "billing@github.com",
|
||||
|
|
@ -270852,6 +270853,7 @@
|
|||
"account": {
|
||||
"login": "github",
|
||||
"id": 4,
|
||||
"node_id": "MDEyOk9yZ2FuaXphdGlvbjE=",
|
||||
"url": "https://api.github.com/orgs/github",
|
||||
"email": null,
|
||||
"organization_billing_email": "billing@github.com",
|
||||
|
|
|
|||
|
|
@ -110376,7 +110376,7 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
|
||||
"description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
|
||||
}
|
||||
},
|
||||
"required": [
|
||||
|
|
|
|||
|
|
@ -113552,7 +113552,7 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
|
||||
"description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
|
||||
}
|
||||
},
|
||||
"required": [
|
||||
|
|
|
|||
|
|
@ -114769,7 +114769,7 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
|
||||
"description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
|
||||
}
|
||||
},
|
||||
"required": [
|
||||
|
|
|
|||
|
|
@ -124029,7 +124029,7 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
|
||||
"description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
|
||||
}
|
||||
},
|
||||
"required": [
|
||||
|
|
|
|||
|
|
@ -145204,7 +145204,7 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
|
||||
"description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
|
||||
}
|
||||
},
|
||||
"required": [
|
||||
|
|
|
|||
|
|
@ -118183,7 +118183,7 @@
|
|||
},
|
||||
"base_tree": {
|
||||
"type": "string",
|
||||
"description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
|
||||
"description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
|
||||
}
|
||||
},
|
||||
"required": [
|
||||
|
|
|
|||
|
|
@ -0,0 +1,8 @@
|
|||
const connectDatadog = require('connect-datadog')
|
||||
const statsd = require('../lib/statsd')
|
||||
|
||||
module.exports = connectDatadog({
|
||||
dogstatsd: statsd,
|
||||
method: true, // Track HTTP methods (GET, POST, etc)
|
||||
response_code: true // Track response codes
|
||||
})
|
||||
|
|
@ -1,5 +1,43 @@
|
|||
const semver = require('semver')
|
||||
const renderContent = require('../../lib/render-content')
|
||||
const patterns = require('../../lib/patterns')
|
||||
const enterpriseReleases = require('../../lib/enterprise-server-releases').supported
|
||||
|
||||
/**
|
||||
* Turn { [key]: { notes, intro, date } }
|
||||
* into [{ version, notes, intro, date }]
|
||||
*/
|
||||
function sortPatchKeys (release, version) {
|
||||
const keys = Object.keys(release)
|
||||
.map(key => ({ version: `${version}.${key}`, patchVersion: key, ...release[key] }))
|
||||
return keys
|
||||
.sort((a, b) => {
|
||||
if (semver.gt(a.version, b.version)) return -1
|
||||
if (semver.lt(a.version, b.version)) return 1
|
||||
return 0
|
||||
})
|
||||
}
|
||||
|
||||
/**
|
||||
* Render each note in the given patch, by looping through the
|
||||
* sections and rendering either `note` or `note.notes` in the
|
||||
* case of a sub-section
|
||||
*/
|
||||
async function renderPatchNotes (patch, ctx) {
|
||||
// Run the notes through the markdown rendering pipeline
|
||||
for (const key in patch.sections) {
|
||||
await Promise.all(patch.sections[key].map(async (noteOrHeading, index) => {
|
||||
patch.sections[key][index] = typeof noteOrHeading === 'string'
|
||||
? await renderContent(noteOrHeading, ctx)
|
||||
: {
|
||||
...noteOrHeading,
|
||||
notes: await Promise.all(noteOrHeading.notes.map(note => renderContent(note, ctx)))
|
||||
}
|
||||
}))
|
||||
}
|
||||
|
||||
return patch
|
||||
}
|
||||
|
||||
module.exports = async (req, res, next) => {
|
||||
// The `/release-notes` sub-path
|
||||
|
|
@ -22,44 +60,23 @@ module.exports = async (req, res, next) => {
|
|||
}
|
||||
|
||||
const releaseNotes = allReleaseNotes[versionString]
|
||||
const keys = Object.keys(releaseNotes)
|
||||
// Turn { [key]: { notes, intro, date } }
|
||||
// into [{ version, notes, intro, date }]
|
||||
const patches = keys
|
||||
.sort((a, b) => {
|
||||
if (a > b) return -1
|
||||
if (a < b) return 1
|
||||
return 0
|
||||
})
|
||||
.map(key => ({ version: `${requestedVersion}.${key}`, ...releaseNotes[key] }))
|
||||
const patches = sortPatchKeys(releaseNotes, requestedVersion)
|
||||
|
||||
const renderedPatches = await Promise.all(patches.map(async patch => {
|
||||
// Render the intro block, it might contain markdown formatting
|
||||
patch.intro = await renderContent(patch.intro, req.context)
|
||||
req.context.releaseNotes = await Promise.all(patches.map(async patch => renderPatchNotes(patch, req.context)))
|
||||
|
||||
// Run the notes through the markdown rendering pipeline
|
||||
patch.notes = await Promise.all(patch.notes.map(async note => {
|
||||
if (note.note) note.note = await renderContent(note.note, req.context)
|
||||
return note
|
||||
}))
|
||||
// Put together information about other releases
|
||||
req.context.releases = enterpriseReleases.map(version => {
|
||||
const ret = { version }
|
||||
if (!req.context.site.data['release-notes']) return ret
|
||||
const release = req.context.site.data['release-notes'][version.replace(/\./g, '-')]
|
||||
if (!release) return ret
|
||||
const patches = sortPatchKeys(release, version)
|
||||
return { ...ret, patches }
|
||||
})
|
||||
|
||||
// Sort the notes into sections
|
||||
// Takes an array of notes: Array<{ note, type }>
|
||||
// Turns it into { [type]: [{ note }] }
|
||||
patch.sortedNotes = patch.notes.reduce((prev, curr) => {
|
||||
const existingObj = prev.find(o => o.title === curr.type)
|
||||
if (!existingObj) {
|
||||
prev.push({ title: curr.type, notes: [curr] })
|
||||
} else {
|
||||
existingObj.notes.push(curr)
|
||||
}
|
||||
return prev
|
||||
}, [])
|
||||
|
||||
return patch
|
||||
}))
|
||||
|
||||
req.context.releaseNotes = renderedPatches
|
||||
const releaseIndex = enterpriseReleases.findIndex(release => release === requestedVersion)
|
||||
req.context.nextRelease = enterpriseReleases[releaseIndex - 1]
|
||||
req.context.prevRelease = enterpriseReleases[releaseIndex + 1]
|
||||
|
||||
return next()
|
||||
}
|
||||
|
|
|
|||
|
|
@ -14,6 +14,11 @@ module.exports = function (app) {
|
|||
app.use(require('morgan')('dev', { skip: (req, res) => !isDevelopment }))
|
||||
if (isDevelopment) app.use(require('./webpack'))
|
||||
|
||||
// *** Observability ***
|
||||
if (process.env.DD_API_KEY) {
|
||||
app.use(require('./connect-datadog'))
|
||||
}
|
||||
|
||||
// *** Early exits ***
|
||||
// Don't use the proxy's IP, use the requester's for rate limiting
|
||||
// See https://expressjs.com/en/guide/behind-proxies.html
|
||||
|
|
|
|||
|
|
@ -5271,7 +5271,7 @@
|
|||
},
|
||||
"agentkeepalive": {
|
||||
"version": "2.2.0",
|
||||
"resolved": "https://registry.npmjs.org/agentkeepalive/-/agentkeepalive-2.2.0.tgz",
|
||||
"resolved": "http://registry.npmjs.org/agentkeepalive/-/agentkeepalive-2.2.0.tgz",
|
||||
"integrity": "sha1-xdG9SxKQCPEWPyNvhuX66iAm4u8="
|
||||
},
|
||||
"aggregate-error": {
|
||||
|
|
@ -5417,7 +5417,7 @@
|
|||
"argparse": {
|
||||
"version": "1.0.10",
|
||||
"resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz",
|
||||
"integrity": "sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==",
|
||||
"integrity": "sha1-vNZ5HqWuCXJeF+WtmIE0zUCz2RE=",
|
||||
"requires": {
|
||||
"sprintf-js": "~1.0.2"
|
||||
}
|
||||
|
|
@ -6794,7 +6794,7 @@
|
|||
},
|
||||
"brfs": {
|
||||
"version": "1.6.1",
|
||||
"resolved": "https://registry.npmjs.org/brfs/-/brfs-1.6.1.tgz",
|
||||
"resolved": "http://registry.npmjs.org/brfs/-/brfs-1.6.1.tgz",
|
||||
"integrity": "sha512-OfZpABRQQf+Xsmju8XE9bDjs+uU4vLREGolP7bDgcpsI17QREyZ4Bl+2KLxxx1kCgA0fAIhKQBaBYh+PEcCqYQ==",
|
||||
"requires": {
|
||||
"quote-stream": "^1.0.1",
|
||||
|
|
@ -7769,6 +7769,24 @@
|
|||
"xdg-basedir": "^4.0.0"
|
||||
}
|
||||
},
|
||||
"connect-datadog": {
|
||||
"version": "0.0.9",
|
||||
"resolved": "https://registry.npmjs.org/connect-datadog/-/connect-datadog-0.0.9.tgz",
|
||||
"integrity": "sha512-CThcRgy6AAStdBRsrNdneeJkEuH0/2G1QanYFfl0F+ZkbQaRMMM9/apvZ1R3SMD9iAST/Xa78Q0jC51KCB/4LQ==",
|
||||
"requires": {
|
||||
"hot-shots": "^6.3.0"
|
||||
},
|
||||
"dependencies": {
|
||||
"hot-shots": {
|
||||
"version": "6.8.7",
|
||||
"resolved": "https://registry.npmjs.org/hot-shots/-/hot-shots-6.8.7.tgz",
|
||||
"integrity": "sha512-XH8iezBSZgVw2jegu96pUfF1Zv0VZ/iXjb7L5yE3F7mn7/bdhf4qeniXjO0wQWeefe433rhOsazNKLxM+XMI9w==",
|
||||
"requires": {
|
||||
"unix-dgram": "2.0.x"
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"connect-slashes": {
|
||||
"version": "1.4.0",
|
||||
"resolved": "https://registry.npmjs.org/connect-slashes/-/connect-slashes-1.4.0.tgz",
|
||||
|
|
@ -9403,7 +9421,7 @@
|
|||
"error-ex": {
|
||||
"version": "1.3.2",
|
||||
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.2.tgz",
|
||||
"integrity": "sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==",
|
||||
"integrity": "sha1-tKxAZIEH/c3PriQvQovqihTU8b8=",
|
||||
"requires": {
|
||||
"is-arrayish": "^0.2.1"
|
||||
}
|
||||
|
|
@ -12541,7 +12559,7 @@
|
|||
"dependencies": {
|
||||
"mkdirp": {
|
||||
"version": "0.3.0",
|
||||
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.0.tgz",
|
||||
"resolved": "http://registry.npmjs.org/mkdirp/-/mkdirp-0.3.0.tgz",
|
||||
"integrity": "sha1-G79asbqCevI1dRQ0kEJkVfSB/h4="
|
||||
},
|
||||
"nopt": {
|
||||
|
|
@ -17667,7 +17685,7 @@
|
|||
},
|
||||
"magic-string": {
|
||||
"version": "0.22.5",
|
||||
"resolved": "https://registry.npmjs.org/magic-string/-/magic-string-0.22.5.tgz",
|
||||
"resolved": "http://registry.npmjs.org/magic-string/-/magic-string-0.22.5.tgz",
|
||||
"integrity": "sha512-oreip9rJZkzvA8Qzk9HFs8fZGF/u7H/gtrE8EN6RjKJ9kh2HlC+yQ2QezifqTZfGyiuAV0dRv5a+y/8gBb1m9w==",
|
||||
"requires": {
|
||||
"vlq": "^0.2.2"
|
||||
|
|
|
|||
|
|
@ -34,6 +34,7 @@
|
|||
"cheerio": "^1.0.0-rc.3",
|
||||
"clipboard": "^2.0.6",
|
||||
"compression": "^1.7.4",
|
||||
"connect-datadog": "0.0.9",
|
||||
"connect-slashes": "^1.4.0",
|
||||
"cookie-parser": "^1.4.5",
|
||||
"copy-webpack-plugin": "^6.0.3",
|
||||
|
|
|
|||
10
server.js
10
server.js
|
|
@ -18,8 +18,14 @@ if (!module.parent) {
|
|||
if (status === false) {
|
||||
// If in a deployed environment, warm the server at the start
|
||||
if (process.env.NODE_ENV === 'production') {
|
||||
// If in a production environment, wait for the cache to be fully warmed.
|
||||
await warmServer()
|
||||
// If in a true production environment, wait for the cache to be fully warmed.
|
||||
if (process.env.HEROKU_PRODUCTION_APP || process.env.GITHUB_ACTIONS) {
|
||||
await warmServer()
|
||||
} else {
|
||||
// If not in a true production environment, don't wait for the cache to be fully warmed.
|
||||
// This avoids deployment timeouts in environments with slower servers.
|
||||
warmServer()
|
||||
}
|
||||
}
|
||||
|
||||
// workaround for https://github.com/expressjs/express/issues/1101
|
||||
|
|
|
|||
|
|
@ -0,0 +1,83 @@
|
|||
// Dark Text Gradients
|
||||
|
||||
.text-gradient {
|
||||
-webkit-background-clip: text !important;
|
||||
background-clip: text !important;
|
||||
-webkit-text-fill-color: transparent;
|
||||
-webkit-box-decoration-break: clone;
|
||||
|
||||
&-aquamarine-mauve {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(130deg, #3bf0e4 -6.8%, #bca1f7 70%);
|
||||
}
|
||||
&-dark-mint {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(90deg, #05aa82, #1c8df0);
|
||||
}
|
||||
&-mint-blue-dark {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #a2facf 0%, #64acff 100%);
|
||||
}
|
||||
&-coral-yellow-dark {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #ff7170 0%, #ffe57f 100%);
|
||||
}
|
||||
&-purple-coral-dark {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(92deg, #bca1f7 15%, #e577b4 45%, #ff7170 85%);
|
||||
}
|
||||
&-turq-purple-dark {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #3bf0e4 0%, #bca1f7 100%);
|
||||
}
|
||||
&-pink-blue-dark {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #e577b4 0%, #64acff 100%);
|
||||
}
|
||||
|
||||
// Light Text Gradients
|
||||
&-blue-green {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #2188ff 0%, #01a49e 100%);
|
||||
}
|
||||
&-red-orange {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #ed4e50 0%, #f06f00 100%);
|
||||
}
|
||||
&-purple-coral {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #9867f0 0%, #ed4e50 100%);
|
||||
}
|
||||
&-blue-purple {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #2188ff 0%, #804eda 100%);
|
||||
}
|
||||
&-pink-blue {
|
||||
@extend .text-gradient;
|
||||
background: -webkit-linear-gradient(-70deg, #db469f 0%, #2188ff 100%);
|
||||
}
|
||||
}
|
||||
|
||||
.bg-gradient {
|
||||
&-red-orange {
|
||||
background: linear-gradient(-70deg, #ed4e50 0%, #f06f00 100%);
|
||||
}
|
||||
&-aquamarine-mauve {
|
||||
background: linear-gradient(130deg, #3bf0e4 -6.8%, #bca1f7 70%);
|
||||
}
|
||||
&-purple-coral {
|
||||
background: linear-gradient(87.54deg, #9867f0 -6.8%, #ed4e50 84.14%);
|
||||
}
|
||||
&-coral-yellow {
|
||||
background: linear-gradient(267.91deg, #ffe57f 9.35%, #ff7170 96.48%);
|
||||
}
|
||||
&-dark-mint {
|
||||
background: linear-gradient(90deg, #05aa82, #1c8df0);
|
||||
}
|
||||
&-mint-blue {
|
||||
background: linear-gradient(271.72deg, #a2facf 7.09%, #64acff 96.61%);
|
||||
}
|
||||
&-blue-purple {
|
||||
background: linear-gradient(90.91deg, #027bfd -24.67%, #9f51fb 53.55%);
|
||||
}
|
||||
}
|
||||
|
|
@ -56,3 +56,5 @@ $marketing-font-path: "/dist/fonts/";
|
|||
@import "shadows.scss";
|
||||
@import "product-landing.scss";
|
||||
@import "dev-toc.scss";
|
||||
@import "release-notes.scss";
|
||||
@import "gradients.scss";
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
ul.release-notes-list li.release-notes-list-item {
|
||||
&::marker {
|
||||
// `• `
|
||||
content: '\2022\00a0';
|
||||
font-size: 1.6em;
|
||||
margin-right: $spacer-2;
|
||||
color: $gray-400;
|
||||
}
|
||||
|
||||
&.list-style-none::marker {
|
||||
content: '';
|
||||
}
|
||||
}
|
||||
|
||||
details[open].release-notes-version-picker summary .octicon.octicon-chevron-down {
|
||||
transform: rotate(180deg);
|
||||
}
|
||||
|
|
@ -48,7 +48,8 @@ describe('check for repository references', () => {
|
|||
'docs/index.yaml',
|
||||
'lib/excluded-links.js',
|
||||
'content/early-access',
|
||||
'data/early-access'
|
||||
'data/early-access',
|
||||
'data/release-notes' // These include links to internal issues in Liquid comments
|
||||
]
|
||||
})
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче