[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fOQaTDXVYyo45djCDT4QFYGiunbMT7NBuY3zxCEFFMQE":3,"$fGrMF0RpZ4Ma3Fl9hgiPXx41lUEXvXryqZt8vtMqLuEc":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"github-rest-api","GitHub API","github","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fgithub\u002Frest-api-description\u002Fmain\u002Fdescriptions\u002Fapi.github.com\u002Fapi.github.com.json",{"id":13,"contentHash":14,"fetchedAt":15},"01KWFV4FWJ0QMZ3PFG32WW5YHK","99cd66559d8e0cad34c55ba26aa3f8d84fda395ffc78ebae3329358415482d52","2026-07-01T22:00:01.176Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KWZ2N2T1BCJQGT9VQ33EJEG5","b2f6e33e0e292caae71e426320d39e88a5446ee724442011497de6d561afb58d","2026-07-07T20:00:01.212Z",null,{"alerts":22},[23,30,36,43,50,57,64,71,79,86,93,101,108,115,122,129,136,143,150,157,164,171],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KWZ2N89XGF3PDKMTR6AJJPKQ","Additive","Add license_compliance_scanning repository rule type","The API now supports a new `license_compliance_scanning` repository rule type that enforces added or changed dependencies to comply with the organization's license policy. This is a purely additive change that does not affect existing integrations. Additionally, several example URLs were updated from internal examples (`mycompany.com`, `my-github-app.com`) to standard examples (`example.com`), which are documentation-only changes.","2026-07-07T20:00:09.021Z","2026-07-07-add-license-compliance-scanning-repository-rule-type",{"id":31,"severity":25,"title":32,"summary":33,"contentHash":14,"detectedAt":34,"slug":35},"01KWFV4MWDFS12H0H60H061KPR","Team member endpoints now include role and inheritance info","The `GET \u002Forgs\u002F{org}\u002Fteams\u002F{team_slug}\u002Fmembers` and legacy `GET \u002Fteams\u002F{team_id}\u002Fmembers` endpoints now return a new `team-member` schema instead of `simple-user`, including two new response fields: `role` (member\u002Fmaintainer) and `inherited` (boolean indicating child team membership). These are purely additive fields on the response; existing code continues to work since all previous fields are still present.","2026-07-01T22:00:08.333Z","2026-07-01-team-member-endpoints-now-include-role-and-inheritance-info",{"id":37,"severity":25,"title":38,"summary":39,"contentHash":40,"detectedAt":41,"slug":42},"01KWF6HF2TV6R2ZZY4KH3R8DES","Add duplicate_issue_id parameter to issue update","A new optional `duplicate_issue_id` parameter has been added to issue update requests, allowing users to specify the canonical duplicate issue when marking an issue as a duplicate. This is purely additive and cannot break existing code.","74cd123856b3ccb4f1325bd61a02b6831ee4e5fca91ee70e5b5218b20aeabfe8","2026-07-01T16:00:08.282Z","2026-07-01-add-duplicate-issue-id-parameter-to-issue-update",{"id":44,"severity":25,"title":45,"summary":46,"contentHash":47,"detectedAt":48,"slug":49},"01KWCV0MAQ43KMMCTHEJQEAWQ4","Add agent_assignment param and multi_user_cost_center budget scope","The diff adds an optional `agent_assignment` object to Dependabot Alert assignment requests, enabling custom instructions, agents, and models when assigning AI agents. It also adds `multi_user_cost_center` as a new budget scope option across multiple endpoints. Both changes are backwards-compatible additions that don't affect existing integrations.","71737578990120d430d50c7034379ea388a3dfb04f48e32cbfb75412bf9e6b28","2026-06-30T18:00:13.399Z","2026-06-30-add-agent-assignment-param-and-multi-user-cost-center",{"id":51,"severity":25,"title":52,"summary":53,"contentHash":54,"detectedAt":55,"slug":56},"01KWA8KV4XAKK87XKG9HE4JWY4","Add issue blocking\u002Fblocked-by events and update org invitation response","The API now supports webhook events for issue blocking relationships: new event types `blocked-by-added-issue-event`, `blocked-by-removed-issue-event`, `blocking-added-issue-event`, and `blocking-removed-issue-event` have been added to the `issue-event-for-issue` schema. Additionally, the **Accept Organization Invitation** endpoint now returns `202 Accepted` responses alongside `200 OK`, and the interaction limits bypass-list endpoint's permission requirement documentation was updated from \"repository admins\" to \"users with maintainer permissions\". These are backward-compatible enhancements to the API.","cfa53c9f9bcbe2e98eddb3825a2966deb4c43e78d31d2220938c4dde1e4e313d","2026-06-29T18:00:11.165Z","2026-06-29-add-issue-blocking-blocked-by-events-and-update-org",{"id":58,"severity":25,"title":59,"summary":60,"contentHash":61,"detectedAt":62,"slug":63},"01KW09AHGWBNN0WWPCB2M3KHDW","Add support for issue hierarchies and expanded budget scopes","GitHub REST API adds support for **issue hierarchies** (parent\u002Fsub-issue relationships) via new schema types `issue-reference`, `sub-issue-added-issue-event`, `sub-issue-removed-issue-event`, `parent-issue-added-issue-event`, and `parent-issue-removed-issue-event`. The issue event timeline now includes these new event types. Additionally, budget APIs now support **`user` and `multi_user_customer` scopes** with new optional fields `user` and `consumed_amount`. The assignees field in issue creation is expanded to accept both strings and objects. Finally, permission requirements for pull request bypass list management are clarified from \"repository admins\" to \"maintainer permissions.\" All changes are backward-compatible additions.","69414372b0796f815147acd9c65a99e46b9688cda46cc2495a3861fa9396ef1c","2026-06-25T21:00:10.652Z","2026-06-25-add-support-for-issue-hierarchies-and-expanded-budget-scopes",{"id":65,"severity":25,"title":66,"summary":67,"contentHash":68,"detectedAt":69,"slug":70},"01KVVBCT5DEMGWSXQN69M8T9A6","Add code quality findings API endpoints","GitHub added two new code quality findings endpoints: `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fcode-quality\u002Ffindings` to list findings and `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fcode-quality\u002Ffindings\u002F{finding_number}` to retrieve a single finding. These are entirely new API routes with no breaking changes to existing functionality. The diff also includes minor documentation updates to existing code scanning endpoints and adds new schema fields like `minimized` to issue comments and new issue type event types to support the timeline API.","d096845f8d9af2ffb2f96f21f8cb2c64c979f163c82e152ffd65a1a80a589d4b","2026-06-23T23:00:10.029Z","2026-06-23-add-code-quality-findings-api-endpoints",{"id":72,"severity":73,"title":74,"summary":75,"contentHash":76,"detectedAt":77,"slug":78},"01KVGM2RGJTBGJYKNKHJHQ0TFG","Breaking","Remove GET \u002Forgs\u002F{org}\u002Fcopilot\u002Fmetrics and GET \u002Forgs\u002F{org}\u002Fteam\u002F{team_slug}\u002Fcopilot\u002Fmetrics endpoints","Two Copilot metrics endpoints have been **removed** from the spec:\n- `GET \u002Forgs\u002F{org}\u002Fcopilot\u002Fmetrics` (operationId `copilot\u002Fcopilot-metrics-for-organization`)\n- `GET \u002Forgs\u002F{org}\u002Fteam\u002F{team_slug}\u002Fcopilot\u002Fmetrics` (operationId `copilot\u002Fcopilot-metrics-for-team`)\n\nAny clients or SDK calls targeting these endpoints will receive 404s. Additionally, the `usage_metrics_api_disabled` response component and the `code_scanning_upload` rate-limit field were removed. The description for `GET \u002Forgs\u002F{org}\u002Fartifacts\u002F{subject_digest}\u002Fmetadata\u002Fstorage-records` also notes a changed required permission: fine-grained tokens now need `artifact-metadata:read` instead of `content:read`.","50070bba280e24c124f73b20a999022e57198f7e2d30d9a3d5c78006731714c7","2026-06-19T19:00:19.090Z","2026-06-19-remove-get-orgs-org-copilot-metrics-and-get-orgs-org-team",{"id":80,"severity":25,"title":81,"summary":82,"contentHash":83,"detectedAt":84,"slug":85},"01KV8WW8A7N2N76FYMGFZG8VFX","Add GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fissue-types endpoint","A new endpoint `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fissue-types` has been added to list issue types available for a repository. This is a purely additive change that does not affect any existing functionality, and requires only the \"Metadata\" repository permission (read) for fine-grained access tokens.","90e04c74fca883c1222b4b5aca4d1a305ee98862830865a0dbe205b2288310c3","2026-06-16T19:00:07.623Z","2026-06-16-add-get-repos-owner-repo-issue-types-endpoint",{"id":87,"severity":25,"title":88,"summary":89,"contentHash":90,"detectedAt":91,"slug":92},"01KV63KX6VWSEYK14E6CY8G12X","Add BundlePricing budget type, user field, runtime_risks, and drives scope","The GitHub API adds support for **`BundlePricing`** as a new budget type option (alongside existing `ProductPricing` and `SkuPricing`), introduces a new optional **`user`** field for user-scoped budgets, adds a **`runtime_risks`** array field to deployment examples, and introduces a new **`drives`** OAuth scope for read\u002Fwrite access. All changes are additive with improved documentation of budget type behavior and no removals of existing functionality.","8d7a2ddc367e44940709b0b4994e21619142c96c779dce3b29fef24ff951fe95","2026-06-15T17:00:10.843Z","2026-06-15-add-bundlepricing-budget-type-user-field-runtime-risks-and",{"id":94,"severity":95,"title":96,"summary":97,"contentHash":98,"detectedAt":99,"slug":100},"01KTW4AHVYBJ96S9TX5WSZ2S1S","Informational","Update budget API pagination documentation","The GitHub API documentation for `GET \u002Forganizations\u002F{org}\u002Fsettings\u002Fbilling\u002Fbudgets` was updated to clarify that the endpoint can return up to 100 budgets per page (changed from \"up to 10\"). This is a documentation-only change to the `description` field that reflects actual API capability and does not alter behavior or breaking compatibility.","8e05c4f9390484e733b1f264fd6f64e05982c6a076df85a5bb943941f4d6ca59","2026-06-11T20:00:08.574Z","2026-06-11-update-budget-api-pagination-documentation",{"id":102,"severity":73,"title":103,"summary":104,"contentHash":105,"detectedAt":106,"slug":107},"01KTSHY2D182EC6DGHGFC54PBM","description no longer required in code security config requests","Two changes affect code security configuration endpoints: **`description`** is removed from the `required` array in request bodies (in two places), making it optional — this is additive\u002Frelaxing for clients. Additionally, the `description` response field now has `\"nullable\": true`, meaning clients must handle `null` values where they previously could assume a string. The nullable change could break clients that don't guard against `null` for `description`.","3e7da5cecfba1791ee2e5d006d1c1240c01836a2fb12484210a84358ad919535","2026-06-10T20:00:16.289Z","2026-06-10-description-no-longer-required-in-code-security-config",{"id":109,"severity":25,"title":110,"summary":111,"contentHash":112,"detectedAt":113,"slug":114},"01KTKVZ5KN87MJ8KQMEWBGTXS7","Add multi-select field support to GitHub Projects API","The GitHub API now supports `multi_select` field types and associated properties across Projects endpoints. New optional fields include `has_pull_requests` and `pull_request_creation_policy` for repository settings, and responses now include `multi_select_options`, `value_ids`, and `options` for multi-select field data. All changes are purely additive with no breaking modifications to existing fields or endpoints.","7dcf50fb93d26ad2021c9fdb48c88fe78a63ce3b187a78f30f509c7e75869c65","2026-06-08T15:00:11.509Z","2026-06-08-add-multi-select-field-support-to-github-projects-api",{"id":116,"severity":25,"title":117,"summary":118,"contentHash":119,"detectedAt":120,"slug":121},"01KTCSC579AGB4RF43GETA28GQ","Add budget management schemas and examples to API","The GitHub API OpenAPI specification has been refactored to extract and consolidate budget response schemas into reusable components. Inline schema definitions for budget creation and update endpoints have been replaced with `$ref` pointers to newly created `create-budget` and `update-budget` schema components. A new `repository-rule-params-dismissal-restriction` schema component has been added. A concrete example for budget creation has been added to the examples section. These changes maintain backward compatibility while improving API specification organization and maintainability.","f385514c42168725359a7748c0cb3c4eeb676c7b957c8d1dc3f1a7d902ce8f6d","2026-06-05T21:00:10.345Z","2026-06-05-add-budget-management-schemas-and-examples-to-api",{"id":123,"severity":95,"title":124,"summary":125,"contentHash":126,"detectedAt":127,"slug":128},"01KTC86RM23ZHN64T16YQ3WJP3","Remove public preview notice from budgets API descriptions","Removed the \"> [!NOTE]\\n> This endpoint is in public preview and is subject to change.\" notice from the descriptions of five budget-related endpoints. This indicates the budgets API endpoints have exited public preview and are now stable, which is a positive development for clients but does not change the functional API contract or require code changes.","f47d4224828f50017019f43aa9d38d9a16792f2e1b9bbd01b074494ce0c65d72","2026-06-05T16:00:07.810Z","2026-06-05-remove-public-preview-notice-from-budgets-api-descriptions",{"id":130,"severity":25,"title":131,"summary":132,"contentHash":133,"detectedAt":134,"slug":135},"01KT7H4V3D81JKM88YCYCVR84R","Add budget scopes and user filtering for GitHub billing APIs","The GitHub billing budgets API gains two new budget scopes (`multi_user_customer` and `user`), a new optional `user` query parameter for filtering budget details, and a new POST endpoint to create budgets for organizations. Response schemas also add `user` and `effective_budget` fields when using the `user` filter. All changes are backward-compatible additions.","f089075adfa4fdd9f3fadc0b773b56e4db86397009e4f23dac61a7ae96acd0b7","2026-06-03T20:00:09.837Z","2026-06-03-add-budget-scopes-and-user-filtering-for-github-billing-apis",{"id":137,"severity":25,"title":138,"summary":139,"contentHash":140,"detectedAt":141,"slug":142},"01KT4QWEJD865JVNMVCCK5W7XH","Add AI credit usage billing report endpoints","Two new GET endpoints for AI credit usage reports: `\u002Forganizations\u002F{org}\u002Fsettings\u002Fbilling\u002Fai_credit\u002Fusage` for organizations and `\u002Fusers\u002F{username}\u002Fsettings\u002Fbilling\u002Fai_credit\u002Fusage` for users. Both support optional query parameters for filtering by year, month, day, and AI model\u002Fproduct. These are purely additive endpoints with no impact on existing functionality.","2024a56b8589002323627ccf8deb27c32a4fff548306080529663fda37ffdcba","2026-06-02T18:00:11.597Z","2026-06-02-add-ai-credit-usage-billing-report-endpoints",{"id":144,"severity":25,"title":145,"summary":146,"contentHash":147,"detectedAt":148,"slug":149},"01KT1YKXP0FZQEPX6YZV6VCYRW","New hash algorithm endpoint and runner version field","GitHub API adds a new `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fhash-algorithm` endpoint to retrieve the hash algorithm used by a repository, a new optional `version` field to runner objects, a new `repository-rule-params-actor` schema for repository rules, and a new `evaluate_status` query parameter for rule suite filtering. These are all backward-compatible additions that do not affect existing integrations.","82ceb7bc2d59c85bcd6389becc637b9ae3bf209b6b6746d5294148a4b178ea47","2026-06-01T16:00:08.896Z","2026-06-01-new-hash-algorithm-endpoint-and-runner-version-field",{"id":151,"severity":25,"title":152,"summary":153,"contentHash":154,"detectedAt":155,"slug":156},"01KS61ZESTA0NFG6ZM0XW9JFQ2","GitHub API: new optional parameters and response fields","GitHub API adds several new optional features: **`creator_id`** query parameter now accepts multiple user IDs (type changed to array), new optional **`head_ref`** field in commit request body, **`custom_properties`** object in repository responses, **`read`** permission level option for **`organization_copilot_seat_management`**, and relaxed commit SHA validation pattern. All changes are backward-compatible and purely additive.","6c30e839ce65ee91b72b576b5a202884e784a2d357c1a4f4d7a6ec77a576d3b7","2026-05-21T20:00:08.506Z","2026-05-21-github-api-new-optional-parameters-and-response-fields",{"id":158,"severity":25,"title":159,"summary":160,"contentHash":161,"detectedAt":162,"slug":163},"01KS27RSXZ63JAHZFSTVCKXH02","Add code quality setup configuration endpoints","Two new endpoints added to manage code quality setup configuration: **GET** `\u002Frepos\u002F{owner}\u002F{repo}\u002Fcode-quality\u002Fsetup` to retrieve configuration and **PATCH** `\u002Frepos\u002F{owner}\u002F{repo}\u002Fcode-quality\u002Fsetup` to update configuration. These additions enable programmatic management of code quality setup and do not affect existing API contracts.","93b14ec8053fde77ac78837e73db9346e3f8802fb4bf4b801ff4269dad89c4ca","2026-05-20T08:24:24.255Z","2026-05-20-add-code-quality-setup-configuration-endpoints",{"id":165,"severity":25,"title":166,"summary":167,"contentHash":168,"detectedAt":169,"slug":170},"01KRP8E51S1Z180MHEEMC1XJC1","New Copilot and repository rule endpoints and fields","Added new endpoint `GET \u002Fenterprises\u002F{enterprise}\u002Fcopilot\u002Fmetrics\u002Freports\u002Fuser-teams-1-day` for Copilot enterprise user-teams reporting, three new repository rule schemas (`max_file_path_length`, `file_extension_restriction`, `max_file_size`), and a new `type` field in issue responses. All changes are purely additive and backward compatible.","0d106d91bafdcbdfe0ad0b4e39c2b3da605183b04fbce19eb7cd3ea2edf187eb","2026-05-15T16:45:10.585Z","2026-05-15-new-copilot-and-repository-rule-endpoints-and-fields",{"id":172,"severity":25,"title":173,"summary":174,"contentHash":175,"detectedAt":176,"slug":177},"01KRF1HSYHPC61Q8DH2YDB6N57","Add code_quality permission scope and new actor types","The GitHub REST API now includes a new **`code_quality`** permission scope for access tokens to view and manage code quality data. Additionally, the ruleset bypass actor types now support **`User`** type, and code scanning alert status descriptions expanded to include \"failed\" and \"unknown\" states. String field length constraints (`maxLength`) were added to artifact-related properties, and descriptions clarified that autofix endpoints operate on the default branch.","e55ab1fbb5f9ec5e850e577ffd2a899ee9fbde8ba43ac2aaebd652793af3ad0d","2026-05-12T21:30:09.233Z","2026-05-12-01krf1hsyhpc61q8dh2ydb6n57"]