[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fQevDwOvPdZ764PNUls06_-8AFO5zx-FvIMTLFRYoAe4":3,"$f5RbrD8HSce4sk8eHUfgkVPZS5wCj-r8RNYTanXv5xYw":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},"gitlab-openapi","GitLab API","gitlab","openapi-yaml","rest","https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fgitlab\u002F-\u002Fraw\u002Fmaster\u002Fdoc\u002Fapi\u002Fopenapi\u002Fopenapi_v2.yaml",{"id":13,"contentHash":14,"fetchedAt":15},"01KX4AWCGWXXW3WX0SMYCD8GRK","e1b97b4237aea30551fb6e47bb9e92f5467802eb957fc208dad6df141f0ccc47","2026-07-09T21:00:02.772Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KX56B97BWCJW3HAJS2DJAGCB","7f07bc753e3629c20de87f7bbd23f03094f8b49ee9b78af7ec7a66e190211bb7","2026-07-10T05:00:02.431Z",null,{"alerts":22},[23,30,37,44,51,58,65,72,79,86,93,100,107,114,121,129,136,143,150,157,164,171,178,185,192,199,206,213,220,227,234,241,248,255,262,269,276,283,290,297,304,311,318,325,332,339,346,353,360,367],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KX56BE0SKHD8CTQ354FWWAZT","Informational","Update parameter descriptions for breaking change resolution","Documentation descriptions for the `duo_dependency_bump_breaking_changes_enabled` parameter across multiple project endpoints were simplified from \"Enable GitLab Duo AI-powered resolution of breaking changes from dependency bumps\" to \"Turn on Agentic Breaking Change Resolution\" (or \"Enable Agentic Breaking Change Resolution\"). This is a purely documentary change that does not affect the API's behavior, parameters, or response structure — existing integrations will continue to work unchanged.","2026-07-10T05:00:08.089Z","2026-07-10-update-parameter-descriptions-for-breaking-change-resolution",{"id":31,"severity":32,"title":33,"summary":34,"contentHash":14,"detectedAt":35,"slug":36},"01KX4AWJ2SB88XG6G2RVJ3K4R1","Additive","Add granular_scopes field to personal access tokens","The diff adds a new `granular_scopes` response field (an array of `API_Entities_PersonalAccessTokenGranularScope` objects) to personal access token endpoints. This is a new optional response field that reveals granular permission scopes for tokens, along with a new schema definition. Existing integrations reading personal access token responses will continue to work, and clients can optionally consume the new field if needed.","2026-07-09T21:00:09.177Z","2026-07-09-add-granular-scopes-field-to-personal-access-tokens",{"id":38,"severity":25,"title":39,"summary":40,"contentHash":41,"detectedAt":42,"slug":43},"01KX2D2ZA09Y7JD0S0H2GSEE3M","GitLab API docs improved with better summaries and descriptions","OpenAPI documentation for GitLab's issue-related endpoints received comprehensive updates to `summary` and `description` fields across multiple endpoints. Changes include added `summary` fields where missing, improved descriptions with clarification on authorization requirements and operation details, and standardized language across similar endpoints — all without modifying request\u002Fresponse schemas or endpoint behavior.","1b81f68ac8e7765942a436fc287804915ca5ba1620adc89c995811633d4f1326","2026-07-09T03:00:07.616Z","2026-07-09-gitlab-api-docs-improved-with-better-summaries-and",{"id":45,"severity":25,"title":46,"summary":47,"contentHash":48,"detectedAt":49,"slug":50},"01KX1N21E1W0NZ5CFVDFHG8C3G","Update documentation and descriptions for member\u002Fpackage\u002Favatar endpoints","This diff updates OpenAPI documentation across multiple endpoints, rewording summaries and descriptions for clarity and accuracy. Changes include distinguishing between group and project member operations, clarifying that certain endpoints return only direct members or inherited members, and improving descriptions for group avatars, packages, and namespace subscriptions. No API behavior, request parameters, or response structures are altered—only documentation text is refined.","002fe396ff19d5e117d503b92506f73d11a704924d835aeb83411d5f6061cc69","2026-07-08T20:00:11.201Z","2026-07-08-update-documentation-and-descriptions-for-member-package",{"id":52,"severity":32,"title":53,"summary":54,"contentHash":55,"detectedAt":56,"slug":57},"01KX0P55A4D41NTJ6DT1ZNN9KY","Add optional ref_type query parameter to archive endpoint","A new optional query parameter `ref_type` has been added to the archive endpoint, allowing callers to specify whether the `sha` refers to a branch (`heads`) or a tag (`tags`). This is purely additive and does not break existing integrations.","7d51d90f25a8f4db84af102c9c958f8cab7d8c9fb7b3fe8ab417c4c6854b5004","2026-07-08T11:00:07.620Z","2026-07-08-add-optional-ref-type-query-parameter-to-archive-endpoint",{"id":59,"severity":25,"title":60,"summary":61,"contentHash":62,"detectedAt":63,"slug":64},"01KWYRBNT3S9244MGJZ403ZRFV","OpenAPI spec int32 to int64 format corrections","Multiple integer field formats updated from `int32` to `int64` across package, project, protected branch, and snippet schema definitions in the OpenAPI specification. This is a documentation correction reflecting actual API behavior and does not change runtime behavior or client compatibility.","8544f2d0c829eaceffcee9e7b45705eb72aae9d629a320378e57fed8e20f7b64","2026-07-07T17:00:09.411Z","2026-07-07-openapi-spec-int32-to-int64-format-corrections",{"id":66,"severity":25,"title":67,"summary":68,"contentHash":69,"detectedAt":70,"slug":71},"01KWYHFXF6T48NKXEVTWTQPSAB","GitLab Conan API documentation improvements","The diff updates summaries and descriptions for 15 Conan package registry endpoints to be more descriptive and precise. Changes include: replacing generic action verbs with specific operation names (\"Ping the Conan API\" → \"Verify availability of a Conan repository\"), removing \"This feature was introduced in GitLab X.Y\" boilerplate, and adding clearer operation context. No endpoint paths, parameters, response schemas, or behaviour are modified.","3682e69197f9dc531e264bb0d4262f2f1db9c88c0b98553bcf08d42b99d5923a","2026-07-07T15:00:08.294Z","2026-07-07-gitlab-conan-api-documentation-improvements",{"id":73,"severity":25,"title":74,"summary":75,"contentHash":76,"detectedAt":77,"slug":78},"01KWWCTMT2GDRDPHKSQQJ9FSBH","OpenAPI spec documentation improvements","This diff contains rewording and clarity improvements to OpenAPI documentation summaries and descriptions across multiple endpoints. The changes make descriptions more consistent and detailed (e.g., \"Authenticate user against conan CLI\" → \"Retrieve an authentication token\") but do not alter request\u002Fresponse schemas, parameters, or functional behavior.","4730a586c1a018d81ed0bab809da3fd254c435d0c26c8bfe106e5e745bceec37","2026-07-06T19:00:08.130Z","2026-07-06-openapi-spec-documentation-improvements",{"id":80,"severity":32,"title":81,"summary":82,"contentHash":83,"detectedAt":84,"slug":85},"01KWW5YYKSEN6AHF10VJGX0T5W","Add appearance_uploads metrics to GitLab Geo metrics","Added 16 new optional response fields for appearance upload metrics to GitLab Geo API responses. These fields track checksum, synchronization, and verification status of appearance uploads across distributed instances. The change is purely additive and does not affect existing integrations.","ede966facfeb712008173f2f974dac8af3d022ab2dc645e299a6224a0bb7be57","2026-07-06T17:00:09.209Z","2026-07-06-add-appearance-uploads-metrics-to-gitlab-geo-metrics",{"id":87,"severity":25,"title":88,"summary":89,"contentHash":90,"detectedAt":91,"slug":92},"01KWW2H5B46HF85EQ82ZYR61R3","Update API documentation for invitations and topics endpoints","Documentation clarifications across invitation management endpoints (groups\u002Fprojects) and topic management endpoints. Updated summaries and descriptions to be more specific about endpoint behavior and to separate group-specific and project-specific operations that previously shared generic language. No changes to request\u002Fresponse schemas, parameters, or API behavior.","995eb51b96f43d9f0df573aedf95cbfbf0fc8e232aad670ba36a31d13ca4e423","2026-07-06T16:00:11.620Z","2026-07-06-update-api-documentation-for-invitations-and-topics",{"id":94,"severity":25,"title":95,"summary":96,"contentHash":97,"detectedAt":98,"slug":99},"01KWVHBSV6RBF4DM3E86CD8ASB","Update GitLab API documentation descriptions for upload endpoints","Updated descriptions for four file upload endpoints to clarify language and, in one case, to document required access roles. The changes reword \"by ID\u002Fsecret and filename\" to \"with a specified ID\u002Fsecret and filename\" and add role requirements for the `\u002Fuploads\u002F{secret}\u002F{filename}` GET endpoint. No endpoint URLs, request\u002Fresponse schemas, or functional behavior changed.","823ef5ac09c396b6b401827e77e1f010b045416ebea97753713bd306bc131ec6","2026-07-06T11:00:10.214Z","2026-07-06-update-gitlab-api-documentation-descriptions-for-upload",{"id":101,"severity":25,"title":102,"summary":103,"contentHash":104,"detectedAt":105,"slug":106},"01KWP5PMAE4JEYWVT15B9Z745J","Update API documentation summaries and descriptions","GitLab has improved the OpenAPI documentation by rewriting numerous endpoint summaries and descriptions to be more consistent, concise, and descriptive of what the endpoint does. These changes include: **NuGet package endpoints** (v2, v3, and symbol uploads) now have clearer language about uploading packages; **package management endpoints** (list, retrieve, delete) use more consistent imperative language; **project endpoints** (get, delete, fork, archive) have improved summaries; and **group\u002Fuser listing endpoints** have expanded descriptions with pagination and authentication details. No API behavior, parameters, or response schemas have changed — only the documentation strings that appear in API clients and tools.","40745f9e86ca7f430753116a8b4dcf89c4ce5efb89e86c4bb02e68c4e7c72d6b","2026-07-04T09:00:09.934Z","2026-07-04-update-api-documentation-summaries-and-descriptions",{"id":108,"severity":32,"title":109,"summary":110,"contentHash":111,"detectedAt":112,"slug":113},"01KWN3BX9WWEH1ZKA7KPHNBJYP","Add pagination method and keyset pagination support to commits list","Added two new optional query parameters to the commits list endpoint: `pagination` (defaults to `legacy`, supports `keyset` option) and `page_token` (for keyset pagination). These are purely additive optional parameters that do not affect existing integrations using default pagination.","429252c98bf747088ffa57448596d0589a9f24ef7592f69d1f066fce82822152","2026-07-03T23:00:07.100Z","2026-07-03-add-pagination-method-and-keyset-pagination-support-to",{"id":115,"severity":25,"title":116,"summary":117,"contentHash":118,"detectedAt":119,"slug":120},"01KWMWG8F3K1ZDF60S7HDN3B6E","Documentation improvements for usage_data and events endpoints","Multiple API endpoint descriptions and summaries were clarified and expanded with additional implementation details. The changes improve documentation for the events list endpoint and several usage_data endpoints (`track_events`, `metric_definitions`, `service_ping`, `track_event`, `non_sql_metrics`, and `queries`), but do not alter any functional behaviour, parameters, or response structures.","b3e92929be424747f5e2f5b9cb328ed855c3e404e481e8f790a3c3970c6b97b3","2026-07-03T21:00:09.571Z","2026-07-03-documentation-improvements-for-usage-data-and-events",{"id":122,"severity":123,"title":124,"summary":125,"contentHash":126,"detectedAt":127,"slug":128},"01KWM4GDWTYASG77AFXFB4MTY1","Breaking","New required field `uuid` added to CI JobRequest RunnerInfo response","The **`uuid`** field (type `string`) has been added to `API_Entities_Ci_JobRequest_RunnerInfo` and marked as **required**. Any client or code generator that validates response payloads against this schema and previously operated without `uuid` will now see validation failures, making this a potentially breaking change for strict schema consumers. Clients that only read the fields they care about and ignore extras are unaffected.","7f0e2c64f11be6fa4308a8cda2f238ab32c4692ba9d7d1470f27c6dcb1cad2a2","2026-07-03T14:00:49.306Z","2026-07-03-new-required-field-uuid-added-to-ci-jobrequest-runnerinfo",{"id":130,"severity":25,"title":131,"summary":132,"contentHash":133,"detectedAt":134,"slug":135},"01KWKK9VBR9H074ATVY8VETW5M","Clarify descriptions for wiki deletion and commit status endpoints","GitLab API documentation was updated to clarify and improve descriptions for several endpoints: wiki deletion endpoints now say \"from\" instead of \"for\", commit status endpoints have more descriptive summaries and details about the functionality, and the web commits public key endpoint has a clearer description. These are documentation-only changes that do not alter request\u002Fresponse behavior or API structure.","7f469eced8fa8f7ef44498dd3ed95fcfe446028f7825f4b660c910339793017a","2026-07-03T09:00:07.928Z","2026-07-03-clarify-descriptions-for-wiki-deletion-and-commit-status",{"id":137,"severity":25,"title":138,"summary":139,"contentHash":140,"detectedAt":141,"slug":142},"01KWKCE55JJNNN5NYC5N96635K","Documentation improvements for group\u002Fproject endpoints","Updated descriptions and summaries for multiple GitLab API endpoints to be more precise and descriptive. Changes include clarifying which endpoints apply to groups vs. projects (especially Debian distribution endpoints), improving response descriptions, and adding more complete operation summaries. No functional changes to request\u002Fresponse schema or endpoint behavior.","d5c547a31b52e9f3e0c91d8cc654dfb99e06496597a636b5cbf6d0375ef83aeb","2026-07-03T07:00:09.010Z","2026-07-03-documentation-improvements-for-group-project-endpoints",{"id":144,"severity":32,"title":145,"summary":146,"contentHash":147,"detectedAt":148,"slug":149},"01KWJV8THT9H02GWN2DK95FN0T","Add project_topic_uploads metrics to geo status response","The GitLab API response schema now includes 15 new optional fields for tracking `project_topic_uploads` synchronization and verification metrics in the geo status endpoint. These new fields follow the same pattern as existing `project_repositories` and `project_uploads` metrics and are purely additive—existing integrations remain unaffected.","0126c4b6e0e1c86d55d6f1f4209dfbc5041fddf66302da479fd90235c8db0170","2026-07-03T02:00:08.506Z","2026-07-03-add-project-topic-uploads-metrics-to-geo-status-response",{"id":151,"severity":32,"title":152,"summary":153,"contentHash":154,"detectedAt":155,"slug":156},"01KWJDHA7MJFK2BE309E09D9S8","Add create_code_review_flow_consent field to group update","A new optional boolean field `create_code_review_flow_consent` has been added to the group update schema. This field records explicit namespace consent for DAP-based Code Review routing and does not affect existing integrations.","76e7cb5b91f72dc0e1aece2a32cd5c0323e35c17cfea8cf6387cb8341af55512","2026-07-02T22:00:06.644Z","2026-07-02-add-create-code-review-flow-consent-field-to-group-update",{"id":158,"severity":32,"title":159,"summary":160,"contentHash":161,"detectedAt":162,"slug":163},"01KWJA3G0R6FQV9ZY7AM728JCV","Add GCS HMAC configuration support to export API","Added a new optional `gcs_hmac_configuration` object to the export API endpoints, enabling S3-interoperability HMAC key authentication for Google Cloud Storage. This provides an additional configuration option alongside existing AWS and S3 methods without breaking existing functionality.","8566dd40da29e5961b812eb56978988b23c4e7ed6068205dcc8a4265d9a9ed96","2026-07-02T21:00:08.088Z","2026-07-02-add-gcs-hmac-configuration-support-to-export-api",{"id":165,"severity":32,"title":166,"summary":167,"contentHash":168,"detectedAt":169,"slug":170},"01KWHNGAYNQ4PRBZ3Q1AQ2QQYQ","Add member_role_id field to project approval rules","Added a new optional response field `member_role_id` (integer, int64 format) to six project approval rule-related API endpoints. This field represents the ID of a custom member role and is purely additive — existing integrations will continue to work unaffected.","0e2ad9356e80bcc09007d51a0a5814387111bd12cb1e9505987618f13cd1f824","2026-07-02T15:00:08.789Z","2026-07-02-add-member-role-id-field-to-project-approval-rules",{"id":172,"severity":32,"title":173,"summary":174,"contentHash":175,"detectedAt":176,"slug":177},"01KWGC9XKR5DSA5BDN4NWGX9YC","Add duo_dependency_bump_breaking_changes_enabled parameter","A new optional boolean parameter `override_params[duo_dependency_bump_breaking_changes_enabled]` has been added to multiple GitLab project APIs, along with a corresponding response field. This enables GitLab Duo AI-powered resolution of breaking changes from dependency bumps and does not affect existing integrations since it is purely optional.","ce6ca5f8772a446849fe9b826bfcb092d63d91aa8683ccc8de7b679157c4cb7a","2026-07-02T03:00:06.904Z","2026-07-02-add-duo-dependency-bump-breaking-changes-enabled-parameter",{"id":179,"severity":25,"title":180,"summary":181,"contentHash":182,"detectedAt":183,"slug":184},"01KWFDD536VWMCPJY99GAGMSVC","Clarify organization parameter accepts paths in API docs","The `organization` parameter documentation was updated to clarify that it accepts both organization IDs and paths (e.g., `1` or `default`), matching the actual API behavior. This is a documentation clarification only with no change to the API's actual functionality or behavior.","74e2969c70d2dbd4e4a5a004592ac1a9445366e75506f431e6f6e3466e34732d","2026-07-01T18:00:07.014Z","2026-07-01-clarify-organization-parameter-accepts-paths-in-api-docs",{"id":186,"severity":32,"title":187,"summary":188,"contentHash":189,"detectedAt":190,"slug":191},"01KWEZNT06ZYVQEHB88KYWVN5T","New Jira Forge integration endpoints","GitLab API adds four new endpoints for Jira Forge integration under two new tag groups (`jira_forge_installation` and `jira_forge_subscriptions`). The changes include PUT and POST operations for installation configuration, namespace subscriptions, and system token registration, along with supporting request\u002Fresponse models. This is purely additive and does not affect existing integrations.","af7d9fd8e35f7f5b069214bc270a79cc363505fae277f44faf7bef549d409ce9","2026-07-01T14:00:10.502Z","2026-07-01-new-jira-forge-integration-endpoints",{"id":193,"severity":25,"title":194,"summary":195,"contentHash":196,"detectedAt":197,"slug":198},"01KWERT430XHP7CJJFSWCC3QAQ","OpenAPI documentation improvements for group and package endpoints","GitLab's OpenAPI specification adds `summary` fields and clarifies descriptions across multiple group management endpoints and package registry endpoints. The changes improve documentation clarity and endpoint discoverability without altering request\u002Fresponse behavior, request parameters, or response schemas.","9c7b2e8a5ca46b6ca01fa744a9b6e3fa96c637577e6e308b86a5f5e843e15746","2026-07-01T12:00:11.872Z","2026-07-01-openapi-documentation-improvements-for-group-and-package",{"id":200,"severity":32,"title":201,"summary":202,"contentHash":203,"detectedAt":204,"slug":205},"01KWDSX5ZERMHVJ40EZYF68AQA","Add optional organization parameter to GitLab API filter","A new optional `organization` parameter has been added to allow filtering by organization ID or comma-separated list of organization IDs. This is a purely additive change that does not affect existing integrations.","462a65b1c64c0bde60eb596d174ee57fa3d5c37f227a381deb2d59c6e6417415","2026-07-01T03:00:06.254Z","2026-07-01-add-optional-organization-parameter-to-gitlab-api-filter",{"id":207,"severity":32,"title":208,"summary":209,"contentHash":210,"detectedAt":211,"slug":212},"01KWDC5Q83GXAMYC70ZB6KKWDS","Add endpoint to remove shared projects from groups","A new DELETE endpoint `DELETE \u002Fapi\u002Fv4\u002Fgroups\u002F{id}\u002Fshared_projects\u002F{project_id}` has been added to allow group owners to remove shared projects. This is a purely additive change that enables new functionality without affecting existing integrations.","078b148bbab1a526a48ddb4a01829790d8fd7b2b7625adf132e1e63e1b9a94c9","2026-06-30T23:00:06.019Z","2026-06-30-add-endpoint-to-remove-shared-projects-from-groups",{"id":214,"severity":123,"title":215,"summary":216,"contentHash":217,"detectedAt":218,"slug":219},"01KWD1WJ6C8CD8XDTYGQHSQ9GZ","MR\u002Fgroup access\u002Fmerge request review fields: int32→int64 and type changes","Multiple response fields have been updated across merge request, group access, and merge request review entities:\n- **`source_project_id`** and **`target_project_id`** on merge request entities changed from `int32` to `int64` format.\n- **`id`**, **`user_id`**, **`group_id`** on group access entities changed from `int32` to `int64`.\n- Several fields on the merge request review entity (`id`, `author_id`, `merge_request_id`) changed from `int32` to `int64`.\n- **`discussion_id`** changed from `type: integer, format: int32` to `type: string` (e.g. a SHA-like hex string).\n- **`commit_id`** changed from `type: integer, format: int32` to `type: string` (e.g. a full commit SHA).\n\nThe `int32`→`int64` changes may break strongly-typed clients that allocated only 32-bit integers. The `discussion_id` and `commit_id` type changes from integer to string are breaking for any client that treats these as numeric values.","b2d88e2df47919c2ca60f157e5d74ef264f8022a100a24189aab30fc3ca5cff8","2026-06-30T20:00:20.172Z","2026-06-30-mr-group-access-merge-request-review-fields-int32-int64-and",{"id":221,"severity":25,"title":222,"summary":223,"contentHash":224,"detectedAt":225,"slug":226},"01KWA55X914PAG1CEAA91Y280K","GitLab API docs clarified for placeholder reassignments and events endpoints","Documentation updates to multiple endpoints to clarify their behavior: **Placeholder reassignments endpoint** summary\u002Fdescription reworded from \"pending placeholder assignments\" to \"pending reassignments\"; **POST issue links endpoint** fixed grammar (\"relation\" → \"relationship\"); **Events endpoints** (`GET \u002Fapi\u002Fv4\u002Fevents` and `GET \u002Fapi\u002Fv4\u002Fusers\u002F{id}\u002Fevents`) updated with more detailed descriptions noting they exclude epics\u002Fmerge requests and return bulk push events with limited details. No API behavior changes or breaking modifications.","57ae983a208af8010c086bed8f62d482f0ed870237b1efa60b676f2b46413a37","2026-06-29T17:00:08.865Z","2026-06-29-gitlab-api-docs-clarified-for-placeholder-reassignments-and",{"id":228,"severity":32,"title":229,"summary":230,"contentHash":231,"detectedAt":232,"slug":233},"01KW9QEGG6FMKST6RDHYCHYW75","Add new \u002Ftrigger_jobs endpoint; deprecate \u002Fbridges","A new endpoint `GET \u002Fapi\u002Fv4\u002Fprojects\u002F{id}\u002Fpipelines\u002F{pipeline_id}\u002Ftrigger_jobs` is added to replace the deprecated `GET \u002Fapi\u002Fv4\u002Fprojects\u002F{id}\u002Fpipelines\u002F{pipeline_id}\u002Fbridges` endpoint. The bridges endpoint is now marked deprecated (still functional) with a note to use trigger_jobs instead. Clients have a migration path and both endpoints work concurrently.","950f52319a176d33199652482b2843767c16db49b969ac34f38abc6a248b0575","2026-06-29T13:00:10.630Z","2026-06-29-add-new-trigger-jobs-endpoint-deprecate-bridges",{"id":235,"severity":32,"title":236,"summary":237,"contentHash":238,"detectedAt":239,"slug":240},"01KW2HDM65B8N3C123YSYJNVP8","Add member_role_id and member_role_name to group member response","Two new optional response fields `member_role_id` (integer) and `member_role_name` (string) have been added to the group member API response. This is a purely additive change that provides additional member role metadata without affecting existing integrations.","bb6e938178a9aac49154b80cbf36372337b9e3865bd1eedccc8cfecf3411f7ad","2026-06-26T18:00:09.157Z","2026-06-26-add-member-role-id-and-member-role-name-to-group-member",{"id":242,"severity":32,"title":243,"summary":244,"contentHash":245,"detectedAt":246,"slug":247},"01KW0TFTQ1PC717ASMY0WSJZ3V","Add last_used_ips field to personal access token responses","The `last_used_ips` field is now defined with explicit `items: {type: string}` schema and a description in the OpenAPI spec for personal access token responses. One occurrence made `last_used_ips` optional (removed from required list), while another added the schema definition. This enhances documentation and API clarity without breaking existing clients—the field was already returned but is now properly specified.","051278ef38de71fc5a2e7c99a77c3f40c1cf042e9b31e3ffb8648fb71a6871c8","2026-06-26T02:00:09.697Z","2026-06-26-add-last-used-ips-field-to-personal-access-token-responses",{"id":249,"severity":32,"title":250,"summary":251,"contentHash":252,"detectedAt":253,"slug":254},"01KW0G659KD804VZRHR17H7VTP","Add uuid field to organization response","A new required `uuid` field has been added to the organization response schema. This is an additive change that adds a new required response field to organization endpoints, which will not break existing clients that ignore unknown response properties.","c6fae1146493e20d3059fd6811bad2fad33302dd71bc6f0e3661ebc73af47dc4","2026-06-25T23:00:07.091Z","2026-06-25-add-uuid-field-to-organization-response",{"id":256,"severity":32,"title":257,"summary":258,"contentHash":259,"detectedAt":260,"slug":261},"01KVZR58M6PDCJ0E36YM2H6GHE","Expand integer fields from int32 to int64 format","Multiple response fields across various GitLab API entities have had their OpenAPI type format changed from `int32` to `int64`. This change increases the range of values these fields can represent without breaking existing clients, as `int64` is a superset of `int32`. All affected fields are in response objects and maintain backward compatibility.","471ff41ab514b80f5fca9d961fe347e95b0bc52ef1f169d3ad10c1656a090867","2026-06-25T16:00:11.910Z","2026-06-25-expand-integer-fields-from-int32-to-int64-format",{"id":263,"severity":25,"title":264,"summary":265,"contentHash":266,"detectedAt":267,"slug":268},"01KVXXSDX2AYWJZM2JDXAKE7F2","Update integer format specs in API schema","Three integer fields in the GitLab API schema have had their format specification changed from `int32` to `int64`: `id`, `project_id`, and `build_id`. This reflects the actual data types returned by the API and does not change runtime behavior for clients already handling 64-bit integers correctly.","63d3d33a1a112d533065d92c4c07167b631c3a26dff13761c2a1d2505ec1985a","2026-06-24T23:00:06.690Z","2026-06-24-update-integer-format-specs-in-api-schema",{"id":270,"severity":25,"title":271,"summary":272,"contentHash":273,"detectedAt":274,"slug":275},"01KVXPXQZCZJ58PDPDG8CXCMX2","Update integer format from int32 to int64 in bulk import schemas","Several ID fields in bulk import–related response schemas changed their OpenAPI format annotation from `int32` to `int64`. This clarifies the actual data type and does not affect runtime behavior or client integration — the underlying integers remain unchanged and compatible with existing code.","49ae6cd69112e9997b4f3d3d14abf34e0d950a87c59d1cf0e2c37cb843e8b92d","2026-06-24T21:00:08.044Z","2026-06-24-update-integer-format-from-int32-to-int64-in-bulk-import",{"id":277,"severity":32,"title":278,"summary":279,"contentHash":280,"detectedAt":281,"slug":282},"01KVXKFX59WCJGYZCZW540SWSA","Add vulnerability remediation upload metrics to usage API","The GitLab API now includes new fields for vulnerability remediation upload metrics in the usage statistics response. These 16 new optional fields track counts, checksums, syncing, and verification status for vulnerability remediation uploads, mirroring the existing vulnerability export upload metrics structure. This is a purely additive change that does not affect existing integrations.","63de1376ab6d6db12bf254290363116331e332c33423a0d9ecaf6ecaccc7dd3b","2026-06-24T20:00:08.873Z","2026-06-24-add-vulnerability-remediation-upload-metrics-to-usage-api",{"id":284,"severity":25,"title":285,"summary":286,"contentHash":287,"detectedAt":288,"slug":289},"01KVX5RKMBC25FK431VQ5GTX31","Reorganize package-type API tags in OpenAPI spec","The OpenAPI specification has reorganized the `packages` tag into multiple package-type-specific tags: `packages_debian`, `packages_npm`, `packages_conan`, `packages_cargo`, `packages_composer`, `packages_nuget`, `packages_pypi`, `packages_helm`, `packages_rpm`, and `packages_rubygem`. All endpoints remain functional and unchanged; this restructuring only affects API documentation organization and tooling that processes tags.","b9d572b76d2a0f5804be124027bd7c8319b594a85105a52aa0867f9dd6256d08","2026-06-24T16:00:13.963Z","2026-06-24-reorganize-package-type-api-tags-in-openapi-spec",{"id":291,"severity":32,"title":292,"summary":293,"contentHash":294,"detectedAt":295,"slug":296},"01KVW3DSGW9P8STW0CTWXAKMR4","Add read_agent_artifacts OAuth scope","A new OAuth scope `read_agent_artifacts` has been added to the GitLab API specification. This is a new optional capability that applications can request; existing integrations are unaffected.","0f3fcfc018675b959444937fd26ce304e4fc46e54ab3c31438509ef2b7e75c7c","2026-06-24T06:00:07.964Z","2026-06-24-add-read-agent-artifacts-oauth-scope",{"id":298,"severity":123,"title":299,"summary":300,"contentHash":301,"detectedAt":302,"slug":303},"01KVVS4N9DH2DH7DZRZ4V9G0K3","Multiple response fields widened from int32 to int64; Agent\u002FCluster field types corrected","Several categories of changes are present in this diff:\n\n- **`int32` → `int64`** on `id`, `project_id`, and `pipeline_id` fields across many CI\u002FCD, pipeline, environment, runner, and deployment response schemas. Strictly speaking this is a widening (larger value range), but strongly-typed clients that generated code from `int32` may overflow or need recompilation.\n- **`type: string` → `type: integer` (int64)** for `id`, `agent_id`, and `created_by_user_id` in `API_Entities_Clusters_AgentTokenBasic`, `API_Entities_Clusters_AgentToken`, `API_Entities_Clusters_AgentTokenWithToken`, and `API_Entities_Clusters_Agent`. Any client that parsed these fields as strings will break.\n- **`is_receptive`** in `API_Entities_Clusters_Agent` changed from `type: string` to `type: boolean` — string-parsing clients will break.\n- **`created_at` \u002F `last_used_at`** in Agent\u002FToken schemas gained `format: date-time` (additive but narrows expected format).\n- **`API_Entities_DiscoveredClusters`** fields `groups` and `projects` changed from `type: string` to `type: object` — clients treating these as strings will break.","8632bc0f587b0dbcc6aa85cf039b7366bf3fc23eebf78ac3c57671d11f882b02","2026-06-24T03:00:22.957Z","2026-06-24-multiple-response-fields-widened-from-int32-to-int64-agent",{"id":305,"severity":25,"title":306,"summary":307,"contentHash":308,"detectedAt":309,"slug":310},"01KVTFZ2CR47MJ4Z2GA3A8YXRT","Update integer format from int32 to int64 in API specs","The OpenAPI specification was updated to correctly describe integer fields as `int64` format instead of `int32` in two objects. This is a documentation correction that clarifies the actual data type constraints without changing the runtime API behavior — clients are already receiving and should handle full 64-bit integers.","0dc13b62afb45c4467fb0d29e65b7cde89a0dd4f442f6f4e8547fd74076784cd","2026-06-23T15:00:48.152Z","2026-06-23-update-integer-format-from-int32-to-int64-in-api-specs",{"id":312,"severity":25,"title":313,"summary":314,"contentHash":315,"detectedAt":316,"slug":317},"01KVSYRGRW8WNKRNKTB6PQXMSK","Integer fields changed from int32 to int64 format","Multiple integer fields across GitLab API responses have been updated from `int32` to `int64` format specification. This change clarifies the actual range of acceptable values for ID and numeric fields and does not affect runtime behavior or existing integrations, as the fields themselves remain integers and JSON does not distinguish between int32 and int64 at the protocol level.","09f4f11ddd8e6efed5068f3760ea5471315898c2662eff7703e712b14b88ccf7","2026-06-23T10:00:07.708Z","2026-06-23-integer-fields-changed-from-int32-to-int64-format",{"id":319,"severity":32,"title":320,"summary":321,"contentHash":322,"detectedAt":323,"slug":324},"01KVSVAQE2AZJSXS6N7DDYB32M","Add AI settings schema and widen integer field formats","The GitLab OpenAPI spec adds a new `ai_settings` field to the application settings response (referencing a new `API_Entities_AiSettings` schema) and widens the numeric format of several integer fields from `int32` to `int64`. The new `AI_Entities_AiSettings` schema includes 14 new boolean\u002Finteger fields for AI feature configuration. The int32→int64 changes are backward-compatible widening of the numeric range.","0894fa573fdacdd1099f979feab74b9f5041c98877cb07f57c1498cdcad8e13a","2026-06-23T09:00:10.050Z","2026-06-23-add-ai-settings-schema-and-widen-integer-field-formats",{"id":326,"severity":32,"title":327,"summary":328,"contentHash":329,"detectedAt":330,"slug":331},"01KVSDK56D8KWK7M4VXSNYS6KH","Expand audit event endpoint access to Developer role","The **GET \u002Fapi\u002Fv4\u002Fprojects\u002F{id}\u002Faudit_events\u002F{audit_event_id}** endpoint now allows access for users with the Developer role (or higher), previously restricted to Maintainer or Owner only. This broadens access to the endpoint, enabling more team members to retrieve project audit events without breaking existing integrations.","e5f34ad673255f56b8d3bce83b287f8cca49e47337489b74bee48bf06e49871b","2026-06-23T05:00:06.221Z","2026-06-23-expand-audit-event-endpoint-access-to-developer-role",{"id":333,"severity":25,"title":334,"summary":335,"contentHash":336,"detectedAt":337,"slug":338},"01KVREPFGE4B2TTM9G8TRQNBY8","Change integer ID format from int32 to int64 in API schema","The OpenAPI specification was updated to change the `format` property of integer `id` fields from `int32` to `int64` across multiple schema objects. This reflects the actual data type representation but does not alter the API behavior or response structure; existing integrations will continue to work unchanged.","efba997bcefc62579e6b576f6f433aa5ffbdfbdc1e6fa176d55ba2fa68bd1a5b","2026-06-22T20:00:09.230Z","2026-06-22-change-integer-id-format-from-int32-to-int64-in-api-schema",{"id":340,"severity":123,"title":341,"summary":342,"contentHash":343,"detectedAt":344,"slug":345},"01KVR7V1Z0S04VW67ZDP6RYARF","project_id format changed from int32 to int64 in storage response","The `project_id` field's format was updated from `int32` to `int64` in a response schema. Clients that deserialize this field into a 32-bit integer type will silently overflow or error for project IDs exceeding 2,147,483,647, which is a real concern for large GitLab instances. Any generated SDK code or typed client that mapped `int32` will need to be updated.","3be1648a6330a819baf4b5b806f80be7332c38d66142d007504474a45b023f59","2026-06-22T18:00:19.168Z","2026-06-22-project-id-format-changed-from-int32-to-int64-in-storage",{"id":347,"severity":25,"title":348,"summary":349,"contentHash":350,"detectedAt":351,"slug":352},"01KVR0Z8Y1BDMXXM2K7W5T8YXM","Widen integer fields from int32 to int64 in package\u002Frelease schemas","Multiple `id` and `project_id` fields across package registry, release, and cleanup policy schemas have had their OpenAPI `format` widened from `int32` to `int64`. This is a spec correction to accurately reflect that GitLab IDs can exceed the 32-bit integer range. Most API clients do not enforce the `format` hint at runtime, so this is unlikely to break existing integrations — but generated client code (e.g. from OpenAPI codegen) may produce different types (`int` vs `long`\u002F`int64`) after regeneration.","a815a90ead11333b1bf57827f597491e106f1598f9b4ed66a963932aacd8964e","2026-06-22T16:00:17.345Z","2026-06-22-widen-integer-fields-from-int32-to-int64-in-package-release",{"id":354,"severity":25,"title":355,"summary":356,"contentHash":357,"detectedAt":358,"slug":359},"01KVQK7HF1YTJ2PZKY7TCZ5X3C","Update integer format from int32 to int64 in OpenAPI schema","Multiple integer fields in the OpenAPI specification have been changed from `int32` format to `int64` format. This is a documentation\u002Fschema update that clarifies the actual range of values these fields support; it does not break existing integrations since clients already handle these values correctly.","462612550a517db551e7e09bed10ee7d46e8521f1810391221028a02a372217d","2026-06-22T12:00:08.161Z","2026-06-22-update-integer-format-from-int32-to-int64-in-openapi-schema",{"id":361,"severity":32,"title":362,"summary":363,"contentHash":364,"detectedAt":365,"slug":366},"01KVQ8XYAFX58GM2M7BVJNSH1P","Add merge_train_enforcement field to project settings","A new optional response field `merge_train_enforcement` has been added to the project settings schema. This field is a string enum that can be one of `allow_bypass`, `enforce_for_all_users`, or `enforce_with_owner_override`, allowing GitLab to communicate merge train enforcement policies in API responses.","b977e2631af44ef083d63db344aec5f738f0a5bf77187ed82697ef55376c95e8","2026-06-22T09:00:07.887Z","2026-06-22-add-merge-train-enforcement-field-to-project-settings",{"id":368,"severity":32,"title":369,"summary":370,"contentHash":371,"detectedAt":372,"slug":373},"01KVPQRJKQSWHTQR4F7JDQDJFV","Add destroy_package capability to user permissions","Added a new optional `destroy_package` boolean field to the user capabilities response schema. This is a new capability that can be returned in API responses to indicate whether a user has permission to destroy packages, and does not affect existing clients.","f52359fb7c7cebdf03ca32b857c5e9d437794c5590878f54e539416524a31ff6","2026-06-22T04:00:06.263Z","2026-06-22-add-destroy-package-capability-to-user-permissions"]