Skip to content
GitLab
菜单
为什么选择 GitLab
定价
联系销售
探索
为什么选择 GitLab
定价
联系销售
探索
登录
获取免费试用
主导航
搜索或转到…
项目
GitLab
管理
动态
成员
标记
计划
议题
议题看板
里程碑
迭代
需求
代码
合并请求
仓库
分支
提交
标签
仓库图
比较修订版本
代码片段
锁定的文件
构建
流水线
作业
流水线计划
测试用例
产物
部署
发布
Package registry
Container registry
模型注册表
运维
环境
Terraform 模块
监控
事件
服务台
分析
价值流分析
贡献者分析
CI/CD 分析
仓库分析
代码评审分析
议题分析
洞察
模型实验
效能分析
帮助
帮助
支持
GitLab 文档
比较 GitLab 各版本
社区论坛
为极狐GitLab 提交贡献
提交反馈
隐私声明
快捷键
?
新增功能
4
代码片段
群组
项目
显示更多面包屑
gitlab-cn
GitLab
提交
8f217d48
未验证
提交
8f217d48
编辑于
11 months ago
作者:
Adil Farrukh
提交者:
GitLab
11 months ago
浏览文件
操作
下载
补丁
差异文件
GraphQL API access is enforced through documented token types only
上级
31db38a5
No related branches found
分支 包含提交
No related tags found
标签 包含提交
无相关合并请求
变更
2
隐藏空白变更内容
行内
左右并排
显示
2 个更改的文件
data/deprecations/17-0-graphql-strict-token-enforcement copy.yml
+16
-0
16 个添加, 0 个删除
...precations/17-0-graphql-strict-token-enforcement copy.yml
doc/update/deprecations.md
+17
-0
17 个添加, 0 个删除
doc/update/deprecations.md
有
33 个添加
和
0 个删除
data/deprecations/17-0-graphql-strict-token-enforcement copy.yml
0 → 100644
+
16
−
0
浏览文件 @
8f217d48
-
title
:
"
GraphQL
API
access
through
unsupported
methods"
# The milestones for the deprecation announcement, and the removal.
removal_milestone
:
"
17.0"
announcement_milestone
:
"
17.0"
# Change breaking_change to false if needed.
breaking_change
:
true
# The stage and GitLab username of the person reporting the change,
# and a link to the deprecation issue
reporter
:
adil.farrukh
stage
:
govern
issue_url
:
https://gitlab.com/gitlab-org/gitlab/-/issues/442520
body
:
|
# (required) Don't change this line.
From GitLab 17.0, we limiting access to GraphQL to only through the
[already documented supported token types](https://docs.gitlab.com/ee/api/graphql/#token-authentication).
For customers already using documented and supported token types, there are no breaking changes.
此差异已折叠。
点击以展开。
doc/update/deprecations.md
+
17
−
0
浏览文件 @
8f217d48
...
@@ -1234,6 +1234,23 @@ Runners generate provenance metadata and currently defaults to generating statem
...
@@ -1234,6 +1234,23 @@ Runners generate provenance metadata and currently defaults to generating statem
<div class="deprecation breaking-change" data-milestone="17.0">
<div class="deprecation breaking-change" data-milestone="17.0">
### GraphQL API access through unsupported methods
<div class="deprecation-notes">
- Announced in GitLab <span class="milestone">17.0</span>
- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change))
- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/442520).
</div>
From GitLab 17.0, we limiting access to GraphQL to only through the
[already documented supported token types](https://docs.gitlab.com/ee/api/graphql/#token-authentication).
For customers already using documented and supported token types, there are no breaking changes.
</div>
<div class="deprecation breaking-change" data-milestone="17.0">
### GraphQL deprecation of `
dependencyProxyTotalSizeInBytes
` field
### GraphQL deprecation of `
dependencyProxyTotalSizeInBytes
` field
<div class="deprecation-notes">
<div class="deprecation-notes">
...
...
此差异已折叠。
点击以展开。
预览
0%
加载中
请重试
或
添加新附件
.
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
保存评论
取消
想要评论请
注册
或
登录