Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
GitLab Bot
parent
8ec882085e
commit
092e41f566
|
|
@ -1354,7 +1354,6 @@ Layout/LineLength:
|
|||
- 'ee/app/models/ee/merge_request_diff.rb'
|
||||
- 'ee/app/models/ee/milestone_release.rb'
|
||||
- 'ee/app/models/ee/namespace.rb'
|
||||
- 'ee/app/models/ee/namespace/root_storage_size.rb'
|
||||
- 'ee/app/models/ee/packages/package_file.rb'
|
||||
- 'ee/app/models/ee/pages_deployment.rb'
|
||||
- 'ee/app/models/ee/project.rb'
|
||||
|
|
@ -2444,9 +2443,7 @@ Layout/LineLength:
|
|||
- 'ee/spec/models/ee/iterations/cadence_spec.rb'
|
||||
- 'ee/spec/models/ee/lfs_object_spec.rb'
|
||||
- 'ee/spec/models/ee/merge_request_diff_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace/root_storage_size_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace/root_storage_statistics_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace_limit_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace_statistics_spec.rb'
|
||||
- 'ee/spec/models/ee/preloaders/group_policy_preloader_spec.rb'
|
||||
|
|
|
|||
|
|
@ -55,7 +55,6 @@ Layout/MultilineOperationIndentation:
|
|||
- 'ee/app/models/approval_project_rule.rb'
|
||||
- 'ee/app/models/concerns/ee/issuable.rb'
|
||||
- 'ee/app/models/ee/namespace.rb'
|
||||
- 'ee/app/models/ee/namespace/root_storage_size.rb'
|
||||
- 'ee/app/models/ee/project.rb'
|
||||
- 'ee/app/models/ee/user.rb'
|
||||
- 'ee/app/models/vulnerabilities/finding_signature.rb'
|
||||
|
|
|
|||
|
|
@ -299,7 +299,6 @@ Rails/SkipsModelValidations:
|
|||
- 'ee/spec/models/ee/groups/feature_setting_spec.rb'
|
||||
- 'ee/spec/models/ee/iteration_spec.rb'
|
||||
- 'ee/spec/models/ee/iterations/cadence_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace_limit_spec.rb'
|
||||
- 'ee/spec/models/ee/vulnerability_spec.rb'
|
||||
- 'ee/spec/models/geo_node_spec.rb'
|
||||
- 'ee/spec/models/geo_node_status_spec.rb'
|
||||
|
|
|
|||
|
|
@ -507,10 +507,7 @@ RSpec/ContextWording:
|
|||
- 'ee/spec/models/ee/incident_management/project_incident_management_setting_spec.rb'
|
||||
- 'ee/spec/models/ee/iteration_spec.rb'
|
||||
- 'ee/spec/models/ee/iterations/cadence_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace/root_storage_size_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace/storage/notification_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace_ci_cd_setting_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace_limit_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace_spec.rb'
|
||||
- 'ee/spec/models/ee/notification_setting_spec.rb'
|
||||
- 'ee/spec/models/ee/personal_access_token_spec.rb'
|
||||
|
|
|
|||
|
|
@ -41,7 +41,6 @@ RSpec/ScatteredLet:
|
|||
- 'ee/spec/models/ci/minutes/notification_spec.rb'
|
||||
- 'ee/spec/models/ci/pipeline_spec.rb'
|
||||
- 'ee/spec/models/ee/ci/build_dependencies_spec.rb'
|
||||
- 'ee/spec/models/ee/namespace/root_storage_size_spec.rb'
|
||||
- 'ee/spec/models/label_note_spec.rb'
|
||||
- 'ee/spec/models/sca/license_compliance_spec.rb'
|
||||
- 'ee/spec/policies/merge_request_policy_spec.rb'
|
||||
|
|
|
|||
|
|
@ -479,8 +479,6 @@ Style/ClassAndModuleChildren:
|
|||
- 'ee/app/models/concerns/geo/syncable.rb'
|
||||
- 'ee/app/models/dast/profile_schedule.rb'
|
||||
- 'ee/app/models/ee/ci/job_artifact.rb'
|
||||
- 'ee/app/models/ee/namespace/root_excess_storage_size.rb'
|
||||
- 'ee/app/models/ee/namespace/root_storage_size.rb'
|
||||
- 'ee/app/models/elastic/reindexing_slice.rb'
|
||||
- 'ee/app/models/elastic/reindexing_subtask.rb'
|
||||
- 'ee/app/models/elastic/reindexing_task.rb'
|
||||
|
|
|
|||
|
|
@ -533,7 +533,6 @@ Style/IfUnlessModifier:
|
|||
- 'ee/app/models/ee/member.rb'
|
||||
- 'ee/app/models/ee/milestone_release.rb'
|
||||
- 'ee/app/models/ee/namespace.rb'
|
||||
- 'ee/app/models/ee/namespace/root_storage_size.rb'
|
||||
- 'ee/app/models/ee/project.rb'
|
||||
- 'ee/app/models/ee/project_feature.rb'
|
||||
- 'ee/app/models/ee/project_team.rb'
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
b731241d770f8cd1e8b81f48d8a011f0383b4b48
|
||||
448304d500ab91dca193a21094319d38e22f60a7
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ export default () => ({
|
|||
attrs: { lang: 'math' },
|
||||
},
|
||||
// Matches HTML generated by Banzai::Filter::MermaidFilter,
|
||||
// after being transformed by app/assets/javascripts/behaviors/markdown/render_mermaid.js
|
||||
// after being transformed by app/assets/javascripts/behaviors/markdown/render_sandboxed_mermaid.js
|
||||
{
|
||||
tag: 'svg.mermaid',
|
||||
preserveWhitespace: 'full',
|
||||
|
|
|
|||
|
|
@ -1,231 +0,0 @@
|
|||
import $ from 'jquery';
|
||||
import { once, countBy } from 'lodash';
|
||||
import createFlash from '~/flash';
|
||||
import { darkModeEnabled } from '~/lib/utils/color_utils';
|
||||
import { __, sprintf } from '~/locale';
|
||||
import { unrestrictedPages } from './constants';
|
||||
|
||||
// Renders diagrams and flowcharts from text using Mermaid in any element with the
|
||||
// `js-render-mermaid` class.
|
||||
//
|
||||
// Example markup:
|
||||
//
|
||||
// <pre class="js-render-mermaid">
|
||||
// graph TD;
|
||||
// A-- > B;
|
||||
// A-- > C;
|
||||
// B-- > D;
|
||||
// C-- > D;
|
||||
// </pre>
|
||||
//
|
||||
|
||||
// This is an arbitrary number; Can be iterated upon when suitable.
|
||||
const MAX_CHAR_LIMIT = 2000;
|
||||
// Max # of mermaid blocks that can be rendered in a page.
|
||||
const MAX_MERMAID_BLOCK_LIMIT = 50;
|
||||
// Max # of `&` allowed in Chaining of links syntax
|
||||
const MAX_CHAINING_OF_LINKS_LIMIT = 30;
|
||||
// Keep a map of mermaid blocks we've already rendered.
|
||||
const elsProcessingMap = new WeakMap();
|
||||
let renderedMermaidBlocks = 0;
|
||||
|
||||
let mermaidModule = {};
|
||||
|
||||
export function initMermaid(mermaid) {
|
||||
let theme = 'neutral';
|
||||
|
||||
if (darkModeEnabled()) {
|
||||
theme = 'dark';
|
||||
}
|
||||
|
||||
mermaid.initialize({
|
||||
// mermaid core options
|
||||
mermaid: {
|
||||
startOnLoad: false,
|
||||
},
|
||||
// mermaidAPI options
|
||||
theme,
|
||||
flowchart: {
|
||||
useMaxWidth: true,
|
||||
htmlLabels: true,
|
||||
},
|
||||
secure: ['secure', 'securityLevel', 'startOnLoad', 'maxTextSize', 'htmlLabels'],
|
||||
securityLevel: 'strict',
|
||||
});
|
||||
|
||||
return mermaid;
|
||||
}
|
||||
|
||||
function importMermaidModule() {
|
||||
return import(/* webpackChunkName: 'mermaid' */ 'mermaid')
|
||||
.then(({ default: mermaid }) => {
|
||||
mermaidModule = initMermaid(mermaid);
|
||||
})
|
||||
.catch((err) => {
|
||||
createFlash({
|
||||
message: sprintf(__("Can't load mermaid module: %{err}"), { err }),
|
||||
});
|
||||
// eslint-disable-next-line no-console
|
||||
console.error(err);
|
||||
});
|
||||
}
|
||||
|
||||
function shouldLazyLoadMermaidBlock(source) {
|
||||
/**
|
||||
* If source contains `&`, which means that it might
|
||||
* contain Chaining of links a new syntax in Mermaid.
|
||||
*/
|
||||
if (countBy(source)['&'] > MAX_CHAINING_OF_LINKS_LIMIT) {
|
||||
return true;
|
||||
}
|
||||
|
||||
return false;
|
||||
}
|
||||
|
||||
function fixElementSource(el) {
|
||||
// Mermaid doesn't like `<br />` tags, so collapse all like tags into `<br>`, which is parsed correctly.
|
||||
const source = el.textContent.replace(/<br\s*\/>/g, '<br>');
|
||||
|
||||
// Remove any extra spans added by the backend syntax highlighting.
|
||||
Object.assign(el, { textContent: source });
|
||||
|
||||
return { source };
|
||||
}
|
||||
|
||||
function renderMermaidEl(el) {
|
||||
mermaidModule.init(undefined, el, (id) => {
|
||||
const source = el.textContent;
|
||||
const svg = document.getElementById(id);
|
||||
|
||||
// As of https://github.com/knsv/mermaid/commit/57b780a0d,
|
||||
// Mermaid will make two init callbacks:one to initialize the
|
||||
// flow charts, and another to initialize the Gannt charts.
|
||||
// Guard against an error caused by double initialization.
|
||||
if (svg.classList.contains('mermaid')) {
|
||||
return;
|
||||
}
|
||||
|
||||
svg.classList.add('mermaid');
|
||||
|
||||
// pre > code > svg
|
||||
svg.closest('pre').replaceWith(svg);
|
||||
|
||||
// We need to add the original source into the DOM to allow Copy-as-GFM
|
||||
// to access it.
|
||||
const sourceEl = document.createElement('text');
|
||||
sourceEl.classList.add('source');
|
||||
sourceEl.setAttribute('display', 'none');
|
||||
sourceEl.textContent = source;
|
||||
|
||||
svg.appendChild(sourceEl);
|
||||
});
|
||||
}
|
||||
|
||||
function renderMermaids($els) {
|
||||
if (!$els.length) return;
|
||||
|
||||
const pageName = document.querySelector('body').dataset.page;
|
||||
|
||||
// A diagram may have been truncated in search results which will cause errors, so abort the render.
|
||||
if (pageName === 'search:show') return;
|
||||
|
||||
importMermaidModule()
|
||||
.then(() => {
|
||||
let renderedChars = 0;
|
||||
|
||||
$els.each((i, el) => {
|
||||
// Skipping all the elements which we've already queued in requestIdleCallback
|
||||
if (elsProcessingMap.has(el)) {
|
||||
return;
|
||||
}
|
||||
|
||||
const { source } = fixElementSource(el);
|
||||
/**
|
||||
* Restrict the rendering to a certain amount of character
|
||||
* and mermaid blocks to prevent mermaidjs from hanging
|
||||
* up the entire thread and causing a DoS.
|
||||
*/
|
||||
if (
|
||||
!unrestrictedPages.includes(pageName) &&
|
||||
((source && source.length > MAX_CHAR_LIMIT) ||
|
||||
renderedChars > MAX_CHAR_LIMIT ||
|
||||
renderedMermaidBlocks >= MAX_MERMAID_BLOCK_LIMIT ||
|
||||
shouldLazyLoadMermaidBlock(source))
|
||||
) {
|
||||
const html = `
|
||||
<div class="alert gl-alert gl-alert-warning alert-dismissible lazy-render-mermaid-container js-lazy-render-mermaid-container fade show" role="alert">
|
||||
<div>
|
||||
<div class="display-flex">
|
||||
<div>${__(
|
||||
'Warning: Displaying this diagram might cause performance issues on this page.',
|
||||
)}</div>
|
||||
<div class="gl-alert-actions">
|
||||
<button class="js-lazy-render-mermaid btn gl-alert-action btn-confirm btn-md gl-button">Display</button>
|
||||
</div>
|
||||
</div>
|
||||
<button type="button" class="close" data-dismiss="alert" aria-label="Close">
|
||||
<span aria-hidden="true">×</span>
|
||||
</button>
|
||||
</div>
|
||||
</div>
|
||||
`;
|
||||
|
||||
const $parent = $(el).parent();
|
||||
|
||||
if (!$parent.hasClass('lazy-alert-shown')) {
|
||||
$parent.after(html);
|
||||
$parent.addClass('lazy-alert-shown');
|
||||
}
|
||||
|
||||
return;
|
||||
}
|
||||
|
||||
renderedChars += source.length;
|
||||
renderedMermaidBlocks += 1;
|
||||
|
||||
const requestId = window.requestIdleCallback(() => {
|
||||
renderMermaidEl(el);
|
||||
});
|
||||
|
||||
elsProcessingMap.set(el, requestId);
|
||||
});
|
||||
})
|
||||
.catch((err) => {
|
||||
createFlash({
|
||||
message: sprintf(__('Encountered an error while rendering: %{err}'), { err }),
|
||||
});
|
||||
// eslint-disable-next-line no-console
|
||||
console.error(err);
|
||||
});
|
||||
}
|
||||
|
||||
const hookLazyRenderMermaidEvent = once(() => {
|
||||
$(document.body).on('click', '.js-lazy-render-mermaid', function eventHandler() {
|
||||
const parent = $(this).closest('.js-lazy-render-mermaid-container');
|
||||
const pre = parent.prev();
|
||||
|
||||
const el = pre.find('.js-render-mermaid');
|
||||
|
||||
parent.remove();
|
||||
|
||||
renderMermaidEl(el);
|
||||
});
|
||||
});
|
||||
|
||||
export default function renderMermaid($els) {
|
||||
if (!$els.length) return;
|
||||
|
||||
const visibleMermaids = $els.filter(function filter() {
|
||||
return $(this).closest('details').length === 0 && $(this).is(':visible');
|
||||
});
|
||||
|
||||
renderMermaids(visibleMermaids);
|
||||
|
||||
$els.closest('details').one('toggle', function toggle() {
|
||||
if (this.open) {
|
||||
renderMermaids($(this).find('.js-render-mermaid'));
|
||||
}
|
||||
});
|
||||
|
||||
hookLazyRenderMermaidEvent();
|
||||
}
|
||||
|
|
@ -140,6 +140,7 @@
|
|||
"WorkItemWidgetAssignees",
|
||||
"WorkItemWidgetDescription",
|
||||
"WorkItemWidgetHierarchy",
|
||||
"WorkItemWidgetLabels",
|
||||
"WorkItemWidgetStartAndDueDate",
|
||||
"WorkItemWidgetVerificationStatus",
|
||||
"WorkItemWidgetWeight"
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ export default {
|
|||
directives: {
|
||||
GlModalDirective,
|
||||
},
|
||||
inject: ['groupPath', 'groupId', 'noManifestsIllustration'],
|
||||
inject: ['groupPath', 'groupId', 'noManifestsIllustration', 'canClearCache'],
|
||||
i18n: {
|
||||
proxyImagePrefix: s__('DependencyProxy|Dependency Proxy image prefix'),
|
||||
copyImagePrefixText: s__('DependencyProxy|Copy prefix'),
|
||||
|
|
@ -114,7 +114,7 @@ export default {
|
|||
);
|
||||
},
|
||||
showDeleteDropdown() {
|
||||
return this.group.dependencyProxyManifests?.nodes.length > 0;
|
||||
return this.group.dependencyProxyManifests?.nodes.length > 0 && this.canClearCache;
|
||||
},
|
||||
showDependencyProxyImagePrefix() {
|
||||
return this.group.dependencyProxyImagePrefix?.length > 0;
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
import Vue from 'vue';
|
||||
import { parseBoolean } from '~/lib/utils/common_utils';
|
||||
import app from '~/packages_and_registries/dependency_proxy/app.vue';
|
||||
import { apolloProvider } from '~/packages_and_registries/dependency_proxy/graphql';
|
||||
import Translate from '~/vue_shared/translate';
|
||||
|
|
@ -10,12 +11,15 @@ export const initDependencyProxyApp = () => {
|
|||
if (!el) {
|
||||
return null;
|
||||
}
|
||||
const { ...dataset } = el.dataset;
|
||||
const { groupPath, groupId, noManifestsIllustration, canClearCache } = el.dataset;
|
||||
return new Vue({
|
||||
el,
|
||||
apolloProvider,
|
||||
provide: {
|
||||
...dataset,
|
||||
groupPath,
|
||||
groupId,
|
||||
noManifestsIllustration,
|
||||
canClearCache: parseBoolean(canClearCache),
|
||||
},
|
||||
render(createElement) {
|
||||
return createElement(app);
|
||||
|
|
|
|||
|
|
@ -1,7 +1,13 @@
|
|||
<script>
|
||||
import { GlFormGroup } from '@gitlab/ui';
|
||||
import NamespaceSelect from '~/vue_shared/components/namespace_select/namespace_select.vue';
|
||||
import produce from 'immer';
|
||||
import ConfirmDanger from '~/vue_shared/components/confirm_danger/confirm_danger.vue';
|
||||
import NamespaceSelect from '~/vue_shared/components/namespace_select/namespace_select.vue';
|
||||
import { getIdFromGraphQLId } from '~/graphql_shared/utils';
|
||||
import { DEBOUNCE_DELAY } from '~/vue_shared/components/filtered_search_bar/constants';
|
||||
import searchNamespacesWhereUserCanTransferProjects from '../graphql/queries/search_namespaces_where_user_can_transfer_projects.query.graphql';
|
||||
|
||||
const GROUPS_PER_PAGE = 25;
|
||||
|
||||
export default {
|
||||
name: 'TransferProjectForm',
|
||||
|
|
@ -11,14 +17,6 @@ export default {
|
|||
ConfirmDanger,
|
||||
},
|
||||
props: {
|
||||
groupNamespaces: {
|
||||
type: Array,
|
||||
required: true,
|
||||
},
|
||||
userNamespaces: {
|
||||
type: Array,
|
||||
required: true,
|
||||
},
|
||||
confirmationPhrase: {
|
||||
type: String,
|
||||
required: true,
|
||||
|
|
@ -28,19 +26,88 @@ export default {
|
|||
required: true,
|
||||
},
|
||||
},
|
||||
apollo: {
|
||||
currentUser: {
|
||||
query: searchNamespacesWhereUserCanTransferProjects,
|
||||
debounce: DEBOUNCE_DELAY,
|
||||
variables() {
|
||||
return {
|
||||
search: this.searchTerm,
|
||||
after: null,
|
||||
first: GROUPS_PER_PAGE,
|
||||
};
|
||||
},
|
||||
result() {
|
||||
this.isLoadingMoreGroups = false;
|
||||
this.isSearchLoading = false;
|
||||
},
|
||||
},
|
||||
},
|
||||
data() {
|
||||
return { selectedNamespace: null };
|
||||
return {
|
||||
currentUser: {},
|
||||
selectedNamespace: null,
|
||||
isLoadingMoreGroups: false,
|
||||
isSearchLoading: false,
|
||||
searchTerm: '',
|
||||
};
|
||||
},
|
||||
computed: {
|
||||
hasSelectedNamespace() {
|
||||
return Boolean(this.selectedNamespace?.id);
|
||||
},
|
||||
groupNamespaces() {
|
||||
return this.currentUser.groups?.nodes?.map(this.formatNamespace) || [];
|
||||
},
|
||||
userNamespaces() {
|
||||
const { namespace } = this.currentUser;
|
||||
|
||||
return namespace ? [this.formatNamespace(namespace)] : [];
|
||||
},
|
||||
hasNextPageOfGroups() {
|
||||
return this.currentUser.groups?.pageInfo?.hasNextPage || false;
|
||||
},
|
||||
},
|
||||
methods: {
|
||||
handleSelect(selectedNamespace) {
|
||||
this.selectedNamespace = selectedNamespace;
|
||||
this.$emit('selectNamespace', selectedNamespace.id);
|
||||
},
|
||||
handleLoadMoreGroups() {
|
||||
this.isLoadingMoreGroups = true;
|
||||
|
||||
this.$apollo.queries.currentUser.fetchMore({
|
||||
variables: {
|
||||
after: this.currentUser.groups.pageInfo.endCursor,
|
||||
first: GROUPS_PER_PAGE,
|
||||
},
|
||||
updateQuery(
|
||||
previousResult,
|
||||
{
|
||||
fetchMoreResult: {
|
||||
currentUser: { groups: newGroups },
|
||||
},
|
||||
},
|
||||
) {
|
||||
const previousGroups = previousResult.currentUser.groups;
|
||||
|
||||
return produce(previousResult, (draftData) => {
|
||||
draftData.currentUser.groups.nodes = [...previousGroups.nodes, ...newGroups.nodes];
|
||||
draftData.currentUser.groups.pageInfo = newGroups.pageInfo;
|
||||
});
|
||||
},
|
||||
});
|
||||
},
|
||||
handleSearch(searchTerm) {
|
||||
this.isSearchLoading = true;
|
||||
this.searchTerm = searchTerm;
|
||||
},
|
||||
formatNamespace({ id, fullName }) {
|
||||
return {
|
||||
id: getIdFromGraphQLId(id),
|
||||
humanName: fullName,
|
||||
};
|
||||
},
|
||||
},
|
||||
};
|
||||
</script>
|
||||
|
|
@ -53,7 +120,13 @@ export default {
|
|||
:group-namespaces="groupNamespaces"
|
||||
:user-namespaces="userNamespaces"
|
||||
:selected-namespace="selectedNamespace"
|
||||
:has-next-page-of-groups="hasNextPageOfGroups"
|
||||
:is-loading-more-groups="isLoadingMoreGroups"
|
||||
:is-search-loading="isSearchLoading"
|
||||
:should-filter-namespaces="false"
|
||||
@select="handleSelect"
|
||||
@load-more-groups="handleLoadMoreGroups"
|
||||
@search="handleSearch"
|
||||
/>
|
||||
</gl-form-group>
|
||||
<confirm-danger
|
||||
|
|
|
|||
|
|
@ -0,0 +1,25 @@
|
|||
#import "~/graphql_shared/fragments/page_info.fragment.graphql"
|
||||
|
||||
query searchNamespacesWhereUserCanTransferProjects(
|
||||
$search: String = ""
|
||||
$after: String = ""
|
||||
$first: Int = null
|
||||
) {
|
||||
currentUser {
|
||||
id
|
||||
groups(permissionScope: TRANSFER_PROJECTS, search: $search, after: $after, first: $first) {
|
||||
nodes {
|
||||
id
|
||||
fullName
|
||||
}
|
||||
pageInfo {
|
||||
__typename
|
||||
...PageInfo
|
||||
}
|
||||
}
|
||||
namespace {
|
||||
id
|
||||
fullName
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
@ -1,36 +1,29 @@
|
|||
import Vue from 'vue';
|
||||
import { convertObjectPropsToCamelCase } from '~/lib/utils/common_utils';
|
||||
import VueApollo from 'vue-apollo';
|
||||
import createDefaultClient from '~/lib/graphql';
|
||||
import TransferProjectForm from './components/transfer_project_form.vue';
|
||||
|
||||
const prepareNamespaces = (rawNamespaces = '') => {
|
||||
if (!rawNamespaces) {
|
||||
return { groupNamespaces: [], userNamespaces: [] };
|
||||
}
|
||||
|
||||
const data = JSON.parse(rawNamespaces);
|
||||
return {
|
||||
groupNamespaces: data?.group?.map(convertObjectPropsToCamelCase) || [],
|
||||
userNamespaces: data?.user?.map(convertObjectPropsToCamelCase) || [],
|
||||
};
|
||||
};
|
||||
|
||||
export default () => {
|
||||
const el = document.querySelector('.js-transfer-project-form');
|
||||
if (!el) {
|
||||
return false;
|
||||
}
|
||||
|
||||
Vue.use(VueApollo);
|
||||
|
||||
const {
|
||||
targetFormId = null,
|
||||
targetHiddenInputId = null,
|
||||
buttonText: confirmButtonText = '',
|
||||
phrase: confirmationPhrase = '',
|
||||
confirmDangerMessage = '',
|
||||
namespaces = '',
|
||||
} = el.dataset;
|
||||
|
||||
return new Vue({
|
||||
el,
|
||||
apolloProvider: new VueApollo({
|
||||
defaultClient: createDefaultClient(),
|
||||
}),
|
||||
provide: {
|
||||
confirmDangerMessage,
|
||||
},
|
||||
|
|
@ -39,7 +32,6 @@ export default () => {
|
|||
props: {
|
||||
confirmButtonText,
|
||||
confirmationPhrase,
|
||||
...prepareNamespaces(namespaces),
|
||||
},
|
||||
on: {
|
||||
selectNamespace: (id) => {
|
||||
|
|
|
|||
|
|
@ -5,6 +5,8 @@ import {
|
|||
GlDropdownItem,
|
||||
GlDropdownSectionHeader,
|
||||
GlSearchBoxByType,
|
||||
GlIntersectionObserver,
|
||||
GlLoadingIcon,
|
||||
} from '@gitlab/ui';
|
||||
import { __ } from '~/locale';
|
||||
|
||||
|
|
@ -32,6 +34,8 @@ export default {
|
|||
GlDropdownItem,
|
||||
GlDropdownSectionHeader,
|
||||
GlSearchBoxByType,
|
||||
GlIntersectionObserver,
|
||||
GlLoadingIcon,
|
||||
},
|
||||
props: {
|
||||
groupNamespaces: {
|
||||
|
|
@ -69,6 +73,26 @@ export default {
|
|||
required: false,
|
||||
default: false,
|
||||
},
|
||||
hasNextPageOfGroups: {
|
||||
type: Boolean,
|
||||
required: false,
|
||||
default: false,
|
||||
},
|
||||
isLoadingMoreGroups: {
|
||||
type: Boolean,
|
||||
required: false,
|
||||
default: false,
|
||||
},
|
||||
isSearchLoading: {
|
||||
type: Boolean,
|
||||
required: false,
|
||||
default: false,
|
||||
},
|
||||
shouldFilterNamespaces: {
|
||||
type: Boolean,
|
||||
required: false,
|
||||
default: true,
|
||||
},
|
||||
},
|
||||
data() {
|
||||
return {
|
||||
|
|
@ -84,10 +108,12 @@ export default {
|
|||
return this.groupNamespaces.length;
|
||||
},
|
||||
filteredGroupNamespaces() {
|
||||
if (!this.shouldFilterNamespaces) return this.groupNamespaces;
|
||||
if (!this.hasGroupNamespaces) return [];
|
||||
return filterByName(this.groupNamespaces, this.searchTerm);
|
||||
},
|
||||
filteredUserNamespaces() {
|
||||
if (!this.shouldFilterNamespaces) return this.userNamespaces;
|
||||
if (!this.hasUserNamespaces) return [];
|
||||
return filterByName(this.userNamespaces, this.searchTerm);
|
||||
},
|
||||
|
|
@ -107,9 +133,15 @@ export default {
|
|||
return emptyNamespaceTitle.toLowerCase().includes(searchTerm.toLowerCase());
|
||||
},
|
||||
},
|
||||
watch: {
|
||||
searchTerm() {
|
||||
this.$emit('search', this.searchTerm);
|
||||
},
|
||||
},
|
||||
methods: {
|
||||
handleSelect(item) {
|
||||
this.selectedNamespace = item;
|
||||
this.searchTerm = '';
|
||||
this.$emit('select', item);
|
||||
},
|
||||
handleSelectEmptyNamespace() {
|
||||
|
|
@ -122,7 +154,11 @@ export default {
|
|||
<template>
|
||||
<gl-dropdown :text="selectedNamespaceText" :block="fullWidth" data-qa-selector="namespaces_list">
|
||||
<template #header>
|
||||
<gl-search-box-by-type v-model.trim="searchTerm" />
|
||||
<gl-search-box-by-type
|
||||
v-model.trim="searchTerm"
|
||||
:is-loading="isSearchLoading"
|
||||
data-qa-selector="namespaces_list_search"
|
||||
/>
|
||||
</template>
|
||||
<div v-if="filteredEmptyNamespaceTitle">
|
||||
<gl-dropdown-item
|
||||
|
|
@ -133,19 +169,11 @@ export default {
|
|||
</gl-dropdown-item>
|
||||
<gl-dropdown-divider />
|
||||
</div>
|
||||
<div v-if="hasGroupNamespaces" data-qa-selector="namespaces_list_groups">
|
||||
<gl-dropdown-section-header v-if="includeHeaders">{{
|
||||
$options.i18n.GROUPS
|
||||
}}</gl-dropdown-section-header>
|
||||
<gl-dropdown-item
|
||||
v-for="item in filteredGroupNamespaces"
|
||||
:key="item.id"
|
||||
data-qa-selector="namespaces_list_item"
|
||||
@click="handleSelect(item)"
|
||||
>{{ item.humanName }}</gl-dropdown-item
|
||||
>
|
||||
</div>
|
||||
<div v-if="hasUserNamespaces" data-qa-selector="namespaces_list_users">
|
||||
<div
|
||||
v-if="hasUserNamespaces"
|
||||
data-qa-selector="namespaces_list_users"
|
||||
data-testid="namespace-list-users"
|
||||
>
|
||||
<gl-dropdown-section-header v-if="includeHeaders">{{
|
||||
$options.i18n.USERS
|
||||
}}</gl-dropdown-section-header>
|
||||
|
|
@ -157,5 +185,24 @@ export default {
|
|||
>{{ item.humanName }}</gl-dropdown-item
|
||||
>
|
||||
</div>
|
||||
<div
|
||||
v-if="hasGroupNamespaces"
|
||||
data-qa-selector="namespaces_list_groups"
|
||||
data-testid="namespace-list-groups"
|
||||
>
|
||||
<gl-dropdown-section-header v-if="includeHeaders">{{
|
||||
$options.i18n.GROUPS
|
||||
}}</gl-dropdown-section-header>
|
||||
<gl-dropdown-item
|
||||
v-for="item in filteredGroupNamespaces"
|
||||
:key="item.id"
|
||||
data-qa-selector="namespaces_list_item"
|
||||
@click="handleSelect(item)"
|
||||
>{{ item.humanName }}</gl-dropdown-item
|
||||
>
|
||||
</div>
|
||||
<gl-intersection-observer v-if="hasNextPageOfGroups" @appear="$emit('load-more-groups')">
|
||||
<gl-loading-icon v-if="isLoadingMoreGroups" class="gl-mb-3" size="sm" />
|
||||
</gl-intersection-observer>
|
||||
</gl-dropdown>
|
||||
</template>
|
||||
|
|
|
|||
|
|
@ -16,4 +16,8 @@ module GraphqlTriggers
|
|||
def self.issuable_labels_updated(issuable)
|
||||
GitlabSchema.subscriptions.trigger('issuableLabelsUpdated', { issuable_id: issuable.to_gid }, issuable)
|
||||
end
|
||||
|
||||
def self.issuable_dates_updated(issuable)
|
||||
GitlabSchema.subscriptions.trigger('issuableDatesUpdated', { issuable_id: issuable.to_gid }, issuable)
|
||||
end
|
||||
end
|
||||
|
|
|
|||
|
|
@ -15,5 +15,8 @@ module Types
|
|||
|
||||
field :issuable_labels_updated, subscription: Subscriptions::IssuableUpdated, null: true,
|
||||
description: 'Triggered when the labels of an issuable are updated.'
|
||||
|
||||
field :issuable_dates_updated, subscription: Subscriptions::IssuableUpdated, null: true,
|
||||
description: 'Triggered when the due date or start date of an issuable is updated.'
|
||||
end
|
||||
end
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ module Types
|
|||
ORPHAN_TYPES = [
|
||||
::Types::WorkItems::Widgets::DescriptionType,
|
||||
::Types::WorkItems::Widgets::HierarchyType,
|
||||
::Types::WorkItems::Widgets::LabelsType,
|
||||
::Types::WorkItems::Widgets::AssigneesType,
|
||||
::Types::WorkItems::Widgets::StartAndDueDateType
|
||||
].freeze
|
||||
|
|
@ -29,6 +30,8 @@ module Types
|
|||
::Types::WorkItems::Widgets::HierarchyType
|
||||
when ::WorkItems::Widgets::Assignees
|
||||
::Types::WorkItems::Widgets::AssigneesType
|
||||
when ::WorkItems::Widgets::Labels
|
||||
::Types::WorkItems::Widgets::LabelsType
|
||||
when ::WorkItems::Widgets::StartAndDueDate
|
||||
::Types::WorkItems::Widgets::StartAndDueDateType
|
||||
else
|
||||
|
|
|
|||
|
|
@ -0,0 +1,24 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
module Types
|
||||
module WorkItems
|
||||
module Widgets
|
||||
# Disabling widget level authorization as it might be too granular
|
||||
# and we already authorize the parent work item
|
||||
# rubocop:disable Graphql/AuthorizeTypes
|
||||
class LabelsType < BaseObject
|
||||
graphql_name 'WorkItemWidgetLabels'
|
||||
description 'Represents the labels widget'
|
||||
|
||||
implements Types::WorkItems::WidgetInterface
|
||||
|
||||
field :labels, Types::LabelType.connection_type, null: true,
|
||||
description: 'Labels assigned to the work item.'
|
||||
|
||||
field :allows_scoped_labels, GraphQL::Types::Boolean, null: true, method: :allows_scoped_labels?,
|
||||
description: 'Indicates whether a scoped label is allowed.'
|
||||
end
|
||||
# rubocop:enable Graphql/AuthorizeTypes
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
@ -81,13 +81,6 @@ module NamespacesHelper
|
|||
group.namespace_settings.public_send(method_name, **args) # rubocop:disable GitlabSecurity/PublicSend
|
||||
end
|
||||
|
||||
def namespaces_as_json(selected = :current_user)
|
||||
{
|
||||
group: formatted_namespaces(current_user.manageable_groups_with_routes),
|
||||
user: formatted_namespaces([current_user.namespace])
|
||||
}.to_json
|
||||
end
|
||||
|
||||
def pipeline_usage_app_data(namespace)
|
||||
{
|
||||
namespace_actual_plan_name: namespace.actual_plan_name,
|
||||
|
|
@ -129,17 +122,6 @@ module NamespacesHelper
|
|||
|
||||
[group_label.camelize, elements]
|
||||
end
|
||||
|
||||
def formatted_namespaces(namespaces)
|
||||
namespaces.sort_by(&:human_name).map! do |n|
|
||||
{
|
||||
id: n.id,
|
||||
display_path: n.full_path,
|
||||
human_name: n.human_name,
|
||||
name: n.name
|
||||
}
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
NamespacesHelper.prepend_mod_with('NamespacesHelper')
|
||||
|
|
|
|||
|
|
@ -537,6 +537,10 @@ module Issuable
|
|||
labels.map(&:hook_attrs)
|
||||
end
|
||||
|
||||
def allows_scoped_labels?
|
||||
false
|
||||
end
|
||||
|
||||
# Convert this Issuable class name to a format usable by Ability definitions
|
||||
#
|
||||
# Examples:
|
||||
|
|
|
|||
|
|
@ -21,11 +21,11 @@ module WorkItems
|
|||
}.freeze
|
||||
|
||||
WIDGETS_FOR_TYPE = {
|
||||
issue: [Widgets::Assignees, Widgets::Description, Widgets::Hierarchy, Widgets::StartAndDueDate],
|
||||
issue: [Widgets::Assignees, Widgets::Labels, Widgets::Description, Widgets::Hierarchy, Widgets::StartAndDueDate],
|
||||
incident: [Widgets::Description, Widgets::Hierarchy],
|
||||
test_case: [Widgets::Description],
|
||||
requirement: [Widgets::Description],
|
||||
task: [Widgets::Assignees, Widgets::Description, Widgets::Hierarchy, Widgets::StartAndDueDate]
|
||||
task: [Widgets::Assignees, Widgets::Labels, Widgets::Description, Widgets::Hierarchy, Widgets::StartAndDueDate]
|
||||
}.freeze
|
||||
|
||||
cache_markdown_field :description, pipeline: :single_line
|
||||
|
|
|
|||
|
|
@ -0,0 +1,10 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
module WorkItems
|
||||
module Widgets
|
||||
class Labels < Base
|
||||
delegate :labels, to: :work_item
|
||||
delegate :allows_scoped_labels?, to: :work_item
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
@ -70,6 +70,7 @@ module Issues
|
|||
handle_severity_change(issue, old_severity)
|
||||
handle_escalation_status_change(issue)
|
||||
handle_issue_type_change(issue)
|
||||
handle_date_changes(issue)
|
||||
end
|
||||
|
||||
def handle_assignee_changes(issue, old_assignees)
|
||||
|
|
@ -116,6 +117,12 @@ module Issues
|
|||
|
||||
attr_reader :spam_params
|
||||
|
||||
def handle_date_changes(issue)
|
||||
return unless issue.previous_changes.slice('due_date', 'start_date').any?
|
||||
|
||||
GraphqlTriggers.issuable_dates_updated(issue)
|
||||
end
|
||||
|
||||
def clone_issue(issue)
|
||||
target_project = params.delete(:target_clone_project)
|
||||
with_notes = params.delete(:clone_with_notes)
|
||||
|
|
|
|||
|
|
@ -14,4 +14,4 @@
|
|||
|
||||
= render_if_exists 'admin/application_settings/group_owners_can_manage_default_branch_protection_setting', form: f
|
||||
|
||||
= f.submit _('Save changes'), class: 'gl-button btn-confirm'
|
||||
= f.submit _('Save changes'), pajamas_button: true
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
= form_for @application_setting, url: general_admin_application_settings_path(anchor: 'js-merge-request-settings'), html: { class: 'fieldset-form', id: 'merge-request-settings' } do |f|
|
||||
= gitlab_ui_form_for @application_setting, url: general_admin_application_settings_path(anchor: 'js-merge-request-settings'), html: { class: 'fieldset-form', id: 'merge-request-settings' } do |f|
|
||||
= form_errors(@application_setting, pajamas_alert: true)
|
||||
|
||||
%fieldset
|
||||
|
|
@ -29,4 +29,4 @@
|
|||
= link_to sprite_icon('question-o'),
|
||||
help_page_path('user/admin_area/diff_limits',
|
||||
anchor: 'diff-limits-administration')
|
||||
= f.submit _('Save changes'), class: 'gl-button btn btn-confirm'
|
||||
= f.submit _('Save changes'), pajamas_button: true
|
||||
|
|
|
|||
|
|
@ -2,4 +2,6 @@
|
|||
- @content_class = "limit-container-width" unless fluid_layout
|
||||
|
||||
#js-dependency-proxy{ data: { group_path: @group.full_path,
|
||||
no_manifests_illustration: image_path('illustrations/docker-empty-state.svg'), group_id: @group.id } }
|
||||
no_manifests_illustration: image_path('illustrations/docker-empty-state.svg'),
|
||||
group_id: @group.id,
|
||||
can_clear_cache: can?(current_user, :admin_group, @group).to_s } }
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
- return unless can?(current_user, :change_namespace, @project)
|
||||
- form_id = "transfer-project-form"
|
||||
- hidden_input_id = "new_namespace_id"
|
||||
- initial_data = { namespaces: namespaces_as_json, button_text: s_('ProjectSettings|Transfer project'), confirm_danger_message: transfer_project_message(@project), phrase: @project.name, target_form_id: form_id, target_hidden_input_id: hidden_input_id }
|
||||
- initial_data = { button_text: s_('ProjectSettings|Transfer project'), confirm_danger_message: transfer_project_message(@project), phrase: @project.name, target_form_id: form_id, target_hidden_input_id: hidden_input_id }
|
||||
|
||||
.sub-section
|
||||
%h4.danger-title= _('Transfer project')
|
||||
|
|
|
|||
|
|
@ -421,6 +421,8 @@
|
|||
- 1
|
||||
- - requirements_management_process_requirements_reports
|
||||
- 1
|
||||
- - sbom_reports
|
||||
- 1
|
||||
- - security_auto_fix
|
||||
- 1
|
||||
- - security_findings_delete_by_job_id
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ Planned removal: GitLab <span class="removal-milestone"><%= deprecation["removal
|
|||
<% if deprecation["breaking_change"] -%>
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
<%= deprecation["body"] -%><% else %>
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ For removal reviewers (Technical Writers only):
|
|||
<% if removal["breaking_change"] -%>
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
<%= removal["body"] -%><% else %>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,32 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
class CreateFunctionGitlabSchemaPreventWrite < Gitlab::Database::Migration[2.0]
|
||||
TRIGGER_FUNCTION_NAME = 'gitlab_schema_prevent_write'
|
||||
|
||||
enable_lock_retries!
|
||||
|
||||
# This migration is only to make sure that the lock-write trigger function
|
||||
# matches what we already have on staging/production for Gitlab.com
|
||||
|
||||
def up
|
||||
execute(<<~SQL)
|
||||
CREATE OR REPLACE FUNCTION #{TRIGGER_FUNCTION_NAME}()
|
||||
RETURNS TRIGGER AS
|
||||
$$
|
||||
BEGIN
|
||||
RAISE EXCEPTION 'Table: "%" is write protected within this Gitlab database.', TG_TABLE_NAME
|
||||
USING ERRCODE = 'modifying_sql_data_not_permitted',
|
||||
HINT = 'Make sure you are using the right database connection';
|
||||
END
|
||||
$$ LANGUAGE PLPGSQL
|
||||
SQL
|
||||
end
|
||||
|
||||
def down
|
||||
return if Gitlab.com?
|
||||
|
||||
execute(<<~SQL)
|
||||
DROP FUNCTION #{TRIGGER_FUNCTION_NAME}
|
||||
SQL
|
||||
end
|
||||
end
|
||||
|
|
@ -0,0 +1,36 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
class UpdateLockWritesFunctionDisabledViaSetting < Gitlab::Database::Migration[2.0]
|
||||
TRIGGER_FUNCTION_NAME = 'gitlab_schema_prevent_write'
|
||||
|
||||
def up
|
||||
execute(<<~SQL)
|
||||
CREATE OR REPLACE FUNCTION #{TRIGGER_FUNCTION_NAME}()
|
||||
RETURNS TRIGGER AS
|
||||
$$
|
||||
BEGIN
|
||||
IF COALESCE(NULLIF(current_setting(CONCAT('lock_writes.', TG_TABLE_NAME), true), ''), 'true') THEN
|
||||
RAISE EXCEPTION 'Table: "%" is write protected within this Gitlab database.', TG_TABLE_NAME
|
||||
USING ERRCODE = 'modifying_sql_data_not_permitted',
|
||||
HINT = 'Make sure you are using the right database connection';
|
||||
END IF;
|
||||
RETURN NEW;
|
||||
END
|
||||
$$ LANGUAGE PLPGSQL;
|
||||
SQL
|
||||
end
|
||||
|
||||
def down
|
||||
execute(<<~SQL)
|
||||
CREATE OR REPLACE FUNCTION #{TRIGGER_FUNCTION_NAME}()
|
||||
RETURNS TRIGGER AS
|
||||
$$
|
||||
BEGIN
|
||||
RAISE EXCEPTION 'Table: "%" is write protected within this Gitlab database.', TG_TABLE_NAME
|
||||
USING ERRCODE = 'modifying_sql_data_not_permitted',
|
||||
HINT = 'Make sure you are using the right database connection';
|
||||
END
|
||||
$$ LANGUAGE PLPGSQL
|
||||
SQL
|
||||
end
|
||||
end
|
||||
|
|
@ -0,0 +1 @@
|
|||
d5fac73cd92e84f49b41aa38e560eed36906e29e7009ff03ef59ebcf9836ee1f
|
||||
|
|
@ -0,0 +1 @@
|
|||
6a3f6ca25cac7f846c2f52388a8898bd05095f0d612bc7d4950e899880e0c8b8
|
||||
|
|
@ -22,6 +22,19 @@ RETURN NULL;
|
|||
END
|
||||
$$;
|
||||
|
||||
CREATE FUNCTION gitlab_schema_prevent_write() RETURNS trigger
|
||||
LANGUAGE plpgsql
|
||||
AS $$
|
||||
BEGIN
|
||||
IF COALESCE(NULLIF(current_setting(CONCAT('lock_writes.', TG_TABLE_NAME), true), ''), 'true') THEN
|
||||
RAISE EXCEPTION 'Table: "%" is write protected within this Gitlab database.', TG_TABLE_NAME
|
||||
USING ERRCODE = 'modifying_sql_data_not_permitted',
|
||||
HINT = 'Make sure you are using the right database connection';
|
||||
END IF;
|
||||
RETURN NEW;
|
||||
END
|
||||
$$;
|
||||
|
||||
CREATE FUNCTION insert_into_loose_foreign_keys_deleted_records() RETURNS trigger
|
||||
LANGUAGE plpgsql
|
||||
AS $$
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ GraphQL data is arranged in types, so your client can use
|
|||
to consume the API and avoid manual parsing.
|
||||
|
||||
There are no fixed endpoints and no data model, so you can add
|
||||
to the API without creating [breaking changes](../../development/contributing/#breaking-changes).
|
||||
to the API without creating [breaking changes](../../development/deprecation_guidelines/index.md).
|
||||
This enables us to have a [versionless API](https://graphql.org/learn/best-practices/#versioning).
|
||||
|
||||
## Vision
|
||||
|
|
@ -69,7 +69,7 @@ However, GitLab sometimes changes the GraphQL API in a way that is not backward-
|
|||
can include removing or renaming fields, arguments, or other parts of the schema.
|
||||
When creating a breaking change, GitLab follows a [deprecation and removal process](#deprecation-and-removal-process).
|
||||
|
||||
Learn more about [breaking changes](../../development/contributing/#breaking-changes).
|
||||
Learn more about [breaking changes](../../development/deprecation_guidelines/index.md).
|
||||
|
||||
Fields behind a feature flag and disabled by default do not follow the deprecation and removal process, and can be removed at any time without notice.
|
||||
|
||||
|
|
|
|||
|
|
@ -18929,6 +18929,18 @@ Represents a hierarchy widget.
|
|||
| <a id="workitemwidgethierarchyparent"></a>`parent` | [`WorkItem`](#workitem) | Parent work item. |
|
||||
| <a id="workitemwidgethierarchytype"></a>`type` | [`WorkItemWidgetType`](#workitemwidgettype) | Widget type. |
|
||||
|
||||
### `WorkItemWidgetLabels`
|
||||
|
||||
Represents the labels widget.
|
||||
|
||||
#### Fields
|
||||
|
||||
| Name | Type | Description |
|
||||
| ---- | ---- | ----------- |
|
||||
| <a id="workitemwidgetlabelsallowsscopedlabels"></a>`allowsScopedLabels` | [`Boolean`](#boolean) | Indicates whether a scoped label is allowed. |
|
||||
| <a id="workitemwidgetlabelslabels"></a>`labels` | [`LabelConnection`](#labelconnection) | Labels assigned to the work item. (see [Connections](#connections)) |
|
||||
| <a id="workitemwidgetlabelstype"></a>`type` | [`WorkItemWidgetType`](#workitemwidgettype) | Widget type. |
|
||||
|
||||
### `WorkItemWidgetStartAndDueDate`
|
||||
|
||||
Represents a start and due date widget.
|
||||
|
|
@ -20839,6 +20851,7 @@ Type of a work item widget.
|
|||
| <a id="workitemwidgettypeassignees"></a>`ASSIGNEES` | Assignees widget. |
|
||||
| <a id="workitemwidgettypedescription"></a>`DESCRIPTION` | Description widget. |
|
||||
| <a id="workitemwidgettypehierarchy"></a>`HIERARCHY` | Hierarchy widget. |
|
||||
| <a id="workitemwidgettypelabels"></a>`LABELS` | Labels widget. |
|
||||
| <a id="workitemwidgettypestart_and_due_date"></a>`START_AND_DUE_DATE` | Start And Due Date widget. |
|
||||
| <a id="workitemwidgettypeverification_status"></a>`VERIFICATION_STATUS` | Verification Status widget. |
|
||||
| <a id="workitemwidgettypeweight"></a>`WEIGHT` | Weight widget. |
|
||||
|
|
@ -22096,6 +22109,7 @@ Implementations:
|
|||
- [`WorkItemWidgetAssignees`](#workitemwidgetassignees)
|
||||
- [`WorkItemWidgetDescription`](#workitemwidgetdescription)
|
||||
- [`WorkItemWidgetHierarchy`](#workitemwidgethierarchy)
|
||||
- [`WorkItemWidgetLabels`](#workitemwidgetlabels)
|
||||
- [`WorkItemWidgetStartAndDueDate`](#workitemwidgetstartandduedate)
|
||||
- [`WorkItemWidgetVerificationStatus`](#workitemwidgetverificationstatus)
|
||||
- [`WorkItemWidgetWeight`](#workitemwidgetweight)
|
||||
|
|
|
|||
|
|
@ -186,21 +186,11 @@ reasons for including it.
|
|||
Mention a maintainer in merge requests that contain:
|
||||
|
||||
- More than 500 changes.
|
||||
- Any major [breaking changes](#breaking-changes).
|
||||
- Any major [breaking changes](../deprecation_guidelines/index.md).
|
||||
- External libraries.
|
||||
|
||||
If you are not sure who to mention, the reviewer will do this for you early in the merge request process.
|
||||
|
||||
#### Breaking changes
|
||||
|
||||
A "breaking change" is any change that requires users to make a corresponding change to their code, settings, or workflow. "Users" might be humans, API clients, or even code classes that "use" another class. Examples of breaking changes include:
|
||||
|
||||
- Removing a user-facing feature without a replacement/workaround.
|
||||
- Changing the definition of an existing API (by doing things like re-naming query parameters or changing routes).
|
||||
- Removing a public method from a code class.
|
||||
|
||||
A breaking change can be considered "major" if it affects many users, or represents a significant change in behavior.
|
||||
|
||||
#### Issues workflow
|
||||
|
||||
This [documentation](issue_workflow.md) outlines the current issue workflow:
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ Most issues will have labels for at least one of the following:
|
|||
- Priority: `~"priority::1"`, `~"priority::2"`, `~"priority::3"`, `~"priority::4"`
|
||||
- Severity: ~`"severity::1"`, `~"severity::2"`, `~"severity::3"`, `~"severity::4"`
|
||||
|
||||
Please add `~"breaking change"` label if the issue can be considered as a [breaking change](index.md#breaking-changes).
|
||||
Please add `~"breaking change"` label if the issue can be considered as a [breaking change](../deprecation_guidelines/index.md).
|
||||
|
||||
Please add `~security` label if the issue is related to application security.
|
||||
|
||||
|
|
|
|||
|
|
@ -119,7 +119,7 @@ Commit messages should follow the guidelines below, for reasons explained by Chr
|
|||
#### Why these standards matter
|
||||
|
||||
1. Consistent commit messages that follow these guidelines make the history more readable.
|
||||
1. Concise standard commit messages helps to identify [breaking changes](index.md#breaking-changes) for a deployment or ~"master:broken" quicker when
|
||||
1. Concise standard commit messages helps to identify [breaking changes](../deprecation_guidelines/index.md) for a deployment or ~"master:broken" quicker when
|
||||
reviewing commits between two points in time.
|
||||
|
||||
#### Commit message template
|
||||
|
|
|
|||
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
---
|
||||
|
||||
# Hash Indexes
|
||||
|
||||
PostgreSQL supports hash indexes besides the regular B-tree
|
||||
indexes. Hash indexes however are to be avoided at all costs. While they may
|
||||
_sometimes_ provide better performance the cost of rehashing can be very high.
|
||||
More importantly: at least until PostgreSQL 10.0 hash indexes are not
|
||||
WAL-logged, meaning they are not replicated to any replicas. From the PostgreSQL
|
||||
documentation:
|
||||
|
||||
> Hash index operations are not presently WAL-logged, so hash indexes might need
|
||||
> to be rebuilt with REINDEX after a database crash if there were unwritten
|
||||
> changes. Also, changes to hash indexes are not replicated over streaming or
|
||||
> file-based replication after the initial base backup, so they give wrong
|
||||
> answers to queries that subsequently use them. For these reasons, hash index
|
||||
> use is presently discouraged.
|
||||
|
||||
RuboCop is configured to register an offense when it detects the use of a hash
|
||||
index.
|
||||
|
||||
Instead of using hash indexes you should use regular B-tree indexes.
|
||||
|
|
@ -48,13 +48,13 @@ info: To determine the technical writer assigned to the Stage/Group associated w
|
|||
- [Strings and the Text data type](strings_and_the_text_data_type.md)
|
||||
- [Single table inheritance](single_table_inheritance.md)
|
||||
- [Polymorphic associations](polymorphic_associations.md)
|
||||
- [Serializing data](../serializing_data.md)
|
||||
- [Hash indexes](../hash_indexes.md)
|
||||
- [Storing SHA1 hashes as binary](../sha1_as_binary.md)
|
||||
- [Serializing data](serializing_data.md)
|
||||
- [Hash indexes](hash_indexes.md)
|
||||
- [Storing SHA1 hashes as binary](sha1_as_binary.md)
|
||||
- [Iterating tables in batches](iterating_tables_in_batches.md)
|
||||
- [Insert into tables in batches](insert_into_tables_in_batches.md)
|
||||
- [Ordering table columns](ordering_table_columns.md)
|
||||
- [Verifying database capabilities](../verifying_database_capabilities.md)
|
||||
- [Verifying database capabilities](verifying_database_capabilities.md)
|
||||
- [Database Debugging and Troubleshooting](../database_debugging.md)
|
||||
- [Query Count Limits](query_count_limits.md)
|
||||
- [Creating enums](creating_enums.md)
|
||||
|
|
|
|||
|
|
@ -0,0 +1,90 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
---
|
||||
|
||||
# Serializing Data
|
||||
|
||||
**Summary:** don't store serialized data in the database, use separate columns
|
||||
and/or tables instead. This includes storing of comma separated values as a
|
||||
string.
|
||||
|
||||
Rails makes it possible to store serialized data in JSON, YAML or other formats.
|
||||
Such a field can be defined as follows:
|
||||
|
||||
```ruby
|
||||
class Issue < ActiveRecord::Model
|
||||
serialize :custom_fields
|
||||
end
|
||||
```
|
||||
|
||||
While it may be tempting to store serialized data in the database there are many
|
||||
problems with this. This document outlines these problems and provide an
|
||||
alternative.
|
||||
|
||||
## Serialized Data Is Less Powerful
|
||||
|
||||
When using a relational database you have the ability to query individual
|
||||
fields, change the schema, index data, and so forth. When you use serialized data
|
||||
all of that becomes either very difficult or downright impossible. While
|
||||
PostgreSQL does offer the ability to query JSON fields it is mostly meant for
|
||||
very specialized use cases, and not for more general use. If you use YAML in
|
||||
turn there's no way to query the data at all.
|
||||
|
||||
## Waste Of Space
|
||||
|
||||
Storing serialized data such as JSON or YAML ends up wasting a lot of space.
|
||||
This is because these formats often include additional characters (for example, double
|
||||
quotes or newlines) besides the data that you are storing.
|
||||
|
||||
## Difficult To Manage
|
||||
|
||||
There comes a time where you must add a new field to the serialized
|
||||
data, or change an existing one. Using serialized data this becomes difficult
|
||||
and very time consuming as the only way of doing so is to re-write all the
|
||||
stored values. To do so you would have to:
|
||||
|
||||
1. Retrieve the data
|
||||
1. Parse it into a Ruby structure
|
||||
1. Mutate it
|
||||
1. Serialize it back to a String
|
||||
1. Store it in the database
|
||||
|
||||
On the other hand, if one were to use regular columns adding a column would be:
|
||||
|
||||
```sql
|
||||
ALTER TABLE table_name ADD COLUMN column_name type;
|
||||
```
|
||||
|
||||
Such a query would take very little to no time and would immediately apply to
|
||||
all rows, without having to re-write large JSON or YAML structures.
|
||||
|
||||
Finally, there comes a time when the JSON or YAML structure is no longer
|
||||
sufficient and you must migrate away from it. When storing only a few rows
|
||||
this may not be a problem, but when storing millions of rows such a migration
|
||||
can take hours or even days to complete.
|
||||
|
||||
## Relational Databases Are Not Document Stores
|
||||
|
||||
When storing data as JSON or YAML you're essentially using your database as if
|
||||
it were a document store (for example, MongoDB), except you're not using any of the
|
||||
powerful features provided by a typical RDBMS _nor_ are you using any of the
|
||||
features provided by a typical document store (for example, the ability to index fields
|
||||
of documents with variable fields). In other words, it's a waste.
|
||||
|
||||
## Consistent Fields
|
||||
|
||||
One argument sometimes made in favour of serialized data is having to store
|
||||
widely varying fields and values. Sometimes this is truly the case, and then
|
||||
perhaps it might make sense to use serialized data. However, in 99% of the cases
|
||||
the fields and types stored tend to be the same for every row. Even if there is
|
||||
a slight difference you can still use separate columns and just not set the ones
|
||||
you don't need.
|
||||
|
||||
## The Solution
|
||||
|
||||
The solution is to use separate columns and/or separate tables.
|
||||
This allows you to use all the features provided by your database, it
|
||||
makes it easier to manage and migrate the data, you conserve space, you can
|
||||
index the data efficiently and so forth.
|
||||
|
|
@ -0,0 +1,42 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
---
|
||||
|
||||
# Storing SHA1 Hashes As Binary
|
||||
|
||||
Storing SHA1 hashes as strings is not very space efficient. A SHA1 as a string
|
||||
requires at least 40 bytes, an additional byte to store the encoding, and
|
||||
perhaps more space depending on the internals of PostgreSQL.
|
||||
|
||||
On the other hand, if one were to store a SHA1 as binary one would only need 20
|
||||
bytes for the actual SHA1, and 1 or 4 bytes of additional space (again depending
|
||||
on database internals). This means that in the best case scenario we can reduce
|
||||
the space usage by 50%.
|
||||
|
||||
To make this easier to work with you can include the concern `ShaAttribute` into
|
||||
a model and define a SHA attribute using the `sha_attribute` class method. For
|
||||
example:
|
||||
|
||||
```ruby
|
||||
class Commit < ActiveRecord::Base
|
||||
include ShaAttribute
|
||||
|
||||
sha_attribute :sha
|
||||
end
|
||||
```
|
||||
|
||||
This allows you to use the value of the `sha` attribute as if it were a string,
|
||||
while storing it as binary. This means that you can do something like this,
|
||||
without having to worry about converting data to the right binary format:
|
||||
|
||||
```ruby
|
||||
commit = Commit.find_by(sha: '88c60307bd1f215095834f09a1a5cb18701ac8ad')
|
||||
commit.sha = '971604de4cfa324d91c41650fabc129420c8d1cc'
|
||||
commit.save
|
||||
```
|
||||
|
||||
There is however one requirement: the column used to store the SHA has _must_ be
|
||||
a binary type. For Rails this means you need to use the `:binary` type instead
|
||||
of `:text` or `:string`.
|
||||
|
|
@ -0,0 +1,38 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
---
|
||||
|
||||
# Verifying Database Capabilities
|
||||
|
||||
Sometimes certain bits of code may only work on a certain database
|
||||
version. While we try to avoid such code as much as possible sometimes it is
|
||||
necessary to add database (version) specific behavior.
|
||||
|
||||
To facilitate this we have the following methods that you can use:
|
||||
|
||||
- `ApplicationRecord.database.version`: returns the PostgreSQL version number as a string
|
||||
in the format `X.Y.Z`.
|
||||
|
||||
This allows you to write code such as:
|
||||
|
||||
```ruby
|
||||
if ApplicationRecord.database.version.to_f >= 11.7
|
||||
run_really_fast_query
|
||||
else
|
||||
run_fast_query
|
||||
end
|
||||
```
|
||||
|
||||
## Read-only database
|
||||
|
||||
The database can be used in read-only mode. In this case we have to
|
||||
make sure all GET requests don't attempt any write operations to the
|
||||
database. If one of those requests wants to write to the database, it needs
|
||||
to be wrapped in a `Gitlab::Database.read_only?` or `Gitlab::Database.read_write?`
|
||||
guard, to make sure it doesn't for read-only databases.
|
||||
|
||||
We have a Rails Middleware that filters any potentially writing
|
||||
operations (the `CUD` operations of CRUD) and prevent the user from trying
|
||||
to update the database and getting a 500 error (see `Gitlab::Middleware::ReadOnly`).
|
||||
|
|
@ -6,8 +6,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
|
|||
|
||||
# Deprecating GitLab features
|
||||
|
||||
This page includes information about how and when to remove or make
|
||||
[breaking changes](../contributing/index.md#breaking-changes) to GitLab features.
|
||||
This page includes information about how and when to remove or make breaking changes
|
||||
to GitLab features.
|
||||
|
||||
## Terminology
|
||||
|
||||
|
|
@ -37,6 +37,16 @@ This page includes information about how and when to remove or make
|
|||
|
||||
|
||||
|
||||
**Breaking change**:
|
||||
|
||||
A "breaking change" is any change that requires users to make a corresponding change to their code, settings, or workflow. "Users" might be humans, API clients, or even code classes that "use" another class. Examples of breaking changes include:
|
||||
|
||||
- Removing a user-facing feature without a replacement/workaround.
|
||||
- Changing the definition of an existing API (by doing things like re-naming query parameters or changing routes).
|
||||
- Removing a public method from a code class.
|
||||
|
||||
A breaking change can be considered major if it affects many users, or represents a significant change in behavior.
|
||||
|
||||
## When can a feature be deprecated?
|
||||
|
||||
Deprecations should be announced on the [Deprecated feature removal schedule](../../update/deprecations.md).
|
||||
|
|
|
|||
|
|
@ -576,7 +576,7 @@ See `Gitlab::Geo.enabled?` and `Gitlab::Geo.license_allows?` methods.
|
|||
|
||||
All Geo **secondary** sites are read-only.
|
||||
|
||||
The general principle of a [read-only database](verifying_database_capabilities.md#read-only-database)
|
||||
The general principle of a [read-only database](database/verifying_database_capabilities.md#read-only-database)
|
||||
applies to all Geo **secondary** sites. So the
|
||||
`Gitlab::Database.read_only?` method will always return `true` on a
|
||||
**secondary** site.
|
||||
|
|
|
|||
|
|
@ -1,26 +1,11 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
redirect_to: 'database/hash_indexes.md'
|
||||
remove_date: '2022-11-06'
|
||||
---
|
||||
|
||||
# Hash Indexes
|
||||
This document was moved to [another location](database/hash_indexes.md).
|
||||
|
||||
PostgreSQL supports hash indexes besides the regular B-tree
|
||||
indexes. Hash indexes however are to be avoided at all costs. While they may
|
||||
_sometimes_ provide better performance the cost of rehashing can be very high.
|
||||
More importantly: at least until PostgreSQL 10.0 hash indexes are not
|
||||
WAL-logged, meaning they are not replicated to any replicas. From the PostgreSQL
|
||||
documentation:
|
||||
|
||||
> Hash index operations are not presently WAL-logged, so hash indexes might need
|
||||
> to be rebuilt with REINDEX after a database crash if there were unwritten
|
||||
> changes. Also, changes to hash indexes are not replicated over streaming or
|
||||
> file-based replication after the initial base backup, so they give wrong
|
||||
> answers to queries that subsequently use them. For these reasons, hash index
|
||||
> use is presently discouraged.
|
||||
|
||||
RuboCop is configured to register an offense when it detects the use of a hash
|
||||
index.
|
||||
|
||||
Instead of using hash indexes you should use regular B-tree indexes.
|
||||
<!-- This redirect file can be deleted after <2022-11-06>. -->
|
||||
<!-- Redirects that point to other docs in the same project expire in three months. -->
|
||||
<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
|
||||
<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->
|
||||
|
|
|
|||
|
|
@ -1,90 +1,11 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
redirect_to: 'database/serializing_data.md'
|
||||
remove_date: '2022-11-06'
|
||||
---
|
||||
|
||||
# Serializing Data
|
||||
This document was moved to [another location](database/serializing_data.md).
|
||||
|
||||
**Summary:** don't store serialized data in the database, use separate columns
|
||||
and/or tables instead. This includes storing of comma separated values as a
|
||||
string.
|
||||
|
||||
Rails makes it possible to store serialized data in JSON, YAML or other formats.
|
||||
Such a field can be defined as follows:
|
||||
|
||||
```ruby
|
||||
class Issue < ActiveRecord::Model
|
||||
serialize :custom_fields
|
||||
end
|
||||
```
|
||||
|
||||
While it may be tempting to store serialized data in the database there are many
|
||||
problems with this. This document outlines these problems and provide an
|
||||
alternative.
|
||||
|
||||
## Serialized Data Is Less Powerful
|
||||
|
||||
When using a relational database you have the ability to query individual
|
||||
fields, change the schema, index data, and so forth. When you use serialized data
|
||||
all of that becomes either very difficult or downright impossible. While
|
||||
PostgreSQL does offer the ability to query JSON fields it is mostly meant for
|
||||
very specialized use cases, and not for more general use. If you use YAML in
|
||||
turn there's no way to query the data at all.
|
||||
|
||||
## Waste Of Space
|
||||
|
||||
Storing serialized data such as JSON or YAML ends up wasting a lot of space.
|
||||
This is because these formats often include additional characters (for example, double
|
||||
quotes or newlines) besides the data that you are storing.
|
||||
|
||||
## Difficult To Manage
|
||||
|
||||
There comes a time where you must add a new field to the serialized
|
||||
data, or change an existing one. Using serialized data this becomes difficult
|
||||
and very time consuming as the only way of doing so is to re-write all the
|
||||
stored values. To do so you would have to:
|
||||
|
||||
1. Retrieve the data
|
||||
1. Parse it into a Ruby structure
|
||||
1. Mutate it
|
||||
1. Serialize it back to a String
|
||||
1. Store it in the database
|
||||
|
||||
On the other hand, if one were to use regular columns adding a column would be:
|
||||
|
||||
```sql
|
||||
ALTER TABLE table_name ADD COLUMN column_name type;
|
||||
```
|
||||
|
||||
Such a query would take very little to no time and would immediately apply to
|
||||
all rows, without having to re-write large JSON or YAML structures.
|
||||
|
||||
Finally, there comes a time when the JSON or YAML structure is no longer
|
||||
sufficient and you must migrate away from it. When storing only a few rows
|
||||
this may not be a problem, but when storing millions of rows such a migration
|
||||
can take hours or even days to complete.
|
||||
|
||||
## Relational Databases Are Not Document Stores
|
||||
|
||||
When storing data as JSON or YAML you're essentially using your database as if
|
||||
it were a document store (for example, MongoDB), except you're not using any of the
|
||||
powerful features provided by a typical RDBMS _nor_ are you using any of the
|
||||
features provided by a typical document store (for example, the ability to index fields
|
||||
of documents with variable fields). In other words, it's a waste.
|
||||
|
||||
## Consistent Fields
|
||||
|
||||
One argument sometimes made in favour of serialized data is having to store
|
||||
widely varying fields and values. Sometimes this is truly the case, and then
|
||||
perhaps it might make sense to use serialized data. However, in 99% of the cases
|
||||
the fields and types stored tend to be the same for every row. Even if there is
|
||||
a slight difference you can still use separate columns and just not set the ones
|
||||
you don't need.
|
||||
|
||||
## The Solution
|
||||
|
||||
The solution is to use separate columns and/or separate tables.
|
||||
This allows you to use all the features provided by your database, it
|
||||
makes it easier to manage and migrate the data, you conserve space, you can
|
||||
index the data efficiently and so forth.
|
||||
<!-- This redirect file can be deleted after <2022-11-06>. -->
|
||||
<!-- Redirects that point to other docs in the same project expire in three months. -->
|
||||
<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
|
||||
<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->
|
||||
|
|
|
|||
|
|
@ -1,42 +1,11 @@
|
|||
---
|
||||
stage: none
|
||||
group: unassigned
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
redirect_to: 'database/sha1_as_binary.md'
|
||||
remove_date: '2022-11-06'
|
||||
---
|
||||
|
||||
# Storing SHA1 Hashes As Binary
|
||||
This document was moved to [another location](database/sha1_as_binary.md).
|
||||
|
||||
Storing SHA1 hashes as strings is not very space efficient. A SHA1 as a string
|
||||
requires at least 40 bytes, an additional byte to store the encoding, and
|
||||
perhaps more space depending on the internals of PostgreSQL.
|
||||
|
||||
On the other hand, if one were to store a SHA1 as binary one would only need 20
|
||||
bytes for the actual SHA1, and 1 or 4 bytes of additional space (again depending
|
||||
on database internals). This means that in the best case scenario we can reduce
|
||||
the space usage by 50%.
|
||||
|
||||
To make this easier to work with you can include the concern `ShaAttribute` into
|
||||
a model and define a SHA attribute using the `sha_attribute` class method. For
|
||||
example:
|
||||
|
||||
```ruby
|
||||
class Commit < ActiveRecord::Base
|
||||
include ShaAttribute
|
||||
|
||||
sha_attribute :sha
|
||||
end
|
||||
```
|
||||
|
||||
This allows you to use the value of the `sha` attribute as if it were a string,
|
||||
while storing it as binary. This means that you can do something like this,
|
||||
without having to worry about converting data to the right binary format:
|
||||
|
||||
```ruby
|
||||
commit = Commit.find_by(sha: '88c60307bd1f215095834f09a1a5cb18701ac8ad')
|
||||
commit.sha = '971604de4cfa324d91c41650fabc129420c8d1cc'
|
||||
commit.save
|
||||
```
|
||||
|
||||
There is however one requirement: the column used to store the SHA has _must_ be
|
||||
a binary type. For Rails this means you need to use the `:binary` type instead
|
||||
of `:text` or `:string`.
|
||||
<!-- This redirect file can be deleted after <2022-11-06>. -->
|
||||
<!-- Redirects that point to other docs in the same project expire in three months. -->
|
||||
<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
|
||||
<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->
|
||||
|
|
|
|||
|
|
@ -1,38 +1,11 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
redirect_to: 'database/verifying_database_capabilities.md'
|
||||
remove_date: '2022-11-06'
|
||||
---
|
||||
|
||||
# Verifying Database Capabilities
|
||||
This document was moved to [another location](database/verifying_database_capabilities.md).
|
||||
|
||||
Sometimes certain bits of code may only work on a certain database
|
||||
version. While we try to avoid such code as much as possible sometimes it is
|
||||
necessary to add database (version) specific behavior.
|
||||
|
||||
To facilitate this we have the following methods that you can use:
|
||||
|
||||
- `ApplicationRecord.database.version`: returns the PostgreSQL version number as a string
|
||||
in the format `X.Y.Z`.
|
||||
|
||||
This allows you to write code such as:
|
||||
|
||||
```ruby
|
||||
if ApplicationRecord.database.version.to_f >= 11.7
|
||||
run_really_fast_query
|
||||
else
|
||||
run_fast_query
|
||||
end
|
||||
```
|
||||
|
||||
## Read-only database
|
||||
|
||||
The database can be used in read-only mode. In this case we have to
|
||||
make sure all GET requests don't attempt any write operations to the
|
||||
database. If one of those requests wants to write to the database, it needs
|
||||
to be wrapped in a `Gitlab::Database.read_only?` or `Gitlab::Database.read_write?`
|
||||
guard, to make sure it doesn't for read-only databases.
|
||||
|
||||
We have a Rails Middleware that filters any potentially writing
|
||||
operations (the `CUD` operations of CRUD) and prevent the user from trying
|
||||
to update the database and getting a 500 error (see `Gitlab::Middleware::ReadOnly`).
|
||||
<!-- This redirect file can be deleted after <2022-11-06>. -->
|
||||
<!-- Redirects that point to other docs in the same project expire in three months. -->
|
||||
<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
|
||||
<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ The [**Maximum number of active pipelines per project** limit](https://docs.gitl
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `job_age` parameter, returned from the `POST /jobs/request` API endpoint used in communication with GitLab Runner, was never used by any GitLab or Runner feature. This parameter will be removed in GitLab 16.0.
|
||||
|
|
@ -93,7 +93,7 @@ This could be a breaking change for anyone that developed their own runner that
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The [Jira DVCS Connector](https://docs.gitlab.com/ee/integration/jira/dvcs.html) (which enables the [Jira Development Panel](https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/)), will no longer support Jira Cloud users starting with GitLab 16.0. The [GitLab for Jira App](https://docs.gitlab.com/ee/integration/jira/connect-app.html) has always been recommended for Jira Cloud users, and it will be required instead of the DVCS connector. If you are a Jira Cloud user, we recommended you begin migrating to the GitLab for Jira App.
|
||||
|
|
@ -108,7 +108,7 @@ Any Jira Server and Jira Data Center users will need to confirm they are not usi
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Previously, the [PipelineSecurityReportFinding GraphQL type was updated](https://gitlab.com/gitlab-org/gitlab/-/issues/335372) to include a new `title` field. This field is an alias for the current `name` field, making the less specific `name` field redundant. The `name` field will be removed from the PipelineSecurityReportFinding type in GitLab 16.0.
|
||||
|
|
@ -122,7 +122,7 @@ Previously, the [PipelineSecurityReportFinding GraphQL type was updated](https:/
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) attribute of vulnerability findings is being deprecated in favor of a `uuid` attribute. By using UUIDv5 values to identify findings, we can easily associate any related entity with a finding. The `project_fingerprint` attribute is no longer being used to track findings, and will be removed in GitLab 16.0.
|
||||
|
|
@ -136,7 +136,7 @@ The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) a
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `maintainer_note` argument in the `POST /runners` REST endpoint was deprecated in GitLab 14.8 and replaced with the `maintenance_note` argument.
|
||||
|
|
@ -164,7 +164,7 @@ GitLab 15.3 to simplify the codebase and prevent any unwanted performance degrad
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Previous work helped [align the vulnerabilities calls for pipeline security tabs](https://gitlab.com/gitlab-org/gitlab/-/issues/343469) to match the vulnerabilities calls for project-level and group-level vulnerability reports. This helped the frontend have a more consistent interface. The old `project.pipeline.securityReportFindings` query was formatted differently than other vulnerability data calls. Now that it has been replaced with the new `project.pipeline.vulnerabilities` field, the old `project.pipeline.securityReportFindings` is being deprecated and will be removed in GitLab 16.0.
|
||||
|
|
@ -183,7 +183,7 @@ Previous work helped [align the vulnerabilities calls for pipeline security tabs
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `CiCdSettingsUpdate` mutation was renamed to `ProjectCiCdSettingsUpdate` in GitLab 15.0.
|
||||
|
|
@ -200,7 +200,7 @@ instead.
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `legacyMode` argument to the `status` field in `RunnerType` will be rendered non-functional in the 16.0 release
|
||||
|
|
@ -219,7 +219,7 @@ be present during the 16.x cycle to avoid breaking the API signature, and will b
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Support for PostgreSQL 12 is scheduled for removal in GitLab 16.0.
|
||||
|
|
@ -256,7 +256,7 @@ by this value remains performant. Due to very low usage of the `State` column fo
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 15.0, for Dependency Scanning, the default version of Java that the scanner expects will be updated from 11 to 17. Java 17 is [the most up-to-date Long Term Support (LTS) version](https://en.wikipedia.org/wiki/Java_version_history). Dependency scanning continues to support the same [range of versions (8, 11, 13, 14, 15, 16, 17)](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#supported-languages-and-package-managers), only the default version is changing. If your project uses the previous default of Java 11, be sure to [set the `DS_Java_Version` variable to match](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning).
|
||||
|
|
@ -270,7 +270,7 @@ In GitLab 15.0, for Dependency Scanning, the default version of Java that the sc
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-04-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Manual iteration management is deprecated and only automatic iteration cadences will be supported in the future.
|
||||
|
|
@ -302,7 +302,7 @@ For more information about iteration cadences, you can refer to
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As Advanced Search migrations usually require support multiple code paths for a long period of time, it’s important to clean those up when we safely can. We use GitLab major version upgrades as a safe time to remove backward compatibility for indices that have not been fully migrated. See the [upgrade documentation](https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version) for details.
|
||||
|
|
@ -316,7 +316,7 @@ As Advanced Search migrations usually require support multiple code paths for a
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Toggling notes confidentiality with REST and GraphQL APIs is being deprecated. Updating notes confidential attribute is no longer supported by any means. We are changing this to simplify the experience and prevent private information from being unintentionally exposed.
|
||||
|
|
@ -335,7 +335,7 @@ Toggling notes confidentiality with REST and GraphQL APIs is being deprecated. U
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
To reduce the overall complexity and maintenance burden of GitLab's [object storage feature](https://docs.gitlab.com/ee/administration/object_storage.html), support for using `background_upload` to upload files is deprecated and will be fully removed in GitLab 15.0. Review the [15.0 specific changes](https://docs.gitlab.com/omnibus/update/gitlab_15_changes.html) for the [removed background uploads settings for object storage](https://docs.gitlab.com/omnibus/update/gitlab_15_changes.html#removed-background-uploads-settings-for-object-storage).
|
||||
|
|
@ -376,7 +376,7 @@ In 15.0, support for daemon mode for GitLab Pages will be removed.
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab self-monitoring gives administrators of self-hosted GitLab instances the tools to monitor the health of their instances. This feature is deprecated in GitLab 14.9, and is scheduled for removal in 16.0.
|
||||
|
|
@ -390,7 +390,7 @@ GitLab self-monitoring gives administrators of self-hosted GitLab instances the
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GitLab Package stage offers a Package Registry, Container Registry, and Dependency Proxy to help you manage all of your dependencies using GitLab. Each of these product categories has a variety of settings that can be adjusted using the API.
|
||||
|
|
@ -421,7 +421,7 @@ The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks.
|
|||
Planned removal: GitLab <span class="removal-milestone">14.10</span> (2022-04-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GitLab Composer repository can be used to push, search, fetch metadata about, and download PHP dependencies. All these actions require authentication, except for downloading dependencies.
|
||||
|
|
@ -437,7 +437,7 @@ Downloading Composer dependencies without authentication is deprecated in GitLab
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The Container Registry supports [authentication](https://gitlab.com/gitlab-org/container-registry/-/blob/master/docs/configuration.md#auth) with `htpasswd`. It relies on an [Apache `htpasswd` file](https://httpd.apache.org/docs/2.4/programs/htpasswd.html), with passwords hashed using `bcrypt`.
|
||||
|
|
@ -453,7 +453,7 @@ Since it isn't used in the context of GitLab (the product), `htpasswd` authentic
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `user_email_lookup_limit` [API field](https://docs.gitlab.com/ee/api/settings.html) is deprecated and will be removed in GitLab 15.0. Until GitLab 15.0, `user_email_lookup_limit` is aliased to `search_rate_limit` and existing workflows will continue to work.
|
||||
|
|
@ -487,7 +487,7 @@ This change is part of regular maintenance to keep our codebase clean.
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
All functionality related to GitLab's Container Network Security and Container Host Security categories is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. Users who need a replacement for this functionality are encouraged to evaluate the following open source projects as potential solutions that can be installed and managed outside of GitLab: [AppArmor](https://gitlab.com/apparmor/apparmor), [Cilium](https://github.com/cilium/cilium), [Falco](https://github.com/falcosecurity/falco), [FluentD](https://github.com/fluent/fluentd), [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/). To integrate these technologies into GitLab, add the desired Helm charts into your copy of the [Cluster Management Project Template](https://docs.gitlab.com/ee/user/clusters/management_project_template.html). Deploy these Helm charts in production by calling commands through GitLab [CI/CD](https://docs.gitlab.com/ee/user/clusters/agent/ci_cd_workflow.html).
|
||||
|
|
@ -510,7 +510,7 @@ For additional context, or to provide feedback regarding this change, please ref
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
For those using Dependency Scanning for Python projects, we are deprecating the default `gemnasium-python:2` image which uses Python 3.6 as well as the custom `gemnasium-python:2-python-3.9` image which uses Python 3.9. The new default image as of GitLab 15.0 will be for Python 3.9 as it is a [supported version](https://endoflife.date/python) and 3.6 [is no longer supported](https://endoflife.date/python).
|
||||
|
|
@ -581,7 +581,7 @@ The following `geo:db:*` tasks will be replaced with their corresponding `db:*:g
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The feature flag `PUSH_RULES_SUPERSEDE_CODE_OWNERS` is being removed in GitLab 15.0. Upon its removal, push rules will supersede CODEOWNERS. The CODEOWNERS feature will no longer be available for access control.
|
||||
|
|
@ -595,7 +595,7 @@ The feature flag `PUSH_RULES_SUPERSEDE_CODE_OWNERS` is being removed in GitLab 1
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Using environment variables `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configure Gitaly is [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/352609).
|
||||
|
|
@ -613,7 +613,7 @@ GitLab instances that use `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configu
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Elasticsearch 6.8 is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0.
|
||||
|
|
@ -631,7 +631,7 @@ Elasticsearch 6.8 is also incompatible with Amazon OpenSearch, which we [plan to
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The [external status check API](https://docs.gitlab.com/ee/api/status_checks.html) was originally implemented to
|
||||
|
|
@ -659,7 +659,7 @@ To align with this change, API calls to list external status checks will also re
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-04-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
We are removing a non-standard extension to our GraphQL processor, which we added for backwards compatibility. This extension modifies the validation of GraphQL queries, allowing the use of the `ID` type for arguments where it would normally be rejected.
|
||||
|
|
@ -723,7 +723,7 @@ an inline argument expression).
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
By default, all new applications expire access tokens after 2 hours. In GitLab 14.2 and earlier, OAuth access tokens
|
||||
|
|
@ -745,7 +745,7 @@ tokens before GitLab 15.0 is released:
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The feature to disable enforcement of PAT expiration is unusual from a security perspective.
|
||||
|
|
@ -761,7 +761,7 @@ Unexpected behavior in a security feature is inherently dangerous, so we have de
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The feature to disable enforcement of SSH expiration is unusual from a security perspective.
|
||||
|
|
@ -777,7 +777,7 @@ Unexpected behavior in a security feature is inherently dangerous, so we have de
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The [GitLab SAST SpotBugs analyzer](https://gitlab.com/gitlab-org/security-products/analyzers/spotbugs) scans [Java, Scala, Groovy, and Kotlin code](https://docs.gitlab.com/ee/user/application_security/sast/#supported-languages-and-frameworks) for security vulnerabilities.
|
||||
|
|
@ -802,7 +802,7 @@ If you rely on Java 8 being present in the analyzer environment, you must take a
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTrendsMeasurements` in 13.10 and the old field name has been marked as deprecated. To fix the existing GraphQL queries, replace `instanceStatisticsMeasurements` with `usageTrendsMeasurements`.
|
||||
|
|
@ -816,7 +816,7 @@ The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTren
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-04-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GitLab Runner REST endpoints will stop accepting `paused` or `active` as a status value in GitLab 16.0.
|
||||
|
|
@ -836,7 +836,7 @@ When checking for active runners, specify `paused=false`.
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-04-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `GET /groups/:id/runners?type=project_type` endpoint will be removed in GitLab 16.0. The endpoint always returned an empty collection.
|
||||
|
|
@ -850,7 +850,7 @@ The `GET /groups/:id/runners?type=project_type` endpoint will be removed in GitL
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-04-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Occurrences of the `active` identifier in the GitLab Runner REST and GraphQL API endpoints will be
|
||||
|
|
@ -882,7 +882,7 @@ existing runners.
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
[Request profiling](https://docs.gitlab.com/ee/administration/monitoring/performance/request_profiling.html) is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0.
|
||||
|
|
@ -902,7 +902,7 @@ For more information, check the [summary section of the deprecation issue](https
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The [required pipeline configuration](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration) feature is deprecated in GitLab 14.8 for Premium customers and is scheduled for removal in GitLab 15.0. This feature is not deprecated for GitLab Ultimate customers.
|
||||
|
|
@ -921,7 +921,7 @@ This change will also help GitLab remain consistent in its tiering strategy with
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As of 14.8 the retire.js job is being deprecated from Dependency Scanning. It will continue to be included in our CI/CD template while deprecated. We are removing retire.js from Dependency Scanning on May 22, 2022 in GitLab 15.0. JavaScript scanning functionality will not be affected as it is still being covered by Gemnasium.
|
||||
|
|
@ -937,7 +937,7 @@ If you have explicitly excluded retire.js using DS_EXCLUDED_ANALYZERS you will n
|
|||
Planned removal: GitLab <span class="removal-milestone">15.4</span> (2022-09-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab SAST uses various [analyzers](https://docs.gitlab.com/ee/user/application_security/sast/analyzers/) to scan code for vulnerabilities.
|
||||
|
|
@ -980,7 +980,7 @@ If you applied customizations to any of the affected analyzers or if you current
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GitLab SAST Security Code Scan analyzer scans .NET code for security vulnerabilities.
|
||||
|
|
@ -1037,7 +1037,7 @@ For further details, see [the deprecation issue for this change](https://gitlab.
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab uses various [analyzers](https://docs.gitlab.com/ee/user/application_security/terminology/#analyzer) to [scan for security vulnerabilities](https://docs.gitlab.com/ee/user/application_security/).
|
||||
|
|
@ -1065,7 +1065,7 @@ See the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352564
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The Secure and Protect stages will be bumping the major versions of their analyzers in tandem with the GitLab 15.0 release. This major bump will enable a clear delineation for analyzers, between:
|
||||
|
|
@ -1110,7 +1110,7 @@ Specifically, the following are being deprecated and will no longer be updated a
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Although not recommended or documented, it was possible to deploy a gRPC-aware proxy between Gitaly and
|
||||
|
|
@ -1134,7 +1134,7 @@ the [relevant epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/463).
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
To simplify setting a test coverage pattern, in GitLab 15.0 the
|
||||
|
|
@ -1153,7 +1153,7 @@ testing coverage results in merge requests.
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The vulnerability check feature is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. We encourage you to migrate to the new security approvals feature instead. You can do so by navigating to **Security & Compliance > Policies** and creating a new Scan Result Policy.
|
||||
|
|
@ -1174,7 +1174,7 @@ The new security approvals feature is similar to vulnerability check. For exampl
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-04-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in GitLab 9.0, and will be removed in GitLab 16.0. If you still use these variables, be sure to change to the replacement [predefined variables](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html) which are functionally identical:
|
||||
|
|
@ -1203,7 +1203,7 @@ The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in G
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `projectFingerprint` field in the [PipelineSecurityReportFinding](https://docs.gitlab.com/ee/api/graphql/reference/index.html#pipelinesecurityreportfinding)
|
||||
|
|
@ -1220,7 +1220,7 @@ exposed in the UUID field. Data previously available in the projectFingerprint f
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `started` field in the [iterations API](https://docs.gitlab.com/ee/api/iterations.html#list-project-iterations) is being deprecated and will be removed in GitLab 15.0. This field is being replaced with the `current` field (already available) which aligns with the naming for other time-based entities, such as milestones.
|
||||
|
|
@ -1359,7 +1359,7 @@ and will remove it in GitLab 15.0
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The logging features in GitLab allow users to install the ELK stack (Elasticsearch, Logstash, and Kibana) to aggregate and manage application logs. Users can search for relevant logs in GitLab. However, since deprecating certificate-based integration with Kubernetes clusters and GitLab Managed Apps, we don't have a recommended solution for logging within GitLab. For more information, you can follow the issue for [integrating Opstrace with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976).
|
||||
|
|
@ -1373,7 +1373,7 @@ The logging features in GitLab allow users to install the ELK stack (Elasticsear
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
By displaying data stored in a Prometheus instance, GitLab allows users to view performance metrics. GitLab also displays visualizations of these metrics in dashboards. The user can connect to a previously-configured external Prometheus instance, or set up Prometheus as a GitLab Managed App.
|
||||
|
|
@ -1445,7 +1445,7 @@ in the Vulnerability Report.
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Exporting Sidekiq metrics and health checks using a single process and port is deprecated.
|
||||
|
|
@ -1489,7 +1489,7 @@ Current users of the Static Site Editor can view the [documentation](https://doc
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distributed tracing system. GitLab users can navigate to their Jaeger instance to gain insight into the performance of a deployed application, tracking each function or microservice that handles a given request. Tracing in GitLab is deprecated in GitLab 14.7, and scheduled for removal in 15.0. To track work on a possible replacement, see the issue for [Opstrace integration with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976).
|
||||
|
|
@ -1503,7 +1503,7 @@ Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distr
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Currently, test coverage visualizations in GitLab only support Cobertura reports. Starting 15.0, the
|
||||
|
|
@ -1520,7 +1520,7 @@ only supported report file in 15.0, but this is the first step towards GitLab su
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `merged_by` field in the [merge request API](https://docs.gitlab.com/ee/api/merge_requests.html#list-merge-requests) is being deprecated and will be removed in GitLab 15.0. This field is being replaced with the `merge_user` field (already present in GraphQL) which more correctly identifies who merged a merge request when performing actions (merge when pipeline succeeds, add to merge train) other than a simple merge.
|
||||
|
|
@ -1539,7 +1539,7 @@ The `merged_by` field in the [merge request API](https://docs.gitlab.com/ee/api/
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 15.0 we are going to limit the number of characters in CI/CD job names to 255. Any pipeline with job names that exceed the 255 character limit will stop working after the 15.0 release.
|
||||
|
|
@ -1553,7 +1553,7 @@ In GitLab 15.0 we are going to limit the number of characters in CI/CD job names
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
We deprecated legacy names for approval status of license policy (blacklisted, approved) in the `managed_licenses` API but they are still used in our API queries and responses. They will be removed in 15.0.
|
||||
|
|
@ -1569,7 +1569,7 @@ If you are using our License Compliance API you should stop using the `approved`
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines that use these keywords will stop working, so you must switch to `stage` and `stages`, which have the same behavior.
|
||||
|
|
@ -1583,7 +1583,7 @@ The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The API Fuzzing configuration snippet is now being generated client-side and does not require an
|
||||
|
|
@ -1599,7 +1599,7 @@ which isn't being used in GitLab anymore.
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As of 14.6 bundler-audit is being deprecated from Dependency Scanning. It will continue to be in our CI/CD template while deprecated. We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. After this removal Ruby scanning functionality will not be affected as it is still being covered by Gemnasium.
|
||||
|
|
@ -1620,7 +1620,7 @@ If you have explicitly excluded bundler-audit using DS_EXCLUDED_ANALYZERS you wi
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 15.0, you can no longer change an instance (shared) runner to a project (specific) runner.
|
||||
|
|
@ -1638,7 +1638,7 @@ Administrators who need to add runners for multiple projects can register a runn
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml` file. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor.
|
||||
|
|
@ -1654,7 +1654,7 @@ In GitLab 15.0 and later, the default value for this configuration option will c
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
A request to the API for `/api/v4/projects/:id/packages` returns a paginated result of packages. Each package lists all of its pipelines in this response. This is a performance concern, as it's possible for a package to have hundreds or thousands of associated pipelines.
|
||||
|
|
@ -1670,7 +1670,7 @@ In milestone 16.0, we will remove the `pipelines` attribute from the API respons
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-04-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 16.0.
|
||||
|
|
@ -1690,7 +1690,7 @@ When checking if a runner is `paused`, API users are advised to check the boolea
|
|||
Planned removal: GitLab <span class="removal-milestone">15.6</span> (2022-11-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The certificate-based integration with Kubernetes will be [deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). As a GitLab SaaS customer, on new namespaces, you will no longer be able to integrate GitLab and your cluster using the certificate-based approach as of GitLab 15.0. The integration for current users will be enabled per namespace. The integrations are expected to be switched off completely on GitLab SaaS around 2022 November 22.
|
||||
|
|
@ -1711,7 +1711,7 @@ GitLab self-managed customers can still use the feature [with a feature flag](ht
|
|||
Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The certificate-based integration with Kubernetes [will be deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/).
|
||||
|
|
@ -1734,7 +1734,7 @@ For updates and details about this deprecation, follow [this epic](https://gitla
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 SP2 [ended on March 31, 2021](https://www.suse.com/lifecycle/). The CA certificates on SP2 include the expired DST root certificate, and it's not getting new CA certificate package updates. We have implemented some [workarounds](https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/merge_requests/191), but we will not be able to continue to keep the build running properly.
|
||||
|
|
@ -1748,7 +1748,7 @@ Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In milestone 15.0, support for the `tags` and `tags_count` parameters will be removed from the Container Registry API that [gets registry repositories from a group](../api/container_registry.md#within-a-group).
|
||||
|
|
@ -1764,7 +1764,7 @@ The `GET /groups/:id/registry/repositories` endpoint will remain, but won't retu
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
We are changing how the date filter works in Value Stream Analytics. Instead of filtering by the time that the issue or merge request was created, the date filter will filter by the end event time of the given stage. This will result in completely different figures after this change has rolled out.
|
||||
|
|
@ -1780,7 +1780,7 @@ If you monitor Value Stream Analytics metrics and rely on the date filter, to av
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `Version` type for the basic `PackageType` type and moved it to [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype).
|
||||
|
|
@ -1796,7 +1796,7 @@ In milestone 15.0, we will completely remove `Version` from `PackageType`.
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprecated and will be removed in GitLab 15.0. For projects with a commit message template set, it will ignore the template.
|
||||
|
|
@ -1810,7 +1810,7 @@ The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprec
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
We added a feature flag because [GitLab-#11582](https://gitlab.com/gitlab-org/gitlab/-/issues/11582) changed how public groups use the Dependency Proxy. Prior to this change, you could use the Dependency Proxy without authentication. The change requires authentication to use the Dependency Proxy.
|
||||
|
|
@ -1826,7 +1826,7 @@ In milestone 15.0, we will remove the feature flag entirely. Moving forward, you
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GraphQL, there are two `pipelines` fields that you can use in a [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/#packagedetailstype) to get the pipelines for package versions:
|
||||
|
|
@ -1845,7 +1845,7 @@ To mitigate possible performance problems, we will remove the `versions` field's
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-db` which is used to promote database nodes in multi-node Geo secondary sites. `gitlab-ctl promote-db` will continue to function as-is and be available until GitLab 15.0. We recommend that Geo customers begin testing the new `gitlab-ctl promote` command in their staging environments and incorporating the new command in their failover procedures.
|
||||
|
|
@ -1859,7 +1859,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-to-primary-node` which was only usable for single-node Geo sites. `gitlab-ctl promote-to-primary-node` will continue to function as-is and be available until GitLab 15.0. We recommend that Geo customers begin testing the new `gitlab-ctl promote` command in their staging environments and incorporating the new command in their failover procedures.
|
||||
|
|
@ -1890,7 +1890,7 @@ Starting in 14.5 we are providing packages for openSUSE Leap 15.3, and will stop
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#removed-events) are now deprecated and will be removed in GitLab 15.0.
|
||||
|
|
@ -1908,7 +1908,7 @@ dramatically slow down GitLab instances. For this reason, they are being removed
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
[GitLab Serverless](https://docs.gitlab.com/ee/user/project/clusters/serverless/) is a feature set to support Knative-based serverless development with automatic deployments and monitoring.
|
||||
|
|
@ -1924,7 +1924,7 @@ We decided to remove the GitLab Serverless features as they never really resonat
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html)
|
||||
|
|
@ -1942,7 +1942,7 @@ This deprecation mainly impacts users compiling GitLab from source because Omnib
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `omniauth-kerberos` gem will be removed in our next major release, GitLab 15.0.
|
||||
|
|
@ -2010,7 +2010,7 @@ We encourage customers currently using NFS for Git repositories to plan their mi
|
|||
Planned removal: GitLab <span class="removal-milestone">15.0</span> (2022-05-22)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The OAuth implicit grant authorization flow will be removed in our next major release, GitLab 15.0. Any applications that use OAuth implicit grant should switch to alternative [supported OAuth flows](https://docs.gitlab.com/ee/api/oauth2.html).
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ The minimum supported browser versions are:
|
|||
### API: `stale` status returned instead of `offline` or `not_connected`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The Runner [API](https://docs.gitlab.com/ee/api/runners.html#runners-api) endpoints have changed in 15.0.
|
||||
|
|
@ -68,7 +68,7 @@ The `not_connected` status is no longer valid. It was replaced with `never_conta
|
|||
### Audit events for repository push events
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#removed-events) are removed as of GitLab 15.0.
|
||||
|
|
@ -81,7 +81,7 @@ Please note that we will add high-volume audit events in the future as part of [
|
|||
### Background upload for object storage
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
To reduce the overall complexity and maintenance burden of GitLab's [object storage feature](https://docs.gitlab.com/ee/administration/object_storage.html), support for using `background_upload` has been removed in GitLab 15.0.
|
||||
|
|
@ -127,7 +127,7 @@ This workaround will be dropped, so we encourage migrating to consolidated objec
|
|||
### Container Network and Host Security
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
All functionality related to the Container Network Security and Container Host Security categories was deprecated in GitLab 14.8 and is scheduled for removal in GitLab 15.0. Users who need a replacement for this functionality are encouraged to evaluate the following open source projects as potential solutions that can be installed and managed outside of GitLab: [AppArmor](https://gitlab.com/apparmor/apparmor), [Cilium](https://github.com/cilium/cilium), [Falco](https://github.com/falcosecurity/falco), [FluentD](https://github.com/fluent/fluentd), [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/). To integrate these technologies with GitLab, add the desired Helm charts in your copy of the [Cluster Management Project Template](https://docs.gitlab.com/ee/user/clusters/management_project_template.html). Deploy these Helm charts in production by calling commands through GitLab [CI/CD](https://docs.gitlab.com/ee/user/clusters/agent/ci_cd_workflow.html).
|
||||
|
|
@ -144,7 +144,7 @@ For additional context, or to provide feedback regarding this change, please ref
|
|||
### Container registry authentication with htpasswd
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The Container Registry supports [authentication](https://gitlab.com/gitlab-org/container-registry/-/blob/master/docs/configuration.md#auth) with `htpasswd`. It relies on an [Apache `htpasswd` file](https://httpd.apache.org/docs/2.4/programs/htpasswd.html), with passwords hashed using `bcrypt`.
|
||||
|
|
@ -177,7 +177,7 @@ The following `geo:db:*` tasks have been removed from GitLab 15.0 and have been
|
|||
### DS_DEFAULT_ANALYZERS environment variable
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
We are removing the `DS_DEFAULT_ANALYZERS` environment variable from Dependency Scanning on May 22, 2022 in 15.0. After this removal, this variable's value will be ignored. To configure which analyzers to run with the default configuration, you should use the `DS_EXCLUDED_ANALYZERS` variable instead.
|
||||
|
|
@ -185,7 +185,7 @@ We are removing the `DS_DEFAULT_ANALYZERS` environment variable from Dependency
|
|||
### Dependency Scanning default Java version changed to 17
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
For Dependency Scanning, the default version of Java that the scanner expects will be updated from 11 to 17. Java 17 is [the most up-to-date Long Term Support (LTS) version](https://en.wikipedia.org/wiki/Java_version_history). Dependency Scanning continues to support the same [range of versions (8, 11, 13, 14, 15, 16, 17)](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#supported-languages-and-package-managers), only the default version is changing. If your project uses the previous default of Java 11, be sure to [set the `DS_JAVA_VERSION` variable to match](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning). Please note that consequently the default version of Gradle is now 7.3.3.
|
||||
|
|
@ -193,7 +193,7 @@ For Dependency Scanning, the default version of Java that the scanner expects wi
|
|||
### ELK stack logging
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The logging features in GitLab allow users to install the ELK stack (Elasticsearch, Logstash, and Kibana) to aggregate and manage application logs. Users could search for relevant logs in GitLab directly. However, since deprecating certificate-based integration with Kubernetes clusters and GitLab Managed Apps, this feature is no longer available. For more information on the future of logging and observability, you can follow the issue for [integrating Opstrace with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976).
|
||||
|
|
@ -201,7 +201,7 @@ The logging features in GitLab allow users to install the ELK stack (Elasticsear
|
|||
### Elasticsearch 6.8.x in GitLab 15.0
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Elasticsearch 6.8 support has been removed in GitLab 15.0. Elasticsearch 6.8 has reached [end of life](https://www.elastic.co/support/eol).
|
||||
|
|
@ -213,7 +213,7 @@ View the [version requirements](https://docs.gitlab.com/ee/integration/elasticse
|
|||
### End of support for Python 3.6 in Dependency Scanning
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
For those using Dependency Scanning for Python projects, we are removing support for the default `gemnasium-python:2` image which uses Python 3.6, as well as the custom `gemnasium-python:2-python-3.9` image which uses Python 3.9. The new default image as of GitLab 15.0 will be for Python 3.9 as it is a [supported version](https://endoflife.date/python) and 3.6 [is no longer supported](https://endoflife.date/python).
|
||||
|
|
@ -221,7 +221,7 @@ For those using Dependency Scanning for Python projects, we are removing support
|
|||
### External status check API breaking changes
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The [external status check API](https://docs.gitlab.com/ee/api/status_checks.html) was originally implemented to
|
||||
|
|
@ -243,7 +243,7 @@ To align with this change, API calls to list external status checks also return
|
|||
### GitLab Serverless
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
All functionality related to GitLab Serverless was deprecated in GitLab 14.3 and is scheduled for removal in GitLab 15.0. Users who need a replacement for this functionality are encouraged to explore using the following technologies with GitLab CI/CD:
|
||||
|
|
@ -256,7 +256,7 @@ For additional context, or to provide feedback regarding this change, please ref
|
|||
### Gitaly nodes in virtual storage
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Configuring the Gitaly nodes directly in the virtual storage's root configuration object has been deprecated in GitLab 13.12 and is no longer supported in GitLab 15.0. You must move the Gitaly nodes under the `'nodes'` key as described in [the Praefect configuration](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#praefect).
|
||||
|
|
@ -264,7 +264,7 @@ Configuring the Gitaly nodes directly in the virtual storage's root configuratio
|
|||
### GraphQL permissions change for Package settings
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GitLab Package stage offers a Package Registry, Container Registry, and Dependency Proxy to help you manage all of your dependencies using GitLab. Each of these product categories has a variety of settings that can be adjusted using the API.
|
||||
|
|
@ -281,7 +281,7 @@ The issue for this removal is [GitLab-#350682](https://gitlab.com/gitlab-org/git
|
|||
### Jaeger integration
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distributed tracing system. GitLab users could previously navigate to their Jaeger instance to gain insight into the performance of a deployed application, tracking each function or microservice that handles a given request. Tracing in GitLab was deprecated in GitLab 14.7, and removed in 15.0. To track work on a possible replacement, see the issue for [Opstrace integration with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976).
|
||||
|
|
@ -289,7 +289,7 @@ Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distr
|
|||
### Known host required for GitLab Runner SSH executor
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml`. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor.
|
||||
|
|
@ -307,7 +307,7 @@ We have now removed the deprecated legacy names for approval status of license p
|
|||
### Move Gitaly Cluster Praefect `database_host_no_proxy` and `database_port_no_proxy configs`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The Gitaly Cluster configuration keys for `praefect['database_host_no_proxy']` and `praefect['database_port_no_proxy']` are replaced with `praefect['database_direct_host']` and `praefect['database_direct_port']`.
|
||||
|
|
@ -315,7 +315,7 @@ The Gitaly Cluster configuration keys for `praefect['database_host_no_proxy']` a
|
|||
### Move `custom_hooks_dir` setting from GitLab Shell to Gitaly
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks.html#create-a-global-server-hook-for-all-repositories) setting is now configured in Gitaly, and is removed from GitLab Shell in GitLab 15.0.
|
||||
|
|
@ -323,7 +323,7 @@ The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks.
|
|||
### OAuth implicit grant
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The OAuth implicit grant authorization flow is no longer supported. Any applications that use OAuth implicit grant must switch to alternative [supported OAuth flows](https://docs.gitlab.com/ee/api/oauth2.html).
|
||||
|
|
@ -331,7 +331,7 @@ The OAuth implicit grant authorization flow is no longer supported. Any applicat
|
|||
### OAuth tokens without an expiration
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab no longer supports OAuth tokens [without an expiration](https://docs.gitlab.com/ee/integration/oauth_provider.html#expiring-access-tokens).
|
||||
|
|
@ -341,7 +341,7 @@ Any existing token without an expiration has one automatically generated and app
|
|||
### Optional enforcement of SSH expiration
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Disabling SSH expiration enforcement is unusual from a security perspective and could create unusual situations where an expired
|
||||
|
|
@ -351,7 +351,7 @@ expiration on all SSH keys.
|
|||
### Optional enforcement of personal access token expiration
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Allowing expired personal access tokens to be used is unusual from a security perspective and could create unusual situations where an
|
||||
|
|
@ -376,7 +376,7 @@ If you rely on Java 8 being present in the analyzer environment, you must take a
|
|||
### Pipelines field from the version field
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GraphQL, there are two `pipelines` fields that you can use in a [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/#packagedetailstype) to get the pipelines for package versions:
|
||||
|
|
@ -389,7 +389,7 @@ To mitigate possible performance problems, we will remove the `versions` field's
|
|||
### Pseudonymizer
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The Pseudonymizer feature is generally unused, can cause production issues with large databases, and can interfere with object storage development.
|
||||
|
|
@ -398,7 +398,7 @@ It was removed in GitLab 15.0.
|
|||
### Request profiling
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
[Request profiling](https://docs.gitlab.com/ee/administration/monitoring/performance/request_profiling.html) has been removed in GitLab 15.0.
|
||||
|
|
@ -412,7 +412,7 @@ For more information, check the [summary section of the deprecation issue](https
|
|||
### Required pipeline configurations in Premium tier
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
[Required pipeline configuration](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration) helps to define and mandate organization-wide pipeline configurations and is a requirement at an executive and organizational level. To align better with our [pricing philosophy](https://about.gitlab.com/company/pricing/#three-tiers), this feature is removed from the Premium tier in GitLab 15.0. This feature continues to be available in the GitLab Ultimate tier.
|
||||
|
|
@ -427,7 +427,7 @@ This change also helps GitLab remain consistent in our tiering strategy with the
|
|||
### Retire-JS Dependency Scanning tool
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
We have removed support for retire.js from Dependency Scanning as of May 22, 2022 in GitLab 15.0. JavaScript scanning functionality will not be affected as it is still being covered by Gemnasium.
|
||||
|
|
@ -437,7 +437,7 @@ If you have explicitly excluded retire.js using the `DS_EXCLUDED_ANALYZERS` vari
|
|||
### Runner status `not_connected` API value
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GitLab Runner REST and GraphQL [API](https://docs.gitlab.com/ee/api/runners.html#runners-api) endpoints
|
||||
|
|
@ -470,7 +470,7 @@ If you rely on .NET 2.1 support being present in the analyzer image by default,
|
|||
### SUSE Linux Enterprise Server 12 SP2
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 SP2 [ended on March 31, 2021](https://www.suse.com/lifecycle/). The CA certificates on SP2 include the expired DST root certificate, and it's not getting new CA certificate package updates. We have implemented some [workarounds](https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/merge_requests/191), but we will not be able to continue to keep the build running properly.
|
||||
|
|
@ -496,7 +496,7 @@ For further details, see [the deprecation issue for this change](https://gitlab.
|
|||
### Self-managed certificate-based integration with Kubernetes feature flagged
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In 15.0 the certificate-based integration with Kubernetes will be disabled by default.
|
||||
|
|
@ -512,7 +512,7 @@ For updates and details, follow [this epic](https://gitlab.com/groups/gitlab-org
|
|||
### Sidekiq configuration for metrics and health checks
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 15.0, you can no longer serve Sidekiq metrics and health checks over a single address and port.
|
||||
|
|
@ -536,7 +536,7 @@ The Static Site Editor was deprecated in GitLab 14.7 and the feature is being re
|
|||
### Support for `gitaly['internal_socket_dir']`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Gitaly introduced a new directory that holds all runtime data Gitaly requires to operate correctly. This new directory replaces the old internal socket directory, and consequentially the usage of `gitaly['internal_socket_dir']` was deprecated in favor of `gitaly['runtime_dir']`.
|
||||
|
|
@ -544,7 +544,7 @@ Gitaly introduced a new directory that holds all runtime data Gitaly requires to
|
|||
### Support for legacy format of `config/database.yml`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The syntax of [GitLab's database](https://docs.gitlab.com/omnibus/settings/database.html)
|
||||
|
|
@ -558,7 +558,7 @@ Instructions are available [in the source update documentation](https://docs.git
|
|||
### Test coverage project CI/CD setting
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
To specify a test coverage pattern, in GitLab 15.0 the
|
||||
|
|
@ -571,7 +571,7 @@ To set test coverage parsing, use the project’s `.gitlab-ci.yml` file by provi
|
|||
### The `promote-db` command is no longer available from `gitlab-ctl`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-db` which is used to promote database nodes in multi-node Geo secondary sites. The `gitlab-ctl promote-db` command has been removed in GitLab 15.0.
|
||||
|
|
@ -579,7 +579,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge
|
|||
### Update to the Container Registry group-level API
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 15.0, support for the `tags` and `tags_count` parameters will be removed from the Container Registry API that [gets registry repositories from a group](../api/container_registry.md#within-a-group).
|
||||
|
|
@ -589,7 +589,7 @@ The `GET /groups/:id/registry/repositories` endpoint will remain, but won't retu
|
|||
### Versions from `PackageType`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `Version` type for the basic `PackageType` type and moved it to [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype).
|
||||
|
|
@ -599,7 +599,7 @@ In GitLab 15.0, we will completely remove `Version` from `PackageType`.
|
|||
### Vulnerability Check
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The vulnerability check feature was deprecated in GitLab 14.8 and is scheduled for removal in GitLab 15.0. We encourage you to migrate to the new security approvals feature instead. You can do so by navigating to **Security & Compliance > Policies** and creating a new Scan Result Policy.
|
||||
|
|
@ -614,7 +614,7 @@ The new security approvals feature is similar to vulnerability check. For exampl
|
|||
### `Managed-Cluster-Applications.gitlab-ci.yml`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `Managed-Cluster-Applications.gitlab-ci.yml` CI/CD template is being removed. If you need an alternative, try the [Cluster Management project template](https://gitlab.com/gitlab-org/gitlab/-/issues/333610) instead. If your are not ready to move, you can copy the [last released version](https://gitlab.com/gitlab-org/gitlab-foss/-/blob/v14.10.1/lib/gitlab/ci/templates/Managed-Cluster-Applications.gitlab-ci.yml) of the template into your project.
|
||||
|
|
@ -622,7 +622,7 @@ The `Managed-Cluster-Applications.gitlab-ci.yml` CI/CD template is being removed
|
|||
### `artifacts:reports:cobertura` keyword
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As of GitLab 15.0, the [`artifacts:reports:cobertura`](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportscobertura-removed)
|
||||
|
|
@ -633,7 +633,7 @@ Cobertura is the only supported report file, but this is the first step towards
|
|||
### `defaultMergeCommitMessageWithDescription` GraphQL API field
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GraphQL API field `defaultMergeCommitMessageWithDescription` has been removed in GitLab 15.0. For projects with a commit message template set, it will ignore the template.
|
||||
|
|
@ -641,7 +641,7 @@ The GraphQL API field `defaultMergeCommitMessageWithDescription` has been remove
|
|||
### `dependency_proxy_for_private_groups` feature flag
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
A feature flag was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/11582) in GitLab 13.7 as part of the change to require authentication to use the Dependency Proxy. Before GitLab 13.7, you could use the Dependency Proxy without authentication.
|
||||
|
|
@ -651,7 +651,7 @@ In GitLab 15.0, we will remove the feature flag, and you must always authenticat
|
|||
### `omniauth-kerberos` gem
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `omniauth-kerberos` gem is no longer supported. This gem has not been maintained and has very little usage. Therefore, we
|
||||
|
|
@ -664,7 +664,7 @@ We are not removing Kerberos SPNEGO integration. We are removing the old passwor
|
|||
### `promote-to-primary-node` command from `gitlab-ctl`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-to-primary-node` which was only usable for single-node Geo sites. `gitlab-ctl promote-to-primary-node` has been removed in GitLab 15.0.
|
||||
|
|
@ -672,7 +672,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge
|
|||
### `push_rules_supersede_code_owners` feature flag
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `push_rules_supersede_code_owners` feature flag has been removed in GitLab 15.0. From now on, push rules will supersede the `CODEOWNERS` file. The code owners feature is no longer available for access control.
|
||||
|
|
@ -680,7 +680,7 @@ The `push_rules_supersede_code_owners` feature flag has been removed in GitLab 1
|
|||
### `type` and `types` keyword from CI/CD configuration
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `type` and `types` CI/CD keywords is removed in GitLab 15.0, so pipelines that use these keywords fail with a syntax error. Switch to `stage` and `stages`, which have the same behavior.
|
||||
|
|
@ -688,7 +688,7 @@ The `type` and `types` CI/CD keywords is removed in GitLab 15.0, so pipelines th
|
|||
### bundler-audit Dependency Scanning tool
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. After this removal, Ruby scanning functionality will not be affected as it is still being covered by Gemnasium.
|
||||
|
|
@ -700,7 +700,7 @@ If you have explicitly excluded bundler-audit using the `DS_EXCLUDED_ANALYZERS`
|
|||
### Permissions change for downloading Composer dependencies
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The GitLab Composer repository can be used to push, search, fetch metadata about, and download PHP dependencies. All these actions require authentication, except for downloading dependencies.
|
||||
|
|
@ -712,7 +712,7 @@ Downloading Composer dependencies without authentication is deprecated in GitLab
|
|||
### Integrated error tracking disabled by default
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 14.4, GitLab released an integrated error tracking backend that replaces Sentry. This feature caused database performance issues. In GitLab 14.9, integrated error tracking is removed from GitLab.com, and turned off by default in GitLab self-managed. While we explore the future development of this feature, please consider switching to the Sentry backend by [changing your error tracking to Sentry in your project settings](https://docs.gitlab.com/ee/operations/error_tracking.html#sentry-error-tracking).
|
||||
|
|
@ -783,7 +783,7 @@ The minimum supported browser versions are:
|
|||
### Auto Deploy CI template v1
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 14.0, we will update the [Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/stages.html#auto-deploy) CI template to the latest version. This includes new features, bug fixes, and performance improvements with a dependency on the v2 [auto-deploy-image](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image). Auto Deploy CI template v1 is deprecated going forward.
|
||||
|
|
@ -793,7 +793,7 @@ Since the v1 and v2 versions are not backward-compatible, your project might enc
|
|||
### Breaking changes to Terraform CI template
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab 14.0 renews the Terraform CI template to the latest version. The new template is set up for the GitLab Managed Terraform state, with a dependency on the GitLab `terraform-images` image, to provide a good user experience around GitLab's Infrastructure-as-Code features.
|
||||
|
|
@ -803,7 +803,7 @@ The current stable and latest templates are not compatible, and the current late
|
|||
### Code Quality RuboCop support changed
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
By default, the Code Quality feature has not provided support for Ruby 2.6+ if you're using the Code Quality template. To better support the latest versions of Ruby, the default RuboCop version is updated to add support for Ruby 2.4 through 3.0. As a result, support for Ruby 2.1, 2.2, and 2.3 is removed. You can re-enable support for older versions by [customizing your configuration](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html#rubocop-errors).
|
||||
|
|
@ -813,7 +813,7 @@ Relevant Issue: [Default `codeclimate-rubocop` engine does not support Ruby 2.6+
|
|||
### Container Scanning Engine Clair
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Clair, the default container scanning engine, was deprecated in GitLab 13.9 and is removed from GitLab 14.0 and replaced by Trivy. We advise customers who are customizing variables for their container scanning job to [follow these instructions](https://docs.gitlab.com/ee/user/application_security/container_scanning/#change-scanners) to ensure that their container scanning jobs continue to work.
|
||||
|
|
@ -821,7 +821,7 @@ Clair, the default container scanning engine, was deprecated in GitLab 13.9 and
|
|||
### DAST default template stages
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 14.0, we've removed the stages defined in the current `DAST.gitlab-ci.yml` template to avoid the situation where the template overrides manual changes made by DAST users. We're making this change in response to customer issues where the stages in the template cause problems when used with customized DAST configurations. Because of this removal, `gitlab-ci.yml` configurations that do not specify a `dast` stage must be updated to include this stage.
|
||||
|
|
@ -829,7 +829,7 @@ In GitLab 14.0, we've removed the stages defined in the current `DAST.gitlab-ci.
|
|||
### DAST environment variable renaming and removal
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab 13.8 renamed multiple environment variables to support their broader usage in different workflows. In GitLab 14.0, the old variables have been permanently removed and will no longer work. Any configurations using these variables must be updated to the new variable names. Any scans using these variables in GitLab 14.0 and later will fail to be configured correctly. These variables are:
|
||||
|
|
@ -846,7 +846,7 @@ GitLab 13.8 renamed multiple environment variables to support their broader usag
|
|||
### Default Browser Performance testing job renamed in GitLab 14.0
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Browser Performance Testing has run in a job named `performance` by default. With the introduction of [Load Performance Testing](https://docs.gitlab.com/ee/user/project/merge_requests/load_performance_testing.html) in GitLab 13.2, this naming could be confusing. To make it clear which job is running [Browser Performance Testing](https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html), the default job name is changed from `performance` to `browser_performance` in the template in GitLab 14.0.
|
||||
|
|
@ -856,7 +856,7 @@ Relevant Issue: [Rename default Browser Performance Testing job](https://gitlab.
|
|||
### Default DAST spider begins crawling at target URL
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab 14.0, DAST has removed the current method of resetting the scan to the hostname when starting to spider. Prior to GitLab 14.0, the spider would not begin at the specified target path for the URL but would instead reset the URL to begin crawling at the host root. GitLab 14.0 changes the default for the new variable `DAST_SPIDER_START_AT_HOST` to `false` to better support users' intention of beginning spidering and scanning at the specified target URL, rather than the host root URL. This change has an added benefit: scans can take less time, if the specified path does not contain links to the entire site. This enables easier scanning of smaller sections of an application, rather than crawling the entire app during every scan.
|
||||
|
|
@ -864,7 +864,7 @@ In GitLab 14.0, DAST has removed the current method of resetting the scan to the
|
|||
### Default branch name for new repositories now `main`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Every Git repository has an initial branch, which is named `master` by default. It's the first branch to be created automatically when you create a new repository. Future [Git versions](https://lore.kernel.org/git/pull.656.v4.git.1593009996.gitgitgadget@gmail.com/) will change the default branch name in Git from `master` to `main`. In coordination with the Git project and the broader community, [GitLab has changed the default branch name](https://gitlab.com/gitlab-org/gitlab/-/issues/223789) for new projects on both our SaaS (GitLab.com) and self-managed offerings starting with GitLab 14.0. This will not affect existing projects.
|
||||
|
|
@ -876,7 +876,7 @@ For more information, check out our [blog post](https://about.gitlab.com/blog/20
|
|||
### Dependency Scanning
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As mentioned in [13.9](https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#deprecations-for-dependency-scanning) and [this blog post](https://about.gitlab.com/blog/2021/02/08/composition-analysis-14-deprecations-and-removals/) several removals for Dependency Scanning take effect.
|
||||
|
|
@ -888,7 +888,7 @@ Previously, to prevent the Gemnasium analyzers to fetch the advisory database at
|
|||
### Deprecated GraphQL fields
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In accordance with our [GraphQL deprecation and removal process](https://docs.gitlab.com/ee/api/graphql/#deprecation-process), the following fields that were deprecated prior to 13.7 are [fully removed in 14.0](https://gitlab.com/gitlab-org/gitlab/-/issues/267966):
|
||||
|
|
@ -903,7 +903,7 @@ In accordance with our [GraphQL deprecation and removal process](https://docs.gi
|
|||
### DevOps Adoption API Segments
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The first release of the DevOps Adoption report had a concept of **Segments**. Segments were [quickly removed from the report](https://gitlab.com/groups/gitlab-org/-/epics/5251) because they introduced an additional layer of complexity on top of **Groups** and **Projects**. Subsequent iterations of the DevOps Adoption report focus on comparing adoption across groups rather than segments. GitLab 14.0 removes all references to **Segments** [from the GraphQL API](https://gitlab.com/gitlab-org/gitlab/-/issues/324414) and replaces them with **Enabled groups**.
|
||||
|
|
@ -911,7 +911,7 @@ The first release of the DevOps Adoption report had a concept of **Segments**. S
|
|||
### Disk source configuration for GitLab Pages
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab Pages [API-based configuration](https://docs.gitlab.com/ee/administration/pages/#gitlab-api-based-configuration) has been available since GitLab 13.0. It replaces the unsupported `disk` source configuration removed in GitLab 14.0, which can no longer be chosen. You should stop using `disk` source configuration, and move to `gitlab` for an API-based configuration. To migrate away from the 'disk' source configuration, set `gitlab_pages['domain_config_source'] = "gitlab"` in your `/etc/gitlab/gitlab.rb` file. We recommend you migrate before updating to GitLab 14.0, to identify and troubleshoot any potential problems before upgrading.
|
||||
|
|
@ -919,7 +919,7 @@ GitLab Pages [API-based configuration](https://docs.gitlab.com/ee/administration
|
|||
### Experimental prefix in Sidekiq queue selector options
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab supports a [queue selector](https://docs.gitlab.com/ee/administration/operations/extra_sidekiq_processes.html#queue-selector) to run only a subset of background jobs for a given process. When it was introduced, this option had an 'experimental' prefix (`experimental_queue_selector` in Omnibus, `experimentalQueueSelector` in Helm charts).
|
||||
|
|
@ -929,7 +929,7 @@ As announced in the [13.6 release post](https://about.gitlab.com/releases/2020/1
|
|||
### External Pipeline Validation Service Code Changes
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
For self-managed instances using the experimental [external pipeline validation service](https://docs.gitlab.com/ee/administration/external_pipeline_validation.html), the range of error codes GitLab accepts will be reduced. Currently, pipelines are invalidated when the validation service returns a response code from `400` to `499`. In GitLab 14.0 and later, pipelines will be invalidated for the `406: Not Accepted` response code only.
|
||||
|
|
@ -937,7 +937,7 @@ For self-managed instances using the experimental [external pipeline validation
|
|||
### Geo Foreign Data Wrapper settings
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As [announced in GitLab 13.3](https://about.gitlab.com/releases/2020/08/22/gitlab-13-3-released/#geo-foreign-data-wrapper-settings-deprecated), the following configuration settings in `/etc/gitlab/gitlab.rb` have been removed in 14.0:
|
||||
|
|
@ -950,7 +950,7 @@ As [announced in GitLab 13.3](https://about.gitlab.com/releases/2020/08/22/gitla
|
|||
### GitLab OAuth implicit grant
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab is deprecating the [OAuth 2 implicit grant flow](https://docs.gitlab.com/ee/api/oauth2.html#implicit-grant-flow) as it has been removed for [OAuth 2.1](https://oauth.net/2.1/).
|
||||
|
|
@ -960,7 +960,7 @@ Migrate your existing applications to other supported [OAuth2 flows](https://doc
|
|||
### GitLab Runner helper image in GitLab.com Container Registry
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In 14.0, we are now pulling the GitLab Runner [helper image](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#helper-image) from the GitLab Container Registry instead of Docker Hub. Refer to [issue #27218](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27218) for details.
|
||||
|
|
@ -968,7 +968,7 @@ In 14.0, we are now pulling the GitLab Runner [helper image](https://docs.gitlab
|
|||
### GitLab Runner installation to ignore the `skel` directory
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab Runner 14.0, the installation process will ignore the `skel` directory by default when creating the user home directory. Refer to [issue #4845](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4845) for details.
|
||||
|
|
@ -976,7 +976,7 @@ In GitLab Runner 14.0, the installation process will ignore the `skel` directory
|
|||
### Gitaly Cluster SQL primary elector
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Now that Praefect supports a [primary election strategy](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#repository-specific-primary-nodes) for each repository, we have removed the `sql` election strategy.
|
||||
|
|
@ -987,7 +987,7 @@ If you had configured the `sql` election strategy, you must follow the [migratio
|
|||
### Global `SAST_ANALYZER_IMAGE_TAG` in SAST CI template
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
With the maturity of GitLab Secure scanning tools, we've needed to add more granularity to our release process. Previously, GitLab shared a major version number for [all analyzers and tools](https://docs.gitlab.com/ee/user/application_security/sast/#supported-languages-and-frameworks). This requires all tools to share a major version, and prevents the use of [semantic version numbering](https://semver.org/). In GitLab 14.0, SAST removes the `SAST_ANALYZER_IMAGE_TAG` global variable in our [managed `SAST.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/SAST.gitlab-ci.yml) CI template, in favor of the analyzer job variable setting the `major.minor` tag in the SAST vendored template.
|
||||
|
|
@ -999,7 +999,7 @@ This deprecation and removal changes our [previously announced plan](https://abo
|
|||
### Hardcoded `master` in CI/CD templates
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Our CI/CD templates have been updated to no longer use hard-coded references to a `master` branch. In 14.0, they all use a variable that points to your project's configured default branch instead. If your CI/CD pipeline relies on our built-in templates, verify that this change works with your current configuration. For example, if you have a `master` branch and a different default branch, the updates to the templates may cause changes to your pipeline behavior. For more information, [read the issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324131).
|
||||
|
|
@ -1007,7 +1007,7 @@ Our CI/CD templates have been updated to no longer use hard-coded references to
|
|||
### Helm v2 support
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Helm v2 was [officially deprecated](https://helm.sh/blog/helm-v2-deprecation-timeline/) in November of 2020, with the `stable` repository being [de-listed from the Helm Hub](https://about.gitlab.com/blog/2020/11/09/ensure-auto-devops-work-after-helm-stable-repo/) shortly thereafter. With the release of GitLab 14.0, which will include the 5.0 release of the [GitLab Helm chart](https://docs.gitlab.com/charts/), Helm v2 will no longer be supported.
|
||||
|
|
@ -1017,7 +1017,7 @@ Users of the chart should [upgrade to Helm v3](https://helm.sh/docs/topics/v2_v3
|
|||
### Legacy DAST domain validation
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The legacy method of DAST Domain Validation for CI/CD scans was deprecated in GitLab 13.8, and is removed in GitLab 14.0. This method of domain validation only disallows scans if the `DAST_FULL_SCAN_DOMAIN_VALIDATION_REQUIRED` environment variable is set to `true` in the `gitlab-ci.yml` file, and a `Gitlab-DAST-Permission` header on the site is not set to `allow`. This two-step method required users to opt in to using the variable before they could opt out from using the header.
|
||||
|
|
@ -1027,7 +1027,7 @@ For more information, see the [removal issue](https://gitlab.com/gitlab-org/gitl
|
|||
### Legacy feature flags
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Legacy feature flags became read-only in GitLab 13.4. GitLab 14.0 removes support for legacy feature flags, so you must migrate them to the [new version](https://docs.gitlab.com/ee/operations/feature_flags.html). You can do this by first taking a note (screenshot) of the legacy flag, then deleting the flag through the API or UI (you don't need to alter the code), and finally create a new Feature Flag with the same name as the legacy flag you deleted. Also, make sure the strategies and environments match the deleted flag. We created a [video tutorial](https://www.youtube.com/watch?v=CAJY2IGep7Y) to help with this migration.
|
||||
|
|
@ -1035,7 +1035,7 @@ Legacy feature flags became read-only in GitLab 13.4. GitLab 14.0 removes suppor
|
|||
### Legacy fields from DAST report
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As a part of the migration to a common report format for all of the Secure scanners in GitLab, DAST is making changes to the DAST JSON report. Certain legacy fields were deprecated in 13.8 and have been completely removed in 14.0. These fields are `@generated`, `@version`, `site`, and `spider`. This should not affect any normal DAST operation, but does affect users who consume the JSON report in an automated way and use these fields. Anyone affected by these changes, and needs these fields for business reasons, is encouraged to open a new GitLab issue and explain the need.
|
||||
|
|
@ -1045,7 +1045,7 @@ For more information, see [the removal issue](https://gitlab.com/gitlab-org/gitl
|
|||
### Legacy storage
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As [announced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/#planned-removal-of-legacy-storage-in-14.0), [legacy storage](https://docs.gitlab.com/ee/administration/repository_storage_types.html#legacy-storage) has been removed in GitLab 14.0.
|
||||
|
|
@ -1053,7 +1053,7 @@ As [announced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitla
|
|||
### License Compliance
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In 13.0, we deprecated the License-Management CI template and renamed it License-Scanning. We have been providing backward compatibility by warning users of the old template to switch. Now in 14.0, we are completely removing the License-Management CI template. Read about it in [issue #216261](https://gitlab.com/gitlab-org/gitlab/-/issues/216261) or [this blog post](https://about.gitlab.com/blog/2021/02/08/composition-analysis-14-deprecations-and-removals/).
|
||||
|
|
@ -1061,7 +1061,7 @@ In 13.0, we deprecated the License-Management CI template and renamed it License
|
|||
### Limit projects returned in `GET /groups/:id/`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
To improve performance, we are limiting the number of projects returned from the `GET /groups/:id/` API call to 100. A complete list of projects can still be retrieved with the `GET /groups/:id/projects` API call.
|
||||
|
|
@ -1069,7 +1069,7 @@ To improve performance, we are limiting the number of projects returned from the
|
|||
### Make `pwsh` the default shell for newly-registered Windows Runners
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab Runner 13.2, PowerShell Core support was added to the Shell executor. In 14.0, PowerShell Core, `pwsh` is now the default shell for newly-registered Windows runners. Windows `CMD` will still be available as a shell option for Windows runners. Refer to [issue #26419](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26419) for details.
|
||||
|
|
@ -1077,7 +1077,7 @@ In GitLab Runner 13.2, PowerShell Core support was added to the Shell executor.
|
|||
### Migrate from `SAST_DEFAULT_ANALYZERS` to `SAST_EXCLUDED_ANALYZERS`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Until GitLab 13.9, if you wanted to avoid running one particular GitLab SAST analyzer, you needed to remove it from the [long string of analyzers in the `SAST.gitlab-ci.yml` file](https://gitlab.com/gitlab-org/gitlab/-/blob/390afc431e7ce1ac253b35beb39f19e49c746bff/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml#L12) and use that to set the [`SAST_DEFAULT_ANALYZERS`](https://docs.gitlab.com/ee/user/application_security/sast/#docker-images) variable in your project's CI file. If you did this, it would exclude you from future new analyzers because this string hard codes the list of analyzers to execute. We avoid this problem by inverting this variable's logic to exclude, rather than choose default analyzers.
|
||||
|
|
@ -1086,7 +1086,7 @@ Beginning with 13.9, [we migrated](https://gitlab.com/gitlab-org/gitlab/-/blob/1
|
|||
### Off peak time mode configuration for Docker Machine autoscaling
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab Runner 13.0, [issue #5069](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/5069), we introduced new timing options for the GitLab Docker Machine executor. In GitLab Runner 14.0, we have removed the old configuration option, [off peak time mode](https://docs.gitlab.com/runner/configuration/autoscale.html#off-peak-time-mode-configuration-deprecated).
|
||||
|
|
@ -1094,7 +1094,7 @@ In GitLab Runner 13.0, [issue #5069](https://gitlab.com/gitlab-org/gitlab-runner
|
|||
### OpenSUSE Leap 15.1
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Support for [OpenSUSE Leap 15.1 is being deprecated](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/5135). Support for 15.1 will be dropped in 14.0. We are now providing support for openSUSE Leap 15.2 packages.
|
||||
|
|
@ -1102,7 +1102,7 @@ Support for [OpenSUSE Leap 15.1 is being deprecated](https://gitlab.com/gitlab-o
|
|||
### PostgreSQL 11 support
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab 14.0 requires PostgreSQL 12 or later. It offers [significant improvements](https://www.postgresql.org/about/news/postgresql-12-released-1976/) to indexing, partitioning, and general performance benefits.
|
||||
|
|
@ -1112,7 +1112,7 @@ Starting in GitLab 13.7, all new installations default to PostgreSQL version 12.
|
|||
### Redundant timestamp field from DORA metrics API payload
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The [deployment frequency project-level API](https://docs.gitlab.com/ee/api/dora4_project_analytics.html#list-project-deployment-frequencies) endpoint has been deprecated in favor of the [DORA 4 API](https://docs.gitlab.com/ee/api/dora/metrics.html), which consolidates all the metrics under one API with the specific metric as a required field. As a result, the timestamp field, which doesn't allow adding future extensions and causes performance issues, will be removed. With the old API, an example response would be `{ "2021-03-01": 3, "date": "2021-03-01", "value": 3 }`. The first key/value (`"2021-03-01": 3`) will be removed and replaced by the last two (`"date": "2021-03-01", "value": 3`).
|
||||
|
|
@ -1120,7 +1120,7 @@ The [deployment frequency project-level API](https://docs.gitlab.com/ee/api/dora
|
|||
### Release description in the Tags API
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab 14.0 removes support for the release description in the Tags API. You can no longer add a release description when [creating a new tag](https://docs.gitlab.com/ee/api/tags.html#create-a-new-tag). You also can no longer [create](https://docs.gitlab.com/ee/api/tags.html#create-a-new-release) or [update](https://docs.gitlab.com/ee/api/tags.html#update-a-release) a release through the Tags API. Please migrate to use the [Releases API](https://docs.gitlab.com/ee/api/releases/#create-a-release) instead.
|
||||
|
|
@ -1128,7 +1128,7 @@ GitLab 14.0 removes support for the release description in the Tags API. You can
|
|||
### Ruby version changed in `Ruby.gitlab-ci.yml`
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
By default, the `Ruby.gitlab-ci.yml` file has included Ruby 2.5.
|
||||
|
|
@ -1140,7 +1140,7 @@ Relevant Issue: [Updates Ruby version 2.5 to 3.0](https://gitlab.com/gitlab-org/
|
|||
### SAST analyzer `SAST_GOSEC_CONFIG` variable
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
With the release of [SAST Custom Rulesets](https://docs.gitlab.com/ee/user/application_security/sast/#customize-rulesets) in GitLab 13.5 we allow greater flexibility in configuration options for our Go analyzer (GoSec). As a result we no longer plan to support our less flexible [`SAST_GOSEC_CONFIG`](https://docs.gitlab.com/ee/user/application_security/sast/#analyzer-settings) analyzer setting. This variable was deprecated in GitLab 13.10.
|
||||
|
|
@ -1149,7 +1149,7 @@ GitLab 14.0 removes the old `SAST_GOSEC_CONFIG variable`. If you use or override
|
|||
### Service Templates
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Service Templates are [removed in GitLab 14.0](https://gitlab.com/groups/gitlab-org/-/epics/5672). They were used to apply identical settings to a large number of projects, but they only did so at the time of project creation.
|
||||
|
|
@ -1159,7 +1159,7 @@ While they solved part of the problem, _updating_ those values later proved to b
|
|||
### Success and failure for finished build metric conversion
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab Runner 13.5, we introduced `failed` and `success` states for a job. To support Prometheus rules, we chose to convert `success/failure` to `finished` for the metric. In 14.0, the conversion has now been removed. Refer to [issue #26900](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26900) for details.
|
||||
|
|
@ -1167,7 +1167,7 @@ In GitLab Runner 13.5, we introduced `failed` and `success` states for a job. To
|
|||
### Terraform template version
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
As we continuously [develop GitLab's Terraform integrations](https://gitlab.com/gitlab-org/gitlab/-/issues/325312), to minimize customer disruption, we maintain two GitLab CI/CD templates for Terraform:
|
||||
|
|
@ -1186,7 +1186,7 @@ To check the new changes, see the [new "major version" template](https://gitlab.
|
|||
### Ubuntu 16.04 support
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Ubuntu 16.04 [reached end-of-life in April 2021](https://ubuntu.com/about/release-cycle), and no longer receives maintenance updates. We strongly recommend users to upgrade to a newer release, such as 20.04.
|
||||
|
|
@ -1196,7 +1196,7 @@ GitLab 13.12 will be the last release with Ubuntu 16.04 support.
|
|||
### Ubuntu 19.10 (Eoan Ermine) package
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitLab Runner 14.0, Ubuntu 19.10 (Eoan Ermine) is no longer available from our package distribution. Refer to [issue #26036](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26036) for details.
|
||||
|
|
@ -1204,7 +1204,7 @@ Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitL
|
|||
### Unicorn in GitLab self-managed
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
[Support for Unicorn](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6078) has been removed in GitLab 14.0 in favor of Puma. [Puma has a multi-threaded architecture](https://docs.gitlab.com/ee/administration/operations/puma.html) which uses less memory than a multi-process application server like Unicorn. On GitLab.com, we saw a 40% reduction in memory consumption by using Puma.
|
||||
|
|
@ -1212,7 +1212,7 @@ Review the details carefully before upgrading.
|
|||
### WIP merge requests renamed 'draft merge requests'
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The WIP (work in progress) status for merge requests signaled to reviewers that the merge request in question wasn't ready to merge. We've renamed the WIP feature to **Draft**, a more inclusive and self-explanatory term. **Draft** clearly communicates the merge request in question isn't ready for review, and makes no assumptions about the progress being made toward it. **Draft** also reduces the cognitive load for new users, non-English speakers, and anyone unfamiliar with the WIP acronym.
|
||||
|
|
@ -1220,7 +1220,7 @@ The WIP (work in progress) status for merge requests signaled to reviewers that
|
|||
### Web Application Firewall (WAF)
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The Web Application Firewall (WAF) was deprecated in GitLab 13.6 and is removed from GitLab 14.0. The WAF had limitations inherent in the architectural design that made it difficult to meet the requirements traditionally expected of a WAF. By removing the WAF, GitLab is able to focus on improving other areas in the product where more value can be provided to users. Users who currently rely on the WAF can continue to use the free and open source [ModSecurity](https://github.com/SpiderLabs/ModSecurity) project, which is independent from GitLab. Additional details are available in the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/271276).
|
||||
|
|
@ -1228,7 +1228,7 @@ The Web Application Firewall (WAF) was deprecated in GitLab 13.6 and is removed
|
|||
### Windows Server 1903 image support
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In 14.0, we have removed Windows Server 1903. Microsoft ended support for this version on 2020-08-12. Refer to [issue #27551](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27551) for details.
|
||||
|
|
@ -1236,7 +1236,7 @@ In 14.0, we have removed Windows Server 1903. Microsoft ended support for this v
|
|||
### Windows Server 1909 image support
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In 14.0, we have removed Windows Server 1909. Microsoft ended support for this version on 2021-05-11. Refer to [issue #27899](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27899) for details.
|
||||
|
|
@ -1244,7 +1244,7 @@ In 14.0, we have removed Windows Server 1909. Microsoft ended support for this v
|
|||
### `/usr/lib/gitlab-runner` symlink from package
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In GitLab Runner 13.3, a symlink was added from `/user/lib/gitlab-runner/gitlab-runner` to `/usr/bin/gitlab-runner`. In 14.0, the symlink has been removed and the runner is now installed in `/usr/bin/gitlab-runner`. Refer to [issue #26651](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26651) for details.
|
||||
|
|
@ -1252,7 +1252,7 @@ In GitLab Runner 13.3, a symlink was added from `/user/lib/gitlab-runner/gitlab-
|
|||
### `?w=1` URL parameter to ignore whitespace changes
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
To create a consistent experience for users based on their preferences, support for toggling whitespace changes via URL parameter has been removed in GitLab 14.0.
|
||||
|
|
@ -1260,7 +1260,7 @@ To create a consistent experience for users based on their preferences, support
|
|||
### `CI_PROJECT_CONFIG_PATH` variable
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
The `CI_PROJECT_CONFIG_PATH` [predefined project variable](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html)
|
||||
|
|
@ -1272,7 +1272,7 @@ please update them to use `CI_CONFIG_PATH` instead.
|
|||
### `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In 14.0, we have deactivated the `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag. Refer to issue [#26679](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26679) for details.
|
||||
|
|
@ -1280,7 +1280,7 @@ In 14.0, we have deactivated the `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag
|
|||
### `FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL` feature flag
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
In [GitLab Runner 13.1](https://docs.gitlab.com/runner/executors/shell.html#gitlab-131-and-later), [issue #3376](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3376), we introduced `sigterm` and then `sigkill` to a process in the Shell executor. We also introduced a new feature flag, `FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL`, so you can use the previous process termination sequence. In GitLab Runner 14.0, [issue #6413](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6413), the feature flag has been removed.
|
||||
|
|
@ -1288,7 +1288,7 @@ In [GitLab Runner 13.1](https://docs.gitlab.com/runner/executors/shell.html#gitl
|
|||
### `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab Runner 14.0 removes the `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag. Refer to [issue #27175](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27175) for details.
|
||||
|
|
@ -1296,7 +1296,7 @@ GitLab Runner 14.0 removes the `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature fla
|
|||
### `secret_detection_default_branch` job
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
To ensure Secret Detection was scanning both default branches and feature branches, we introduced two separate secret detection CI jobs (`secret_detection_default_branch` and `secret_detection`) in our managed [`Secret-Detection.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/Secret-Detection.gitlab-ci.yml) template. These two CI jobs created confusion and complexity in the CI rules logic. This deprecation moves the `rule` logic into the `script` section, which then determines how the `secret_detection` job is run (historic, on a branch, commits, etc).
|
||||
|
|
@ -1305,7 +1305,7 @@ If you override or maintain custom versions of `SAST.gitlab-ci.yml` or `Secret-D
|
|||
### `trace` parameter in `jobs` API
|
||||
|
||||
WARNING:
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
|
||||
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
|
||||
Review the details carefully before upgrading.
|
||||
|
||||
GitLab Runner was updated in GitLab 13.4 to internally stop passing the `trace` parameter to the `/api/jobs/:id` endpoint. GitLab 14.0 deprecates the `trace` parameter entirely for all other requests of this endpoint. Make sure your [GitLab Runner version matches your GitLab version](https://docs.gitlab.com/runner/#gitlab-runner-versions) to ensure consistent behavior.
|
||||
|
|
|
|||
|
|
@ -95,6 +95,7 @@ The following table lists project permissions available for each role:
|
|||
| [Issues](project/issues/index.md):<br>View [Design Management](project/issues/design_management.md) pages | ✓ | ✓ | ✓ | ✓ | ✓ |
|
||||
| [Issues](project/issues/index.md):<br>View [related issues](project/issues/related_issues.md) | ✓ | ✓ | ✓ | ✓ | ✓ |
|
||||
| [Issues](project/issues/index.md):<br>Set [weight](project/issues/issue_weight.md) | ✓ (*15*) | ✓ | ✓ | ✓ | ✓ |
|
||||
| [Issues]](project/issues/index.md):<br>Set [parent epic](group/epics/manage_epics.md#add-an-existing-issue-to-an-epic) | | ✓ | ✓ | ✓ | ✓ |
|
||||
| [Issues](project/issues/index.md):<br>View [confidential issues](project/issues/confidential_issues.md) | (*2*) | ✓ | ✓ | ✓ | ✓ |
|
||||
| [Issues](project/issues/index.md):<br>Close / reopen (*19*) | | ✓ | ✓ | ✓ | ✓ |
|
||||
| [Issues](project/issues/index.md):<br>Lock threads | | ✓ | ✓ | ✓ | ✓ |
|
||||
|
|
|
|||
|
|
@ -16,15 +16,18 @@ Use the <kbd>.</kbd> [keyboard shortcut](../../shortcuts.md) to open the Web IDE
|
|||
You can also open the Web IDE when viewing a file, from the repository file list,
|
||||
and from merge requests:
|
||||
|
||||
- *When viewing a file, or the repository file list* -
|
||||
### When viewing a file or the repository file list
|
||||
|
||||
1. In the upper right corner of the page, select **Open in Web IDE** if it is visible.
|
||||
1. If **Open in Web IDE** is not visible:
|
||||
1. Select the (**{chevron-lg-down}**) next to **Edit** or **Gitpod**, depending on your configuration.
|
||||
1. Select **Open in Web IDE** from the list to display it as the editing option.
|
||||
1. Select **Open in Web IDE** to open the editor.
|
||||
- *When viewing a merge request* -
|
||||
|
||||
### When viewing a merge request
|
||||
|
||||
1. Go to your merge request.
|
||||
1. In the upper right corner, select **Code**, then select **Open in Gitpod**.
|
||||
1. In the upper right corner, select **Code > Open in Web IDE**.
|
||||
|
||||
## File finder
|
||||
|
||||
|
|
@ -86,7 +89,7 @@ You can pick a theme from your [profile preferences](../../profile/preferences.m
|
|||
|
||||
## Highlight lines
|
||||
|
||||
WebIDE is built with the [Web Editor](../repository/web_editor.md). This enables WebIDE to share the
|
||||
The Web IDE is built with the [Web Editor](../repository/web_editor.md). This enables the Web IDE to share the
|
||||
same core features for highlighting and linking to particular lines in the edited files
|
||||
[described for the Web Editor](../repository/web_editor.md#highlight-lines).
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,80 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
module Gitlab
|
||||
module Database
|
||||
class LockWritesManager
|
||||
TRIGGER_FUNCTION_NAME = 'gitlab_schema_prevent_write'
|
||||
|
||||
def initialize(table_name:, connection:, database_name:, logger: nil)
|
||||
@table_name = table_name
|
||||
@connection = connection
|
||||
@database_name = database_name
|
||||
@logger = logger
|
||||
end
|
||||
|
||||
def lock_writes
|
||||
logger&.info "Database: '#{database_name}', Table: '#{table_name}': Lock Writes".color(:yellow)
|
||||
sql = <<-SQL
|
||||
DROP TRIGGER IF EXISTS #{write_trigger_name(table_name)} ON #{table_name};
|
||||
CREATE TRIGGER #{write_trigger_name(table_name)}
|
||||
BEFORE INSERT OR UPDATE OR DELETE OR TRUNCATE
|
||||
ON #{table_name}
|
||||
FOR EACH STATEMENT EXECUTE FUNCTION #{TRIGGER_FUNCTION_NAME}();
|
||||
SQL
|
||||
|
||||
with_retries(connection) do
|
||||
connection.execute(sql)
|
||||
end
|
||||
end
|
||||
|
||||
def unlock_writes
|
||||
logger&.info "Database: '#{database_name}', Table: '#{table_name}': Allow Writes".color(:green)
|
||||
sql = <<-SQL
|
||||
DROP TRIGGER IF EXISTS #{write_trigger_name(table_name)} ON #{table_name}
|
||||
SQL
|
||||
|
||||
with_retries(connection) do
|
||||
connection.execute(sql)
|
||||
end
|
||||
end
|
||||
|
||||
private
|
||||
|
||||
attr_reader :table_name, :connection, :database_name, :logger
|
||||
|
||||
def with_retries(connection, &block)
|
||||
with_statement_timeout_retries do
|
||||
with_lock_retries(connection) do
|
||||
yield
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
def with_statement_timeout_retries(times = 5)
|
||||
current_iteration = 1
|
||||
begin
|
||||
yield
|
||||
rescue ActiveRecord::QueryCanceled => err # rubocop:disable Database/RescueQueryCanceled
|
||||
if current_iteration <= times
|
||||
current_iteration += 1
|
||||
retry
|
||||
else
|
||||
raise err
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
def with_lock_retries(connection, &block)
|
||||
Gitlab::Database::WithLockRetries.new(
|
||||
klass: "gitlab:db:lock_writes",
|
||||
logger: logger || Gitlab::AppLogger,
|
||||
connection: connection
|
||||
).run(&block)
|
||||
end
|
||||
|
||||
def write_trigger_name(table_name)
|
||||
"gitlab_schema_write_trigger_for_#{table_name}"
|
||||
end
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
@ -505,14 +505,14 @@ module Gitlab
|
|||
# case another unique integer column can be used. Example: :user_id
|
||||
#
|
||||
# rubocop: disable Metrics/AbcSize
|
||||
def update_column_in_batches(table, column, value, batch_size: nil, batch_column_name: :id)
|
||||
def update_column_in_batches(table_name, column, value, batch_size: nil, batch_column_name: :id, disable_lock_writes: false)
|
||||
if transaction_open?
|
||||
raise 'update_column_in_batches can not be run inside a transaction, ' \
|
||||
'you can disable transactions by calling disable_ddl_transaction! ' \
|
||||
'in the body of your migration class'
|
||||
end
|
||||
|
||||
table = Arel::Table.new(table)
|
||||
table = Arel::Table.new(table_name)
|
||||
|
||||
count_arel = table.project(Arel.star.count.as('count'))
|
||||
count_arel = yield table, count_arel if block_given?
|
||||
|
|
@ -559,7 +559,10 @@ module Gitlab
|
|||
|
||||
update_arel = yield table, update_arel if block_given?
|
||||
|
||||
execute(update_arel.to_sql)
|
||||
transaction do
|
||||
execute("SELECT set_config('lock_writes.#{table_name}', 'false', true)") if disable_lock_writes
|
||||
execute(update_arel.to_sql)
|
||||
end
|
||||
|
||||
# There are no more rows left to update.
|
||||
break unless stop_row
|
||||
|
|
@ -1667,7 +1670,7 @@ into similar problems in the future (e.g. when new tables are created).
|
|||
|
||||
Gitlab::Database::QueryAnalyzers::RestrictAllowedSchemas.with_suppressed do
|
||||
Gitlab::Database::QueryAnalyzers::GitlabSchemasValidateConnection.with_suppressed do
|
||||
update_column_in_batches(table, new, old_value, batch_column_name: batch_column_name)
|
||||
update_column_in_batches(table, new, old_value, batch_column_name: batch_column_name, disable_lock_writes: true)
|
||||
end
|
||||
end
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,20 @@
|
|||
module Gitlab
|
||||
module FormBuilders
|
||||
class GitlabUiFormBuilder < ActionView::Helpers::FormBuilder
|
||||
def submit(value = nil, options = {})
|
||||
if options[:pajamas_button]
|
||||
@template.render Pajamas::ButtonComponent.new(
|
||||
variant: :confirm,
|
||||
type: :submit,
|
||||
button_options: options.except!(:pajamas_button)
|
||||
) do
|
||||
value
|
||||
end
|
||||
else
|
||||
super
|
||||
end
|
||||
end
|
||||
|
||||
def gitlab_ui_checkbox_component(
|
||||
method,
|
||||
label = nil,
|
||||
|
|
|
|||
|
|
@ -2,22 +2,25 @@
|
|||
|
||||
namespace :gitlab do
|
||||
namespace :db do
|
||||
TRIGGER_FUNCTION_NAME = 'gitlab_schema_prevent_write'
|
||||
|
||||
desc "GitLab | DB | Install prevent write triggers on all databases"
|
||||
task lock_writes: [:environment, 'gitlab:db:validate_config'] do
|
||||
Gitlab::Database::EachDatabase.each_database_connection(include_shared: false) do |connection, database_name|
|
||||
create_write_trigger_function(connection)
|
||||
|
||||
schemas_for_connection = Gitlab::Database.gitlab_schemas_for_connection(connection)
|
||||
Gitlab::Database::GitlabSchema.tables_to_schema.each do |table_name, schema_name|
|
||||
# TODO: https://gitlab.com/gitlab-org/gitlab/-/issues/366834
|
||||
next if schema_name == :gitlab_geo
|
||||
|
||||
lock_writes_manager = Gitlab::Database::LockWritesManager.new(
|
||||
table_name: table_name,
|
||||
connection: connection,
|
||||
database_name: database_name,
|
||||
logger: Logger.new($stdout)
|
||||
)
|
||||
|
||||
if schemas_for_connection.include?(schema_name.to_sym)
|
||||
drop_write_trigger(database_name, connection, table_name)
|
||||
lock_writes_manager.unlock_writes
|
||||
else
|
||||
create_write_trigger(database_name, connection, table_name)
|
||||
lock_writes_manager.lock_writes
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
@ -30,96 +33,16 @@ namespace :gitlab do
|
|||
# TODO: https://gitlab.com/gitlab-org/gitlab/-/issues/366834
|
||||
next if schema_name == :gitlab_geo
|
||||
|
||||
drop_write_trigger(database_name, connection, table_name)
|
||||
end
|
||||
drop_write_trigger_function(connection)
|
||||
end
|
||||
end
|
||||
lock_writes_manager = Gitlab::Database::LockWritesManager.new(
|
||||
table_name: table_name,
|
||||
connection: connection,
|
||||
database_name: database_name,
|
||||
logger: Logger.new($stdout)
|
||||
)
|
||||
|
||||
def create_write_trigger_function(connection)
|
||||
sql = <<-SQL
|
||||
CREATE OR REPLACE FUNCTION #{TRIGGER_FUNCTION_NAME}()
|
||||
RETURNS TRIGGER AS
|
||||
$$
|
||||
BEGIN
|
||||
RAISE EXCEPTION 'Table: "%" is write protected within this Gitlab database.', TG_TABLE_NAME
|
||||
USING ERRCODE = 'modifying_sql_data_not_permitted',
|
||||
HINT = 'Make sure you are using the right database connection';
|
||||
END
|
||||
$$ LANGUAGE PLPGSQL
|
||||
SQL
|
||||
|
||||
connection.execute(sql)
|
||||
end
|
||||
|
||||
def drop_write_trigger_function(connection)
|
||||
sql = <<-SQL
|
||||
DROP FUNCTION IF EXISTS #{TRIGGER_FUNCTION_NAME}()
|
||||
SQL
|
||||
|
||||
connection.execute(sql)
|
||||
end
|
||||
|
||||
def create_write_trigger(database_name, connection, table_name)
|
||||
puts "#{database_name}: '#{table_name}'... Lock Writes".color(:yellow)
|
||||
sql = <<-SQL
|
||||
DROP TRIGGER IF EXISTS #{write_trigger_name(table_name)} ON #{table_name};
|
||||
CREATE TRIGGER #{write_trigger_name(table_name)}
|
||||
BEFORE INSERT OR UPDATE OR DELETE OR TRUNCATE
|
||||
ON #{table_name}
|
||||
FOR EACH STATEMENT EXECUTE FUNCTION #{TRIGGER_FUNCTION_NAME}();
|
||||
SQL
|
||||
|
||||
with_retries(connection) do
|
||||
connection.execute(sql)
|
||||
end
|
||||
end
|
||||
|
||||
def drop_write_trigger(database_name, connection, table_name)
|
||||
puts "#{database_name}: '#{table_name}'... Allow Writes".color(:green)
|
||||
sql = <<-SQL
|
||||
DROP TRIGGER IF EXISTS #{write_trigger_name(table_name)} ON #{table_name}
|
||||
SQL
|
||||
|
||||
with_retries(connection) do
|
||||
connection.execute(sql)
|
||||
end
|
||||
end
|
||||
|
||||
def with_retries(connection, &block)
|
||||
with_statement_timeout_retries do
|
||||
with_lock_retries(connection) do
|
||||
yield
|
||||
lock_writes_manager.unlock_writes
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
def with_statement_timeout_retries(times = 5)
|
||||
current_iteration = 1
|
||||
begin
|
||||
yield
|
||||
rescue ActiveRecord::QueryCanceled => err
|
||||
puts "Retrying after #{err.message}"
|
||||
|
||||
if current_iteration <= times
|
||||
current_iteration += 1
|
||||
retry
|
||||
else
|
||||
raise err
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
def with_lock_retries(connection, &block)
|
||||
Gitlab::Database::WithLockRetries.new(
|
||||
klass: "gitlab:db:lock_writes",
|
||||
logger: Gitlab::AppLogger,
|
||||
connection: connection
|
||||
).run(&block)
|
||||
end
|
||||
|
||||
def write_trigger_name(table_name)
|
||||
"gitlab_schema_write_trigger_for_#{table_name}"
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
|
|||
|
|
@ -7306,9 +7306,6 @@ msgstr ""
|
|||
msgid "Can't find variable: ZiteReader"
|
||||
msgstr ""
|
||||
|
||||
msgid "Can't load mermaid module: %{err}"
|
||||
msgstr ""
|
||||
|
||||
msgid "Can't scan the code?"
|
||||
msgstr ""
|
||||
|
||||
|
|
@ -14553,9 +14550,6 @@ msgstr ""
|
|||
msgid "Enabled OAuth authentication sources"
|
||||
msgstr ""
|
||||
|
||||
msgid "Encountered an error while rendering: %{err}"
|
||||
msgstr ""
|
||||
|
||||
msgid "End Time"
|
||||
msgstr ""
|
||||
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ module QA
|
|||
element :namespaces_list
|
||||
element :namespaces_list_groups
|
||||
element :namespaces_list_item
|
||||
element :namespaces_list_search
|
||||
end
|
||||
end
|
||||
|
||||
|
|
@ -20,6 +21,10 @@ module QA
|
|||
click_element :namespaces_list
|
||||
|
||||
within_element(:namespaces_list) do
|
||||
find_element(:namespaces_list_search).fill_in(with: item)
|
||||
|
||||
wait_for_requests
|
||||
|
||||
find_element(:namespaces_list_item, text: item).click
|
||||
end
|
||||
end
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
module QA
|
||||
RSpec.describe 'Manage' do
|
||||
describe 'Project transfer between groups', :reliable do
|
||||
describe 'Project transfer between groups' do
|
||||
let(:source_group) do
|
||||
Resource::Group.fabricate_via_api! do |group|
|
||||
group.path = "source-group-#{SecureRandom.hex(8)}"
|
||||
|
|
|
|||
|
|
@ -0,0 +1,46 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
require 'spec_helper'
|
||||
|
||||
RSpec.describe 'Jobs (JavaScript fixtures)' do
|
||||
include ApiHelpers
|
||||
include JavaScriptFixturesHelpers
|
||||
include GraphqlHelpers
|
||||
|
||||
describe GraphQL::Query, type: :request do
|
||||
let_it_be(:user) { create(:user) }
|
||||
let_it_be(:groups) { create_list(:group, 4) }
|
||||
|
||||
before_all do
|
||||
groups.each { |group| group.add_owner(user) }
|
||||
end
|
||||
|
||||
query_name = 'search_namespaces_where_user_can_transfer_projects'
|
||||
query_extension = '.query.graphql'
|
||||
|
||||
full_input_path = "projects/settings/graphql/queries/#{query_name}#{query_extension}"
|
||||
base_output_path = "graphql/projects/settings/#{query_name}"
|
||||
|
||||
it "#{base_output_path}_page_1#{query_extension}.json" do
|
||||
query = get_graphql_query_as_string(full_input_path)
|
||||
|
||||
post_graphql(query, current_user: user, variables: { first: 2 })
|
||||
|
||||
expect_graphql_errors_to_be_empty
|
||||
end
|
||||
|
||||
it "#{base_output_path}_page_2#{query_extension}.json" do
|
||||
query = get_graphql_query_as_string(full_input_path)
|
||||
|
||||
post_graphql(query, current_user: user, variables: { first: 2 })
|
||||
|
||||
post_graphql(
|
||||
query,
|
||||
current_user: user,
|
||||
variables: { first: 2, after: graphql_data_at('currentUser', 'groups', 'pageInfo', 'endCursor') }
|
||||
)
|
||||
|
||||
expect_graphql_errors_to_be_empty
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
@ -50,6 +50,7 @@ describe('DependencyProxyApp', () => {
|
|||
groupPath: 'gitlab-org',
|
||||
groupId: dummyGrouptId,
|
||||
noManifestsIllustration: 'noManifestsIllustration',
|
||||
canClearCache: true,
|
||||
};
|
||||
|
||||
function createComponent({ provide = provideDefaults } = {}) {
|
||||
|
|
@ -268,6 +269,23 @@ describe('DependencyProxyApp', () => {
|
|||
'All items in the cache are scheduled for removal.',
|
||||
);
|
||||
});
|
||||
|
||||
describe('when user has no permission to clear cache', () => {
|
||||
beforeEach(() => {
|
||||
createComponent({
|
||||
provide: {
|
||||
groupPath: 'gitlab-org',
|
||||
groupId: dummyGrouptId,
|
||||
noManifestsIllustration: 'noManifestsIllustration',
|
||||
canClearCache: false,
|
||||
},
|
||||
});
|
||||
});
|
||||
|
||||
it('does not show the clear cache dropdown list', () => {
|
||||
expect(findClearCacheDropdownList().exists()).toBe(false);
|
||||
});
|
||||
});
|
||||
});
|
||||
});
|
||||
});
|
||||
|
|
|
|||
|
|
@ -1,11 +1,19 @@
|
|||
import Vue, { nextTick } from 'vue';
|
||||
import VueApollo from 'vue-apollo';
|
||||
import searchNamespacesWhereUserCanTransferProjectsQueryResponsePage1 from 'test_fixtures/graphql/projects/settings/search_namespaces_where_user_can_transfer_projects_page_1.query.graphql.json';
|
||||
import searchNamespacesWhereUserCanTransferProjectsQueryResponsePage2 from 'test_fixtures/graphql/projects/settings/search_namespaces_where_user_can_transfer_projects_page_2.query.graphql.json';
|
||||
import {
|
||||
groupNamespaces,
|
||||
userNamespaces,
|
||||
} from 'jest/vue_shared/components/namespace_select/mock_data';
|
||||
import { shallowMountExtended } from 'helpers/vue_test_utils_helper';
|
||||
import createMockApollo from 'helpers/mock_apollo_helper';
|
||||
import { getIdFromGraphQLId } from '~/graphql_shared/utils';
|
||||
import TransferProjectForm from '~/projects/settings/components/transfer_project_form.vue';
|
||||
import NamespaceSelect from '~/vue_shared/components/namespace_select/namespace_select.vue';
|
||||
import ConfirmDanger from '~/vue_shared/components/confirm_danger/confirm_danger.vue';
|
||||
import searchNamespacesWhereUserCanTransferProjectsQuery from '~/projects/settings/graphql/queries/search_namespaces_where_user_can_transfer_projects.query.graphql';
|
||||
import waitForPromises from 'helpers/wait_for_promises';
|
||||
|
||||
describe('Transfer project form', () => {
|
||||
let wrapper;
|
||||
|
|
@ -13,36 +21,50 @@ describe('Transfer project form', () => {
|
|||
const confirmButtonText = 'Confirm';
|
||||
const confirmationPhrase = 'You must construct additional pylons!';
|
||||
|
||||
const createComponent = () =>
|
||||
shallowMountExtended(TransferProjectForm, {
|
||||
const runDebounce = () => jest.runAllTimers();
|
||||
|
||||
Vue.use(VueApollo);
|
||||
|
||||
const defaultQueryHandler = jest
|
||||
.fn()
|
||||
.mockResolvedValue(searchNamespacesWhereUserCanTransferProjectsQueryResponsePage1);
|
||||
|
||||
const createComponent = ({
|
||||
requestHandlers = [[searchNamespacesWhereUserCanTransferProjectsQuery, defaultQueryHandler]],
|
||||
} = {}) => {
|
||||
wrapper = shallowMountExtended(TransferProjectForm, {
|
||||
propsData: {
|
||||
userNamespaces,
|
||||
groupNamespaces,
|
||||
confirmButtonText,
|
||||
confirmationPhrase,
|
||||
},
|
||||
apolloProvider: createMockApollo(requestHandlers),
|
||||
});
|
||||
};
|
||||
|
||||
const findNamespaceSelect = () => wrapper.findComponent(NamespaceSelect);
|
||||
const findConfirmDanger = () => wrapper.findComponent(ConfirmDanger);
|
||||
|
||||
beforeEach(() => {
|
||||
wrapper = createComponent();
|
||||
});
|
||||
|
||||
afterEach(() => {
|
||||
wrapper.destroy();
|
||||
});
|
||||
|
||||
it('renders the namespace selector', () => {
|
||||
createComponent();
|
||||
|
||||
expect(findNamespaceSelect().exists()).toBe(true);
|
||||
});
|
||||
|
||||
it('renders the confirm button', () => {
|
||||
createComponent();
|
||||
|
||||
expect(findConfirmDanger().exists()).toBe(true);
|
||||
});
|
||||
|
||||
it('disables the confirm button by default', () => {
|
||||
createComponent();
|
||||
|
||||
expect(findConfirmDanger().attributes('disabled')).toBe('true');
|
||||
});
|
||||
|
||||
|
|
@ -50,6 +72,8 @@ describe('Transfer project form', () => {
|
|||
const [selectedItem] = groupNamespaces;
|
||||
|
||||
beforeEach(() => {
|
||||
createComponent();
|
||||
|
||||
findNamespaceSelect().vm.$emit('select', selectedItem);
|
||||
});
|
||||
|
||||
|
|
@ -69,4 +93,132 @@ describe('Transfer project form', () => {
|
|||
expect(wrapper.emitted('confirm')).toBeDefined();
|
||||
});
|
||||
});
|
||||
|
||||
it('passes correct props to `NamespaceSelect` component', async () => {
|
||||
createComponent();
|
||||
|
||||
runDebounce();
|
||||
await waitForPromises();
|
||||
|
||||
const {
|
||||
namespace,
|
||||
groups,
|
||||
} = searchNamespacesWhereUserCanTransferProjectsQueryResponsePage1.data.currentUser;
|
||||
|
||||
expect(findNamespaceSelect().props()).toMatchObject({
|
||||
userNamespaces: [
|
||||
{
|
||||
id: getIdFromGraphQLId(namespace.id),
|
||||
humanName: namespace.fullName,
|
||||
},
|
||||
],
|
||||
groupNamespaces: groups.nodes.map((node) => ({
|
||||
id: getIdFromGraphQLId(node.id),
|
||||
humanName: node.fullName,
|
||||
})),
|
||||
hasNextPageOfGroups: true,
|
||||
isLoadingMoreGroups: false,
|
||||
isSearchLoading: false,
|
||||
shouldFilterNamespaces: false,
|
||||
});
|
||||
});
|
||||
|
||||
describe('when `search` event is fired', () => {
|
||||
const arrange = async () => {
|
||||
createComponent();
|
||||
|
||||
findNamespaceSelect().vm.$emit('search', 'foo');
|
||||
|
||||
await nextTick();
|
||||
};
|
||||
|
||||
it('sets `isSearchLoading` prop to `true`', async () => {
|
||||
await arrange();
|
||||
|
||||
expect(findNamespaceSelect().props('isSearchLoading')).toBe(true);
|
||||
});
|
||||
|
||||
it('passes `search` variable to query', async () => {
|
||||
await arrange();
|
||||
|
||||
runDebounce();
|
||||
await waitForPromises();
|
||||
|
||||
expect(defaultQueryHandler).toHaveBeenCalledWith(expect.objectContaining({ search: 'foo' }));
|
||||
});
|
||||
});
|
||||
|
||||
describe('when `load-more-groups` event is fired', () => {
|
||||
let queryHandler;
|
||||
|
||||
const arrange = async () => {
|
||||
queryHandler = jest.fn();
|
||||
queryHandler.mockResolvedValueOnce(
|
||||
searchNamespacesWhereUserCanTransferProjectsQueryResponsePage1,
|
||||
);
|
||||
queryHandler.mockResolvedValueOnce(
|
||||
searchNamespacesWhereUserCanTransferProjectsQueryResponsePage2,
|
||||
);
|
||||
|
||||
createComponent({
|
||||
requestHandlers: [[searchNamespacesWhereUserCanTransferProjectsQuery, queryHandler]],
|
||||
});
|
||||
|
||||
runDebounce();
|
||||
await waitForPromises();
|
||||
|
||||
findNamespaceSelect().vm.$emit('load-more-groups');
|
||||
await nextTick();
|
||||
};
|
||||
|
||||
it('sets `isLoadingMoreGroups` prop to `true`', async () => {
|
||||
await arrange();
|
||||
|
||||
expect(findNamespaceSelect().props('isLoadingMoreGroups')).toBe(true);
|
||||
});
|
||||
|
||||
it('passes `after` and `first` variables to query', async () => {
|
||||
await arrange();
|
||||
|
||||
runDebounce();
|
||||
await waitForPromises();
|
||||
|
||||
expect(queryHandler).toHaveBeenCalledWith(
|
||||
expect.objectContaining({
|
||||
first: 25,
|
||||
after:
|
||||
searchNamespacesWhereUserCanTransferProjectsQueryResponsePage1.data.currentUser.groups
|
||||
.pageInfo.endCursor,
|
||||
}),
|
||||
);
|
||||
});
|
||||
|
||||
it('updates `groupNamespaces` prop with new groups', async () => {
|
||||
await arrange();
|
||||
|
||||
runDebounce();
|
||||
await waitForPromises();
|
||||
|
||||
expect(findNamespaceSelect().props('groupNamespaces')).toEqual(
|
||||
[
|
||||
...searchNamespacesWhereUserCanTransferProjectsQueryResponsePage1.data.currentUser.groups
|
||||
.nodes,
|
||||
...searchNamespacesWhereUserCanTransferProjectsQueryResponsePage2.data.currentUser.groups
|
||||
.nodes,
|
||||
].map((node) => ({
|
||||
id: getIdFromGraphQLId(node.id),
|
||||
humanName: node.fullName,
|
||||
})),
|
||||
);
|
||||
});
|
||||
|
||||
it('updates `hasNextPageOfGroups` prop', async () => {
|
||||
await arrange();
|
||||
|
||||
runDebounce();
|
||||
await waitForPromises();
|
||||
|
||||
expect(findNamespaceSelect().props('hasNextPageOfGroups')).toBe(false);
|
||||
});
|
||||
});
|
||||
});
|
||||
|
|
|
|||
|
|
@ -1,5 +1,12 @@
|
|||
import { nextTick } from 'vue';
|
||||
import { GlDropdown, GlDropdownItem, GlDropdownSectionHeader, GlSearchBoxByType } from '@gitlab/ui';
|
||||
import {
|
||||
GlDropdown,
|
||||
GlDropdownItem,
|
||||
GlDropdownSectionHeader,
|
||||
GlSearchBoxByType,
|
||||
GlIntersectionObserver,
|
||||
GlLoadingIcon,
|
||||
} from '@gitlab/ui';
|
||||
import { shallowMountExtended } from 'helpers/vue_test_utils_helper';
|
||||
import NamespaceSelect, {
|
||||
i18n,
|
||||
|
|
@ -7,7 +14,7 @@ import NamespaceSelect, {
|
|||
} from '~/vue_shared/components/namespace_select/namespace_select.vue';
|
||||
import { userNamespaces, groupNamespaces } from './mock_data';
|
||||
|
||||
const FLAT_NAMESPACES = [...groupNamespaces, ...userNamespaces];
|
||||
const FLAT_NAMESPACES = [...userNamespaces, ...groupNamespaces];
|
||||
const EMPTY_NAMESPACE_TITLE = 'Empty namespace TEST';
|
||||
const EMPTY_NAMESPACE_ITEM = { id: EMPTY_NAMESPACE_ID, humanName: EMPTY_NAMESPACE_TITLE };
|
||||
|
||||
|
|
@ -31,6 +38,8 @@ describe('Namespace Select', () => {
|
|||
const findDropdown = () => wrapper.findComponent(GlDropdown);
|
||||
const findDropdownText = () => findDropdown().props('text');
|
||||
const findDropdownItems = () => wrapper.findAllComponents(GlDropdownItem);
|
||||
const findGroupDropdownItems = () =>
|
||||
wrapper.findByTestId('namespace-list-groups').findAllComponents(GlDropdownItem);
|
||||
const findDropdownItemsTexts = () => findDropdownItems().wrappers.map((x) => x.text());
|
||||
const findSectionHeaders = () => wrapper.findAllComponents(GlDropdownSectionHeader);
|
||||
const findSearchBox = () => wrapper.findComponent(GlSearchBoxByType);
|
||||
|
|
@ -59,7 +68,7 @@ describe('Namespace Select', () => {
|
|||
|
||||
it('splits group and user namespaces', () => {
|
||||
const headers = findSectionHeaders();
|
||||
expect(wrappersText(headers)).toEqual([i18n.GROUPS, i18n.USERS]);
|
||||
expect(wrappersText(headers)).toEqual([i18n.USERS, i18n.GROUPS]);
|
||||
});
|
||||
|
||||
it('does not render wrapper as full width', () => {
|
||||
|
|
@ -89,18 +98,20 @@ describe('Namespace Select', () => {
|
|||
|
||||
describe('with search', () => {
|
||||
it.each`
|
||||
term | includeEmptyNamespace | expectedItems
|
||||
${''} | ${false} | ${[...groupNamespaces, ...userNamespaces]}
|
||||
${'sub'} | ${false} | ${[groupNamespaces[1]]}
|
||||
${'User'} | ${false} | ${[...userNamespaces]}
|
||||
${'User'} | ${true} | ${[...userNamespaces]}
|
||||
${'namespace'} | ${true} | ${[EMPTY_NAMESPACE_ITEM, ...userNamespaces]}
|
||||
term | includeEmptyNamespace | shouldFilterNamespaces | expectedItems
|
||||
${''} | ${false} | ${true} | ${[...userNamespaces, ...groupNamespaces]}
|
||||
${'sub'} | ${false} | ${true} | ${[groupNamespaces[1]]}
|
||||
${'User'} | ${false} | ${true} | ${[...userNamespaces]}
|
||||
${'User'} | ${true} | ${true} | ${[...userNamespaces]}
|
||||
${'namespace'} | ${true} | ${true} | ${[EMPTY_NAMESPACE_ITEM, ...userNamespaces]}
|
||||
${'sub'} | ${false} | ${false} | ${[...userNamespaces, ...groupNamespaces]}
|
||||
`(
|
||||
'with term=$term and includeEmptyNamespace=$includeEmptyNamespace, should show $expectedItems.length',
|
||||
async ({ term, includeEmptyNamespace, expectedItems }) => {
|
||||
'with term=$term, includeEmptyNamespace=$includeEmptyNamespace, and shouldFilterNamespaces=$shouldFilterNamespaces should show $expectedItems.length',
|
||||
async ({ term, includeEmptyNamespace, shouldFilterNamespaces, expectedItems }) => {
|
||||
wrapper = createComponent({
|
||||
includeEmptyNamespace,
|
||||
emptyNamespaceTitle: EMPTY_NAMESPACE_TITLE,
|
||||
shouldFilterNamespaces,
|
||||
});
|
||||
|
||||
search(term);
|
||||
|
|
@ -114,6 +125,18 @@ describe('Namespace Select', () => {
|
|||
);
|
||||
});
|
||||
|
||||
describe('when search is typed in', () => {
|
||||
it('emits `search` event', async () => {
|
||||
wrapper = createComponent();
|
||||
|
||||
wrapper.findComponent(GlSearchBoxByType).vm.$emit('input', 'foo');
|
||||
|
||||
await nextTick();
|
||||
|
||||
expect(wrapper.emitted('search')).toEqual([['foo']]);
|
||||
});
|
||||
});
|
||||
|
||||
describe('with a selected namespace', () => {
|
||||
const selectedGroupIndex = 1;
|
||||
const selectedItem = groupNamespaces[selectedGroupIndex];
|
||||
|
|
@ -121,7 +144,8 @@ describe('Namespace Select', () => {
|
|||
beforeEach(() => {
|
||||
wrapper = createComponent();
|
||||
|
||||
findDropdownItems().at(selectedGroupIndex).vm.$emit('click');
|
||||
wrapper.findComponent(GlSearchBoxByType).vm.$emit('input', 'foo');
|
||||
findGroupDropdownItems().at(selectedGroupIndex).vm.$emit('click');
|
||||
});
|
||||
|
||||
it('sets the dropdown text', () => {
|
||||
|
|
@ -132,6 +156,10 @@ describe('Namespace Select', () => {
|
|||
const args = [selectedItem];
|
||||
expect(wrapper.emitted('select')).toEqual([args]);
|
||||
});
|
||||
|
||||
it('clears search', () => {
|
||||
expect(wrapper.findComponent(GlSearchBoxByType).props('value')).toBe('');
|
||||
});
|
||||
});
|
||||
|
||||
describe('with an empty namespace option', () => {
|
||||
|
|
@ -166,4 +194,33 @@ describe('Namespace Select', () => {
|
|||
expect(findDropdownItemsTexts().includes(EMPTY_NAMESPACE_TITLE)).toBe(shouldShow);
|
||||
});
|
||||
});
|
||||
|
||||
describe('when `hasNextPageOfGroups` prop is `true`', () => {
|
||||
it('renders `GlIntersectionObserver` and emits `load-more-groups` event when bottom is reached', () => {
|
||||
wrapper = createComponent({ hasNextPageOfGroups: true });
|
||||
|
||||
const intersectionObserver = wrapper.findComponent(GlIntersectionObserver);
|
||||
|
||||
intersectionObserver.vm.$emit('appear');
|
||||
|
||||
expect(intersectionObserver.exists()).toBe(true);
|
||||
expect(wrapper.emitted('load-more-groups')).toEqual([[]]);
|
||||
});
|
||||
|
||||
describe('when `isLoadingMoreGroups` prop is `true`', () => {
|
||||
it('renders a loading icon', () => {
|
||||
wrapper = createComponent({ hasNextPageOfGroups: true, isLoadingMoreGroups: true });
|
||||
|
||||
expect(wrapper.findComponent(GlLoadingIcon).exists()).toBe(true);
|
||||
});
|
||||
});
|
||||
});
|
||||
|
||||
describe('when `isSearchLoading` prop is `true`', () => {
|
||||
it('sets `isLoading` prop to `true`', () => {
|
||||
wrapper = createComponent({ isSearchLoading: true });
|
||||
|
||||
expect(wrapper.findComponent(GlSearchBoxByType).props('isLoading')).toBe(true);
|
||||
});
|
||||
});
|
||||
});
|
||||
|
|
|
|||
|
|
@ -47,4 +47,18 @@ RSpec.describe GraphqlTriggers do
|
|||
GraphqlTriggers.issuable_labels_updated(issue)
|
||||
end
|
||||
end
|
||||
|
||||
describe '.issuable_dates_updated' do
|
||||
it 'triggers the issuableDatesUpdated subscription' do
|
||||
work_item = create(:work_item)
|
||||
|
||||
expect(GitlabSchema.subscriptions).to receive(:trigger).with(
|
||||
'issuableDatesUpdated',
|
||||
{ issuable_id: work_item.to_gid },
|
||||
work_item
|
||||
).and_call_original
|
||||
|
||||
GraphqlTriggers.issuable_dates_updated(work_item)
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ RSpec.describe GitlabSchema.types['Subscription'] do
|
|||
issue_crm_contacts_updated
|
||||
issuable_title_updated
|
||||
issuable_labels_updated
|
||||
issuable_dates_updated
|
||||
]
|
||||
|
||||
expect(described_class).to have_graphql_fields(*expected_fields).only
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@ RSpec.describe Types::WorkItems::WidgetInterface do
|
|||
WorkItems::Widgets::Description | Types::WorkItems::Widgets::DescriptionType
|
||||
WorkItems::Widgets::Hierarchy | Types::WorkItems::Widgets::HierarchyType
|
||||
WorkItems::Widgets::Assignees | Types::WorkItems::Widgets::AssigneesType
|
||||
WorkItems::Widgets::Labels | Types::WorkItems::Widgets::LabelsType
|
||||
end
|
||||
|
||||
with_them do
|
||||
|
|
|
|||
|
|
@ -0,0 +1,11 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
require 'spec_helper'
|
||||
|
||||
RSpec.describe Types::WorkItems::Widgets::LabelsType do
|
||||
it 'exposes the expected fields' do
|
||||
expected_fields = %i[labels allowsScopedLabels type]
|
||||
|
||||
expect(described_class).to have_graphql_fields(*expected_fields)
|
||||
end
|
||||
end
|
||||
|
|
@ -45,39 +45,6 @@ RSpec.describe NamespacesHelper do
|
|||
user_group.add_owner(user)
|
||||
end
|
||||
|
||||
describe '#namespaces_as_json' do
|
||||
let(:result) { helper.namespaces_as_json(user) }
|
||||
|
||||
before do
|
||||
allow(helper).to receive(:current_user).and_return(user)
|
||||
end
|
||||
|
||||
it 'returns the user\'s groups' do
|
||||
json_data = Gitlab::Json.parse(result)
|
||||
|
||||
expect(result).to include('group')
|
||||
expect(json_data['group']).to include(
|
||||
"id" => user_group.id,
|
||||
"name" => user_group.name,
|
||||
"display_path" => user_group.full_path,
|
||||
"human_name" => user_group.human_name
|
||||
)
|
||||
end
|
||||
|
||||
it 'returns the user\'s namespace' do
|
||||
user_namespace = user.namespace
|
||||
json_data = Gitlab::Json.parse(result)
|
||||
|
||||
expect(result).to include('user')
|
||||
expect(json_data['user']).to include(
|
||||
"id" => user_namespace.id,
|
||||
"name" => user_namespace.name,
|
||||
"display_path" => user_namespace.full_path,
|
||||
"human_name" => user_namespace.human_name
|
||||
)
|
||||
end
|
||||
end
|
||||
|
||||
describe '#namespaces_options' do
|
||||
context 'when admin mode is enabled', :enable_admin_mode do
|
||||
it 'returns groups without being a member for admin' do
|
||||
|
|
|
|||
|
|
@ -0,0 +1,123 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
require 'spec_helper'
|
||||
|
||||
RSpec.describe Gitlab::Database::LockWritesManager do
|
||||
let(:connection) { ApplicationRecord.connection }
|
||||
let(:test_table) { '_test_table' }
|
||||
let(:logger) { instance_double(Logger) }
|
||||
|
||||
subject(:lock_writes_manager) do
|
||||
described_class.new(
|
||||
table_name: test_table,
|
||||
connection: connection,
|
||||
database_name: 'main',
|
||||
logger: logger
|
||||
)
|
||||
end
|
||||
|
||||
before do
|
||||
allow(logger).to receive(:info)
|
||||
|
||||
connection.execute(<<~SQL)
|
||||
CREATE TABLE #{test_table} (id integer NOT NULL, value integer NOT NULL DEFAULT 0);
|
||||
|
||||
INSERT INTO #{test_table} (id, value)
|
||||
VALUES (1, 1), (2, 2), (3, 3)
|
||||
SQL
|
||||
end
|
||||
|
||||
describe '#lock_writes' do
|
||||
it 'prevents any writes on the table' do
|
||||
subject.lock_writes
|
||||
|
||||
expect do
|
||||
connection.execute("delete from #{test_table}")
|
||||
end.to raise_error(ActiveRecord::StatementInvalid, /Table: "#{test_table}" is write protected/)
|
||||
end
|
||||
|
||||
it 'prevents truncating the table' do
|
||||
subject.lock_writes
|
||||
|
||||
expect do
|
||||
connection.execute("truncate #{test_table}")
|
||||
end.to raise_error(ActiveRecord::StatementInvalid, /Table: "#{test_table}" is write protected/)
|
||||
end
|
||||
|
||||
it 'adds 3 triggers to the ci schema tables on the main database' do
|
||||
expect do
|
||||
subject.lock_writes
|
||||
end.to change {
|
||||
number_of_triggers_on(connection, test_table)
|
||||
}.by(3) # Triggers to block INSERT / UPDATE / DELETE
|
||||
# Triggers on TRUNCATE are not added to the information_schema.triggers
|
||||
# See https://www.postgresql.org/message-id/16934.1568989957%40sss.pgh.pa.us
|
||||
end
|
||||
|
||||
it 'logs the write locking' do
|
||||
expect(logger).to receive(:info).with("Database: 'main', Table: '_test_table': Lock Writes")
|
||||
|
||||
subject.lock_writes
|
||||
end
|
||||
|
||||
it 'retries again if it receives a statement_timeout a few number of times' do
|
||||
error_message = "PG::QueryCanceled: ERROR: canceling statement due to statement timeout"
|
||||
call_count = 0
|
||||
allow(connection).to receive(:execute) do |statement|
|
||||
if statement.include?("CREATE TRIGGER")
|
||||
call_count += 1
|
||||
raise(ActiveRecord::QueryCanceled, error_message) if call_count.even?
|
||||
end
|
||||
end
|
||||
subject.lock_writes
|
||||
end
|
||||
|
||||
it 'raises the exception if it happened many times' do
|
||||
error_message = "PG::QueryCanceled: ERROR: canceling statement due to statement timeout"
|
||||
allow(connection).to receive(:execute) do |statement|
|
||||
if statement.include?("CREATE TRIGGER")
|
||||
raise(ActiveRecord::QueryCanceled, error_message)
|
||||
end
|
||||
end
|
||||
|
||||
expect do
|
||||
subject.lock_writes
|
||||
end.to raise_error(ActiveRecord::QueryCanceled)
|
||||
end
|
||||
end
|
||||
|
||||
describe '#unlock_writes' do
|
||||
before do
|
||||
subject.lock_writes
|
||||
end
|
||||
|
||||
it 'allows writing on the table again' do
|
||||
subject.unlock_writes
|
||||
|
||||
expect do
|
||||
connection.execute("delete from #{test_table}")
|
||||
end.not_to raise_error
|
||||
end
|
||||
|
||||
it 'removes the write protection triggers from the gitlab_main tables on the ci database' do
|
||||
expect do
|
||||
subject.unlock_writes
|
||||
end.to change {
|
||||
number_of_triggers_on(connection, test_table)
|
||||
}.by(-3) # Triggers to block INSERT / UPDATE / DELETE
|
||||
# Triggers on TRUNCATE are not added to the information_schema.triggers
|
||||
# See https://www.postgresql.org/message-id/16934.1568989957%40sss.pgh.pa.us
|
||||
end
|
||||
|
||||
it 'logs the write unlocking' do
|
||||
expect(logger).to receive(:info).with("Database: 'main', Table: '_test_table': Allow Writes")
|
||||
|
||||
subject.unlock_writes
|
||||
end
|
||||
end
|
||||
|
||||
def number_of_triggers_on(connection, table_name)
|
||||
connection
|
||||
.select_value("SELECT count(*) FROM information_schema.triggers WHERE event_object_table=$1", nil, [table_name])
|
||||
end
|
||||
end
|
||||
|
|
@ -1022,6 +1022,40 @@ RSpec.describe Gitlab::Database::MigrationHelpers do
|
|||
expect(Project.sum(:star_count)).to eq(2 * Project.count)
|
||||
end
|
||||
end
|
||||
|
||||
context 'when the table is write-locked' do
|
||||
let(:test_table) { '_test_table' }
|
||||
let(:lock_writes_manager) do
|
||||
Gitlab::Database::LockWritesManager.new(
|
||||
table_name: test_table,
|
||||
connection: model.connection,
|
||||
database_name: 'main'
|
||||
)
|
||||
end
|
||||
|
||||
before do
|
||||
model.connection.execute(<<~SQL)
|
||||
CREATE TABLE #{test_table} (id integer NOT NULL, value integer NOT NULL DEFAULT 0);
|
||||
|
||||
INSERT INTO #{test_table} (id, value)
|
||||
VALUES (1, 1), (2, 2), (3, 3)
|
||||
SQL
|
||||
|
||||
lock_writes_manager.lock_writes
|
||||
end
|
||||
|
||||
it 'disables the write-lock trigger function' do
|
||||
expect do
|
||||
model.update_column_in_batches(test_table, :value, Arel.sql('1+1'), disable_lock_writes: true)
|
||||
end.not_to raise_error
|
||||
end
|
||||
|
||||
it 'raises an error if it does not disable the trigger function' do
|
||||
expect do
|
||||
model.update_column_in_batches(test_table, :value, Arel.sql('1+1'), disable_lock_writes: false)
|
||||
end.to raise_error(ActiveRecord::StatementInvalid, /Table: "#{test_table}" is write protected/)
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
context 'when running inside the transaction' do
|
||||
|
|
@ -1122,6 +1156,7 @@ RSpec.describe Gitlab::Database::MigrationHelpers do
|
|||
it 'copies the value to the new column using the type_cast_function', :aggregate_failures do
|
||||
expect(model).to receive(:copy_indexes).with(:users, :id, :new)
|
||||
expect(model).to receive(:add_not_null_constraint).with(:users, :new)
|
||||
expect(model).to receive(:execute).with("SELECT set_config('lock_writes.users', 'false', true)")
|
||||
expect(model).to receive(:execute).with("UPDATE \"users\" SET \"new\" = cast_to_jsonb_with_default(\"users\".\"id\") WHERE \"users\".\"id\" >= #{user.id}")
|
||||
expect(copy_trigger).to receive(:create).with(:id, :new, trigger_name: nil)
|
||||
|
||||
|
|
@ -1181,6 +1216,34 @@ RSpec.describe Gitlab::Database::MigrationHelpers do
|
|||
end
|
||||
end
|
||||
|
||||
context 'when the table in the other database is write-locked' do
|
||||
let(:test_table) { '_test_table' }
|
||||
let(:lock_writes_manager) do
|
||||
Gitlab::Database::LockWritesManager.new(
|
||||
table_name: test_table,
|
||||
connection: model.connection,
|
||||
database_name: 'main'
|
||||
)
|
||||
end
|
||||
|
||||
before do
|
||||
model.connection.execute(<<~SQL)
|
||||
CREATE TABLE #{test_table} (id integer NOT NULL, value integer NOT NULL DEFAULT 0);
|
||||
|
||||
INSERT INTO #{test_table} (id, value)
|
||||
VALUES (1, 1), (2, 2), (3, 3)
|
||||
SQL
|
||||
|
||||
lock_writes_manager.lock_writes
|
||||
end
|
||||
|
||||
it 'does not raise an error when renaming the column' do
|
||||
expect do
|
||||
model.rename_column_concurrently(test_table, :value, :new_value)
|
||||
end.not_to raise_error
|
||||
end
|
||||
end
|
||||
|
||||
context 'when the column to be renamed does not exist' do
|
||||
before do
|
||||
allow(model).to receive(:columns).and_return([])
|
||||
|
|
|
|||
|
|
@ -9,6 +9,40 @@ RSpec.describe Gitlab::FormBuilders::GitlabUiFormBuilder do
|
|||
|
||||
let_it_be(:form_builder) { described_class.new(:user, user, fake_action_view_base, {}) }
|
||||
|
||||
describe '#submit' do
|
||||
context 'without pajamas_button enabled' do
|
||||
subject(:submit_html) do
|
||||
form_builder.submit('Save', class: 'gl-button btn-confirm custom-class', data: { test: true })
|
||||
end
|
||||
|
||||
it 'renders a submit input' do
|
||||
expected_html = <<~EOS
|
||||
<input type="submit" name="commit" value="Save" class="gl-button btn-confirm custom-class" data-test="true" data-disable-with="Save" />
|
||||
EOS
|
||||
|
||||
expect(html_strip_whitespace(submit_html)).to eq(html_strip_whitespace(expected_html))
|
||||
end
|
||||
end
|
||||
|
||||
context 'with pajamas_button enabled' do
|
||||
subject(:submit_html) do
|
||||
form_builder.submit('Save', pajamas_button: true, class: 'custom-class', data: { test: true })
|
||||
end
|
||||
|
||||
it 'renders a submit button' do
|
||||
expected_html = <<~EOS
|
||||
<button class="gl-button btn btn-md btn-confirm custom-class" data-test="true" type="submit">
|
||||
<span class="gl-button-text">
|
||||
Save
|
||||
</span>
|
||||
</button>
|
||||
EOS
|
||||
|
||||
expect(html_strip_whitespace(submit_html)).to eq(html_strip_whitespace(expected_html))
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
describe '#gitlab_ui_checkbox_component' do
|
||||
context 'when not using slots' do
|
||||
let(:optional_args) { {} }
|
||||
|
|
|
|||
|
|
@ -43,6 +43,7 @@ RSpec.describe WorkItem do
|
|||
is_expected.to include(
|
||||
instance_of(WorkItems::Widgets::Description),
|
||||
instance_of(WorkItems::Widgets::Hierarchy),
|
||||
instance_of(WorkItems::Widgets::Labels),
|
||||
instance_of(WorkItems::Widgets::Assignees),
|
||||
instance_of(WorkItems::Widgets::StartAndDueDate)
|
||||
)
|
||||
|
|
|
|||
|
|
@ -67,6 +67,7 @@ RSpec.describe WorkItems::Type do
|
|||
is_expected.to include(
|
||||
::WorkItems::Widgets::Description,
|
||||
::WorkItems::Widgets::Hierarchy,
|
||||
::WorkItems::Widgets::Labels,
|
||||
::WorkItems::Widgets::Assignees,
|
||||
::WorkItems::Widgets::StartAndDueDate
|
||||
)
|
||||
|
|
|
|||
|
|
@ -0,0 +1,31 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
require 'spec_helper'
|
||||
|
||||
RSpec.describe WorkItems::Widgets::Labels do
|
||||
let_it_be(:work_item) { create(:work_item, labels: [create(:label)]) }
|
||||
|
||||
describe '.type' do
|
||||
subject { described_class.type }
|
||||
|
||||
it { is_expected.to eq(:labels) }
|
||||
end
|
||||
|
||||
describe '#type' do
|
||||
subject { described_class.new(work_item).type }
|
||||
|
||||
it { is_expected.to eq(:labels) }
|
||||
end
|
||||
|
||||
describe '#labels' do
|
||||
subject { described_class.new(work_item).labels }
|
||||
|
||||
it { is_expected.to eq(work_item.labels) }
|
||||
end
|
||||
|
||||
describe '#allowScopedLabels' do
|
||||
subject { described_class.new(work_item).allows_scoped_labels? }
|
||||
|
||||
it { is_expected.to eq(work_item.allows_scoped_labels?) }
|
||||
end
|
||||
end
|
||||
|
|
@ -215,6 +215,44 @@ RSpec.describe 'Query.work_item(id)' do
|
|||
end
|
||||
end
|
||||
|
||||
describe 'labels widget' do
|
||||
let(:labels) { create_list(:label, 2, project: project) }
|
||||
let(:work_item) { create(:work_item, project: project, labels: labels) }
|
||||
|
||||
let(:work_item_fields) do
|
||||
<<~GRAPHQL
|
||||
id
|
||||
widgets {
|
||||
type
|
||||
... on WorkItemWidgetLabels {
|
||||
labels {
|
||||
nodes {
|
||||
id
|
||||
title
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
GRAPHQL
|
||||
end
|
||||
|
||||
it 'returns widget information' do
|
||||
expect(work_item_data).to include(
|
||||
'id' => work_item.to_gid.to_s,
|
||||
'widgets' => include(
|
||||
hash_including(
|
||||
'type' => 'LABELS',
|
||||
'labels' => {
|
||||
'nodes' => match_array(
|
||||
labels.map { |a| { 'id' => a.to_gid.to_s, 'title' => a.title } }
|
||||
)
|
||||
}
|
||||
)
|
||||
)
|
||||
)
|
||||
end
|
||||
end
|
||||
|
||||
describe 'start and due date widget' do
|
||||
let(:work_item_fields) do
|
||||
<<~GRAPHQL
|
||||
|
|
|
|||
|
|
@ -988,6 +988,52 @@ RSpec.describe Issues::UpdateService, :mailer do
|
|||
end
|
||||
end
|
||||
|
||||
context 'updating dates' do
|
||||
subject(:result) { described_class.new(project: project, current_user: user, params: params).execute(issue) }
|
||||
|
||||
let(:updated_date) { 1.week.from_now.to_date }
|
||||
|
||||
shared_examples 'issue update service that triggers date updates' do
|
||||
it 'triggers graphql date updated subscription' do
|
||||
expect(GraphqlTriggers).to receive(:issuable_dates_updated).with(issue).and_call_original
|
||||
|
||||
result
|
||||
end
|
||||
end
|
||||
|
||||
shared_examples 'issue update service that does not trigger date updates' do
|
||||
it 'does not trigger date updated subscriptions' do
|
||||
expect(GraphqlTriggers).not_to receive(:issuable_dates_updated)
|
||||
|
||||
result
|
||||
end
|
||||
end
|
||||
|
||||
context 'when due_date is updated' do
|
||||
let(:params) { { due_date: updated_date } }
|
||||
|
||||
it_behaves_like 'issue update service that triggers date updates'
|
||||
end
|
||||
|
||||
context 'when start_date is updated' do
|
||||
let(:params) { { start_date: updated_date } }
|
||||
|
||||
it_behaves_like 'issue update service that triggers date updates'
|
||||
end
|
||||
|
||||
context 'when no date is updated' do
|
||||
let(:params) { { title: 'should not trigger date updates' } }
|
||||
|
||||
it_behaves_like 'issue update service that does not trigger date updates'
|
||||
end
|
||||
|
||||
context 'when update is not successful but date is provided' do
|
||||
let(:params) { { title: '', due_date: updated_date } }
|
||||
|
||||
it_behaves_like 'issue update service that does not trigger date updates'
|
||||
end
|
||||
end
|
||||
|
||||
context 'updating asssignee_id' do
|
||||
it 'does not update assignee when assignee_id is invalid' do
|
||||
update_issue(assignee_ids: [-1])
|
||||
|
|
|
|||
|
|
@ -36,6 +36,14 @@ RSpec.describe WorkItems::UpdateService do
|
|||
stub_spam_services
|
||||
end
|
||||
|
||||
shared_examples 'update service that triggers graphql dates updated subscription' do
|
||||
it 'triggers graphql subscription issueableDatesUpdated' do
|
||||
expect(GraphqlTriggers).to receive(:issuable_dates_updated).with(work_item).and_call_original
|
||||
|
||||
update_work_item
|
||||
end
|
||||
end
|
||||
|
||||
context 'when title is changed' do
|
||||
let(:opts) { { title: 'changed' } }
|
||||
|
||||
|
|
@ -187,6 +195,32 @@ RSpec.describe WorkItems::UpdateService do
|
|||
end
|
||||
end
|
||||
|
||||
context 'for start and due date widget' do
|
||||
let(:updated_date) { 1.week.from_now.to_date }
|
||||
|
||||
context 'when due_date is updated' do
|
||||
let(:widget_params) { { start_and_due_date_widget: { due_date: updated_date } } }
|
||||
|
||||
it_behaves_like 'update service that triggers graphql dates updated subscription'
|
||||
end
|
||||
|
||||
context 'when start_date is updated' do
|
||||
let(:widget_params) { { start_and_due_date_widget: { start_date: updated_date } } }
|
||||
|
||||
it_behaves_like 'update service that triggers graphql dates updated subscription'
|
||||
end
|
||||
|
||||
context 'when no date param is updated' do
|
||||
let(:opts) { { title: 'should not trigger' } }
|
||||
|
||||
it 'does not trigger date updated subscription' do
|
||||
expect(GraphqlTriggers).not_to receive(:issuable_dates_updated)
|
||||
|
||||
update_work_item
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
context 'for the hierarchy widget' do
|
||||
let(:opts) { { title: 'changed' } }
|
||||
let_it_be(:child_work_item) { create(:work_item, :task, project: project) }
|
||||
|
|
|
|||
|
|
@ -49,26 +49,6 @@ RSpec.describe 'gitlab:db:lock_writes', :silence_stdout, :reestablished_active_r
|
|||
end
|
||||
|
||||
context 'when locking writes' do
|
||||
it 'adds 3 triggers to the ci schema tables on the main database' do
|
||||
expect do
|
||||
run_rake_task('gitlab:db:lock_writes')
|
||||
end.to change {
|
||||
number_of_triggers_on(main_connection, Ci::Build.table_name)
|
||||
}.by(3) # Triggers to block INSERT / UPDATE / DELETE
|
||||
# Triggers on TRUNCATE are not added to the information_schema.triggers
|
||||
# See https://www.postgresql.org/message-id/16934.1568989957%40sss.pgh.pa.us
|
||||
end
|
||||
|
||||
it 'adds 3 triggers to the main schema tables on the ci database' do
|
||||
expect do
|
||||
run_rake_task('gitlab:db:lock_writes')
|
||||
end.to change {
|
||||
number_of_triggers_on(ci_connection, Project.table_name)
|
||||
}.by(3) # Triggers to block INSERT / UPDATE / DELETE
|
||||
# Triggers on TRUNCATE are not added to the information_schema.triggers
|
||||
# See https://www.postgresql.org/message-id/16934.1568989957%40sss.pgh.pa.us
|
||||
end
|
||||
|
||||
it 'still allows writes on the tables with the correct connections' do
|
||||
Project.update_all(updated_at: Time.now)
|
||||
Ci::Build.update_all(updated_at: Time.now)
|
||||
|
|
@ -107,31 +87,6 @@ RSpec.describe 'gitlab:db:lock_writes', :silence_stdout, :reestablished_active_r
|
|||
main_connection.execute("truncate ci_build_needs")
|
||||
end.to raise_error(ActiveRecord::StatementInvalid, /Table: "ci_build_needs" is write protected/)
|
||||
end
|
||||
|
||||
it 'retries again if it receives a statement_timeout a few number of times' do
|
||||
error_message = "PG::QueryCanceled: ERROR: canceling statement due to statement timeout"
|
||||
call_count = 0
|
||||
allow(main_connection).to receive(:execute) do |statement|
|
||||
if statement.include?("CREATE TRIGGER")
|
||||
call_count += 1
|
||||
raise(ActiveRecord::QueryCanceled, error_message) if call_count.even?
|
||||
end
|
||||
end
|
||||
run_rake_task('gitlab:db:lock_writes')
|
||||
end
|
||||
|
||||
it 'raises the exception if it happened many times' do
|
||||
error_message = "PG::QueryCanceled: ERROR: canceling statement due to statement timeout"
|
||||
allow(main_connection).to receive(:execute) do |statement|
|
||||
if statement.include?("CREATE TRIGGER")
|
||||
raise(ActiveRecord::QueryCanceled, error_message)
|
||||
end
|
||||
end
|
||||
|
||||
expect do
|
||||
run_rake_task('gitlab:db:lock_writes')
|
||||
end.to raise_error(ActiveRecord::QueryCanceled)
|
||||
end
|
||||
end
|
||||
|
||||
context 'multiple shared databases' do
|
||||
|
|
@ -156,26 +111,8 @@ RSpec.describe 'gitlab:db:lock_writes', :silence_stdout, :reestablished_active_r
|
|||
run_rake_task('gitlab:db:lock_writes')
|
||||
end
|
||||
|
||||
it 'removes the write protection triggers from the gitlab_main tables on the ci database' do
|
||||
expect do
|
||||
run_rake_task('gitlab:db:unlock_writes')
|
||||
end.to change {
|
||||
number_of_triggers_on(ci_connection, Project.table_name)
|
||||
}.by(-3) # Triggers to block INSERT / UPDATE / DELETE
|
||||
# Triggers on TRUNCATE are not added to the information_schema.triggers
|
||||
# See https://www.postgresql.org/message-id/16934.1568989957%40sss.pgh.pa.us
|
||||
|
||||
expect do
|
||||
ci_connection.execute("delete from projects")
|
||||
end.not_to raise_error
|
||||
end
|
||||
|
||||
it 'removes the write protection triggers from the gitlab_ci tables on the main database' do
|
||||
expect do
|
||||
run_rake_task('gitlab:db:unlock_writes')
|
||||
end.to change {
|
||||
number_of_triggers_on(main_connection, Ci::Build.table_name)
|
||||
}.by(-3)
|
||||
it 'allows writes again on the gitlab_ci tables on the main database' do
|
||||
run_rake_task('gitlab:db:unlock_writes')
|
||||
|
||||
expect do
|
||||
main_connection.execute("delete from ci_builds")
|
||||
|
|
@ -187,9 +124,4 @@ RSpec.describe 'gitlab:db:lock_writes', :silence_stdout, :reestablished_active_r
|
|||
def number_of_triggers(connection)
|
||||
connection.select_value("SELECT count(*) FROM information_schema.triggers")
|
||||
end
|
||||
|
||||
def number_of_triggers_on(connection, table_name)
|
||||
connection
|
||||
.select_value("SELECT count(*) FROM information_schema.triggers WHERE event_object_table=$1", nil, [table_name])
|
||||
end
|
||||
end
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ require (
|
|||
golang.org/x/tools v0.1.11
|
||||
google.golang.org/grpc v1.48.0
|
||||
google.golang.org/protobuf v1.28.1
|
||||
honnef.co/go/tools v0.3.2
|
||||
honnef.co/go/tools v0.3.3
|
||||
)
|
||||
|
||||
require (
|
||||
|
|
@ -116,3 +116,12 @@ require (
|
|||
gopkg.in/DataDog/dd-trace-go.v1 v1.32.0 // indirect
|
||||
gopkg.in/yaml.v3 v3.0.1 // indirect
|
||||
)
|
||||
|
||||
exclude (
|
||||
// CVE-2020-28483
|
||||
github.com/gin-gonic/gin v1.4.0
|
||||
github.com/gin-gonic/gin v1.6.3
|
||||
|
||||
// CVE-2021-42576
|
||||
github.com/microcosm-cc/bluemonday v1.0.2
|
||||
)
|
||||
|
|
|
|||
|
|
@ -390,10 +390,7 @@ github.com/getsentry/sentry-go v0.7.0/go.mod h1:pLFpD2Y5RHIKF9Bw3KH6/68DeN2K/XBJ
|
|||
github.com/getsentry/sentry-go v0.10.0/go.mod h1:kELm/9iCblqUYh+ZRML7PNdCvEuw24wBvJPYyi86cws=
|
||||
github.com/getsentry/sentry-go v0.13.0/go.mod h1:EOsfu5ZdvKPfeHYV6pTVQnsjfp30+XA7//UooKNumH0=
|
||||
github.com/ghodss/yaml v1.0.0/go.mod h1:4dBDuWmgqj2HViK6kFavaiC9ZROes6MMH2rRYeMEF04=
|
||||
github.com/gin-contrib/sse v0.0.0-20190301062529-5545eab6dad3/go.mod h1:VJ0WA2NBN22VlZ2dKZQPAPnyWw5XTlK1KymzLKsr59s=
|
||||
github.com/gin-contrib/sse v0.1.0/go.mod h1:RHrZQHXnP2xjPF+u1gW/2HnVO7nvIa9PG3Gm+fLHvGI=
|
||||
github.com/gin-gonic/gin v1.4.0/go.mod h1:OW2EZn3DO8Ln9oIKOvM++LBO+5UPHJJDH72/q/3rZdM=
|
||||
github.com/gin-gonic/gin v1.6.3/go.mod h1:75u5sXoLsGZoRN5Sgbi1eraJ4GU3++wFwWzhwvtwp4M=
|
||||
github.com/gin-gonic/gin v1.7.3/go.mod h1:jD2toBW3GZUr5UMcdrwQA10I7RuaFOl/SGeDjXkfUtY=
|
||||
github.com/gin-gonic/gin v1.7.7/go.mod h1:axIBovoeJpVj8S3BwE0uPMTeReE4+AfFtqpqaZ1qq1U=
|
||||
github.com/git-lfs/git-lfs v1.5.1-0.20210304194248-2e1d981afbe3/go.mod h1:8Xqs4mqL7o6xEnaXckIgELARTeK7RYtm3pBab7S79Js=
|
||||
|
|
@ -433,7 +430,6 @@ github.com/go-ole/go-ole v1.2.4/go.mod h1:XCwSNxSkXRo4vlyPy93sltvi/qJq0jqQhjqQNI
|
|||
github.com/go-playground/assert/v2 v2.0.1/go.mod h1:VDjEfimB/XKnb+ZQfWdccd7VUvScMdVu0Titje2rxJ4=
|
||||
github.com/go-playground/locales v0.13.0/go.mod h1:taPMhCMXrRLJO55olJkUXHZBHCxTMfnGwq/HNwmWNS8=
|
||||
github.com/go-playground/universal-translator v0.17.0/go.mod h1:UkSxE5sNxxRwHyU+Scu5vgOQjsIJAF8j9muTVoKLVtA=
|
||||
github.com/go-playground/validator/v10 v10.2.0/go.mod h1:uOYAAleCW8F/7oMFd6aG0GOhaH6EGOAJShg8Id5JGkI=
|
||||
github.com/go-playground/validator/v10 v10.4.1/go.mod h1:nlOn6nFhuKACm19sB/8EGNn9GlaMV7XkbRSipzJ0Ii4=
|
||||
github.com/go-sql-driver/mysql v1.4.0/go.mod h1:zAC/RDZ24gD3HViQzih4MyKcchzm+sOG5ZlKdlhCg5w=
|
||||
github.com/go-sql-driver/mysql v1.4.1/go.mod h1:zAC/RDZ24gD3HViQzih4MyKcchzm+sOG5ZlKdlhCg5w=
|
||||
|
|
@ -835,7 +831,6 @@ github.com/matttproud/golang_protobuf_extensions v1.0.1/go.mod h1:D8He9yQNgCq6Z5
|
|||
github.com/mediocregopher/mediocre-go-lib v0.0.0-20181029021733-cb65787f37ed/go.mod h1:dSsfyI2zABAdhcbvkXqgxOxrCsbYeHCPgrZkku60dSg=
|
||||
github.com/mediocregopher/radix/v3 v3.3.0/go.mod h1:EmfVyvspXz1uZEyPBMyGK+kjWiKQGvsUt6O3Pj+LDCQ=
|
||||
github.com/mediocregopher/radix/v3 v3.4.2/go.mod h1:8FL3F6UQRXHXIBSPUs5h0RybMF8i4n7wVopoX3x7Bv8=
|
||||
github.com/microcosm-cc/bluemonday v1.0.2/go.mod h1:iVP4YcDBq+n/5fb23BhYFvIMq/leAFZyRl6bYmGDlGc=
|
||||
github.com/miekg/dns v1.0.14/go.mod h1:W1PPwlIAgtquWBMBEV9nkV9Cazfe8ScdGz/Lj7v3Nrg=
|
||||
github.com/mikesmitty/edkey v0.0.0-20170222072505-3356ea4e686a/go.mod h1:v8eSC2SMp9/7FTKUncp7fH9IwPfw+ysMObcEz5FWheQ=
|
||||
github.com/mitchellh/cli v1.0.0/go.mod h1:hNIlj7HEI86fIcpObd7a0FcrxTWetlwJDGcceTlRvqc=
|
||||
|
|
@ -1079,7 +1074,6 @@ github.com/uber/jaeger-client-go v2.29.1+incompatible/go.mod h1:WVhlPFC8FDjOFMMW
|
|||
github.com/uber/jaeger-lib v1.5.0/go.mod h1:ComeNDZlWwrWnDv8aPp0Ba6+uUTzImX/AauajbLI56U=
|
||||
github.com/uber/jaeger-lib v2.4.1+incompatible h1:td4jdvLcExb4cBISKIpHuGoVXh+dVKhn2Um6rjCsSsg=
|
||||
github.com/uber/jaeger-lib v2.4.1+incompatible/go.mod h1:ComeNDZlWwrWnDv8aPp0Ba6+uUTzImX/AauajbLI56U=
|
||||
github.com/ugorji/go v1.1.4/go.mod h1:uQMGLiO92mf5W77hV/PUCpI3pbzQx3CRekS0kk+RGrc=
|
||||
github.com/ugorji/go v1.1.7/go.mod h1:kZn38zHttfInRq0xu/PH0az30d+z6vm202qpg1oXVMw=
|
||||
github.com/ugorji/go/codec v0.0.0-20181204163529-d75b2dcb6bc8/go.mod h1:VFNgLljTbGfSG7qAOspJ7OScBnGdDN/yBr0sguwnwf0=
|
||||
github.com/ugorji/go/codec v1.1.7/go.mod h1:Ax+UKWsSmolVDwsd+7N3ZtXu+yMGCf907BLYF3GoBXY=
|
||||
|
|
@ -1802,8 +1796,6 @@ gopkg.in/errgo.v2 v2.1.0/go.mod h1:hNsd1EY+bozCKY1Ytp96fpM3vjJbqLJn88ws8XvfDNI=
|
|||
gopkg.in/fsnotify.v1 v1.4.7 h1:xOHLXZwVvI9hhs+cLKq5+I5onOuwQLhQwiu63xxlHs4=
|
||||
gopkg.in/fsnotify.v1 v1.4.7/go.mod h1:Tz8NjZHkW78fSQdbUxIjBTcgA1z1m8ZHf0WmKUhAMys=
|
||||
gopkg.in/gcfg.v1 v1.2.3/go.mod h1:yesOnuUOFQAhST5vPY4nbZsb/huCgGGXlipJsBn0b3o=
|
||||
gopkg.in/go-playground/assert.v1 v1.2.1/go.mod h1:9RXL0bg/zibRAgZUYszZSwO/z8Y/a8bDuhia5mkpMnE=
|
||||
gopkg.in/go-playground/validator.v8 v8.18.2/go.mod h1:RX2a/7Ha8BgOhfk7j780h4/u/RRjR0eouCJSH80/M2Y=
|
||||
gopkg.in/gorp.v1 v1.7.2/go.mod h1:Wo3h+DBQZIxATwftsglhdD/62zRFPhGhTiu5jUJmCaw=
|
||||
gopkg.in/inconshreveable/log15.v2 v2.0.0-20180818164646-67afb5ed74ec/go.mod h1:aPpfJ7XW+gOuirDoZ8gHhLh3kZ1B08FtV2bbmy7Jv3s=
|
||||
gopkg.in/ini.v1 v1.51.1/go.mod h1:pNLf8WUiyNEtQjuu5G5vTm06TEv9tsIgeAvK8hOrP4k=
|
||||
|
|
@ -1841,8 +1833,8 @@ honnef.co/go/tools v0.0.0-20190523083050-ea95bdfd59fc/go.mod h1:rf3lG4BRIbNafJWh
|
|||
honnef.co/go/tools v0.0.1-2019.2.3/go.mod h1:a3bituU0lyd329TUQxRnasdCoJDkEUEAqEt0JzvZhAg=
|
||||
honnef.co/go/tools v0.0.1-2020.1.3/go.mod h1:X/FiERA/W4tHapMX5mGpAtMSVEeEUOyHaw9vFzvIQ3k=
|
||||
honnef.co/go/tools v0.0.1-2020.1.4/go.mod h1:X/FiERA/W4tHapMX5mGpAtMSVEeEUOyHaw9vFzvIQ3k=
|
||||
honnef.co/go/tools v0.3.2 h1:ytYb4rOqyp1TSa2EPvNVwtPQJctSELKaMyLfqNP4+34=
|
||||
honnef.co/go/tools v0.3.2/go.mod h1:jzwdWgg7Jdq75wlfblQxO4neNaFFSvgc1tD5Wv8U0Yw=
|
||||
honnef.co/go/tools v0.3.3 h1:oDx7VAwstgpYpb3wv0oxiZlxY+foCpRAwY7Vk6XpAgA=
|
||||
honnef.co/go/tools v0.3.3/go.mod h1:jzwdWgg7Jdq75wlfblQxO4neNaFFSvgc1tD5Wv8U0Yw=
|
||||
nhooyr.io/websocket v1.8.6/go.mod h1:B70DZP8IakI65RVQ51MsWP/8jndNma26DVA/nFSCgW0=
|
||||
nhooyr.io/websocket v1.8.7/go.mod h1:B70DZP8IakI65RVQ51MsWP/8jndNma26DVA/nFSCgW0=
|
||||
rsc.io/binaryregexp v0.2.0/go.mod h1:qTv7/COck+e2FymRvadv62gMdZztPaShugOCi3I+8D8=
|
||||
|
|
|
|||
Loading…
Reference in New Issue