diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-09-08 03:09:20 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-09-08 03:09:20 +0300 |
commit | e85e128aa0ed5539e3a70a908c6ab0ff6b59a365 (patch) | |
tree | 6c2a17f13eaca8d529abcba56ebe207b5c38589f | |
parent | 4e9110c3c5b218bb8e1b183b9570426d9bbb0670 (diff) |
Add latest changes from gitlab-org/gitlab@master
-rw-r--r-- | doc/update/versions/gitlab_14_changes.md | 17 | ||||
-rw-r--r-- | locale/gitlab.pot | 11 | ||||
-rw-r--r-- | package.json | 2 | ||||
-rw-r--r-- | spec/requests/content_security_policy_spec.rb | 3 | ||||
-rw-r--r-- | yarn.lock | 8 |
5 files changed, 28 insertions, 13 deletions
diff --git a/doc/update/versions/gitlab_14_changes.md b/doc/update/versions/gitlab_14_changes.md index e093abf46de..0e59ba3be91 100644 --- a/doc/update/versions/gitlab_14_changes.md +++ b/doc/update/versions/gitlab_14_changes.md @@ -240,10 +240,6 @@ that may remain stuck permanently in a **pending** state. ## 14.5.0 -- When `make` is run, Gitaly builds are now created in `_build/bin` and no longer in the root directory of the source directory. If you -are using a self-compiled installation, update paths to these binaries in your [systemd unit files](../upgrading_from_source.md#configure-systemd-units) -or [init scripts](../upgrading_from_source.md#configure-sysv-init-script) by [following the documentation](../upgrading_from_source.md). - - Connections between Workhorse and Gitaly use the Gitaly `backchannel` protocol by default. If you deployed a gRPC proxy between Workhorse and Gitaly, Workhorse can no longer connect. As a workaround, [disable the temporary `workhorse_use_sidechannel`](../../administration/feature_flags.md#enable-or-disable-the-feature) feature flag. If you need a proxy between Workhorse and Gitaly, use a TCP proxy. If you have feedback about this change, go to [this issue](https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/1301). @@ -303,6 +299,12 @@ or [init scripts](../upgrading_from_source.md#configure-sysv-init-script) by [fo sudo -u git -H editor config/cable.yml ``` +### Self-compiled installations + +- When `make` is run, Gitaly builds are now created in `_build/bin` and no longer in the root directory of the source directory. If you +are using a self-compiled installation, update paths to these binaries in your [systemd unit files](../upgrading_from_source.md#configure-systemd-units) +or [init scripts](../upgrading_from_source.md#configure-sysv-init-script) by [following the documentation](../upgrading_from_source.md). + ### Geo installations **(PREMIUM SELF)** - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) @@ -401,8 +403,6 @@ that may remain stuck permanently in a **pending** state when the instance lacks - [Instances running 14.0.0 - 14.0.4 should not upgrade directly to GitLab 14.2 or later](#upgrading-to-later-14y-releases). - Ensure [batched background migrations finish](../background_migrations.md#batched-background-migrations) before upgrading to 14.3.Z from earlier GitLab 14 releases. -- Ruby 2.7.4 is required. Refer to [the Ruby installation instructions](../../install/installation.md#2-ruby) -for how to proceed. - GitLab 14.3.0 contains post-deployment migrations to [address Primary Key overflow risk for tables with an integer PK](https://gitlab.com/groups/gitlab-org/-/epics/4785) for the tables listed below: - [`ci_builds.id`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70245) @@ -543,6 +543,11 @@ for how to proceed. - If you encounter the error, `I18n::InvalidLocale: :en is not a valid locale`, when starting the application, follow the [patching](https://about.gitlab.com/handbook/support/workflows/patching_an_instance.html) process. Use [122978](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/122978) as the `mr_iid`. +### Self-compiled installations + +- Ruby 2.7.4 is required. Refer to [the Ruby installation instructions](../../install/installation.md#2-ruby) + for how to proceed. + ### Geo installations **(PREMIUM SELF)** - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) diff --git a/locale/gitlab.pot b/locale/gitlab.pot index 45e817d9a0f..0c89b1f1e1a 100644 --- a/locale/gitlab.pot +++ b/locale/gitlab.pot @@ -41342,7 +41342,7 @@ msgstr "" msgid "ScanResultPolicy|When %{scanType} in an open merge request targeting %{branches} %{branchExceptions} and the licenses match all of the following criteria:" msgstr "" -msgid "ScanResultPolicy|When %{scanType} in an open that targets %{branches} with %{commitType}" +msgid "ScanResultPolicy|When %{scanType} in an open that targets %{branches} %{branchExceptions} with %{commitType}" msgstr "" msgid "ScanResultPolicy|When %{scanners} find scanner specified conditions in an open merge request targeting the %{branches} %{branchExceptions} and match %{boldDescription} of the following criteria" @@ -41925,6 +41925,12 @@ msgstr "" msgid "SecurityOrchestration| and all the following apply:" msgstr "" +msgid "SecurityOrchestration| for any commits" +msgstr "" + +msgid "SecurityOrchestration| for unsigned commits" +msgstr "" + msgid "SecurityOrchestration| or " msgstr "" @@ -42084,6 +42090,9 @@ msgstr "" msgid "SecurityOrchestration|Failed to load images." msgstr "" +msgid "SecurityOrchestration|For any merge request on %{branches}%{commitType}%{branchExceptionsString}" +msgstr "" + msgid "SecurityOrchestration|For large groups, there may be a significant delay in applying policy changes to pre-existing merge requests. Policy changes typically apply almost immediately for newly created merge requests." msgstr "" diff --git a/package.json b/package.json index 8c07963c2fa..a8719375f5c 100644 --- a/package.json +++ b/package.json @@ -126,7 +126,7 @@ "clipboard": "^2.0.8", "compression-webpack-plugin": "^5.0.2", "copy-webpack-plugin": "^6.4.1", - "core-js": "^3.32.1", + "core-js": "^3.32.2", "cron-validator": "^1.1.1", "cronstrue": "^1.122.0", "cropper": "^2.3.0", diff --git a/spec/requests/content_security_policy_spec.rb b/spec/requests/content_security_policy_spec.rb index dcd55b1eeee..3ce7e33d88a 100644 --- a/spec/requests/content_security_policy_spec.rb +++ b/spec/requests/content_security_policy_spec.rb @@ -48,7 +48,8 @@ RSpec.describe 'Content Security Policy', feature_category: :application_instrum it_behaves_like 'snowplow is not in the CSP' end - context 'when vite enabled during development' do + context 'when vite enabled during development', + quarantine: 'https://gitlab.com/gitlab-org/gitlab/-/issues/424334' do before do stub_rails_env('development') stub_feature_flags(vite: true) diff --git a/yarn.lock b/yarn.lock index 736a17aca67..aa10a04accf 100644 --- a/yarn.lock +++ b/yarn.lock @@ -4511,10 +4511,10 @@ core-js-pure@^3.0.0: resolved "https://registry.yarnpkg.com/core-js-pure/-/core-js-pure-3.6.5.tgz#c79e75f5e38dbc85a662d91eea52b8256d53b813" integrity sha512-lacdXOimsiD0QyNf9BC/mxivNJ/ybBGJXQFKzRekp1WTHoVUWsUHEn+2T8GJAzzIhyOuXA+gOxCVN3l+5PLPUA== -core-js@^3.29.1, core-js@^3.32.1, core-js@^3.6.5: - version "3.32.1" - resolved "https://registry.yarnpkg.com/core-js/-/core-js-3.32.1.tgz#a7d8736a3ed9dd05940c3c4ff32c591bb735be77" - integrity sha512-lqufgNn9NLnESg5mQeYsxQP5w7wrViSj0jr/kv6ECQiByzQkrn1MKvV0L3acttpDqfQrHLwr2KCMgX5b8X+lyQ== +core-js@^3.29.1, core-js@^3.32.2, core-js@^3.6.5: + version "3.32.2" + resolved "https://registry.yarnpkg.com/core-js/-/core-js-3.32.2.tgz#172fb5949ef468f93b4be7841af6ab1f21992db7" + integrity sha512-pxXSw1mYZPDGvTQqEc5vgIb83jGQKFGYWY76z4a7weZXUolw3G+OvpZqSRcfYOoOVUQJYEPsWeQK8pKEnUtWxQ== core-util-is@~1.0.0: version "1.0.3" |