root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2024-03-18 12:07:07 +00:00
parent e5ebbac8ba
commit a9eab24098
24 changed files with 38 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/administration/geo/replication/troubleshooting.md
View File

@ -364,9 +364,9 @@ The Ruby gem which performs the check is hard coded with `pool.ntp.org` as its r
This issue occurs when the hostname `pool.ntp.org` resolves to a server which does not provide a time service.
In this case, in GitLab 15.7 and newer, [specify a custom NTP server using environment variables](#health-check-rake-task).
In this case, in GitLab 15.7 and later, [specify a custom NTP server using environment variables](#health-check-rake-task).
In GitLab 15.6 and older, use one of the following workarounds:
In GitLab 15.6 and earlier, use one of the following workarounds:
- Add entries in `/etc/hosts` for `pool.ntp.org` to direct the request to valid local time servers.
This fixes the long timeout and the timeout error.
@ -776,7 +776,7 @@ The following configuration example:
- Ignores five common check failures.
[The Gitaly documentation has more details](../../gitaly/consistency_checks.md)
about other Git check failures and older versions of GitLab.
about other Git check failures and earlier versions of GitLab.
```ruby
gitaly['configuration'] = {

2
doc/administration/integration/plantuml.md
View File

@ -330,7 +330,7 @@ After configuring your local PlantUML server, you're ready to enable the PlantUM
Depending on your PlantUML and GitLab version numbers, you may also need to take
these steps:
- For PlantUML servers running v1.2020.9 and above, such as [plantuml.com](https://plantuml.com),
- For PlantUML servers running v1.2020.9 and later, such as [plantuml.com](https://plantuml.com),
you must set the `PLANTUML_ENCODING` environment variable to enable the `deflate`
compression. In Linux package installations, you can set this value in `/etc/gitlab/gitlab.rb` with
this command:

4
doc/api/groups.md
View File

@ -1728,7 +1728,7 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** Self-managed
Adds an LDAP group link using a CN or filter. Adding a group link by filter is only supported in the Premium tier and above.
Adds an LDAP group link using a CN or filter. Adding a group link by filter is only supported in the Premium and Ultimate tier.
```plaintext
POST /groups/:id/ldap_group_links
@ -1780,7 +1780,7 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** Self-managed
Deletes an LDAP group link using a CN or filter. Deleting by filter is only supported in the Premium tier and above.
Deletes an LDAP group link using a CN or filter. Deleting by filter is only supported in the Premium and Ultimate tier.
```plaintext
DELETE /groups/:id/ldap_group_links

2
doc/architecture/blueprints/capacity_planning/index.md
View File

@ -1,5 +1,5 @@
---
status: proposed
status: implemented
creation-date: "2023-09-11"
authors: [ "@abrandl" ]
coach: "@andrewn"

2
doc/architecture/blueprints/cells/iterations/cells-1.0.md
View File

@ -24,7 +24,7 @@ contribution model in a cellular architecture.
A Cells 1.0 is meant to target enterprise customers that have the following expectations:
1. They want to use our multi-tenant SaaS solution (GitLab.com) to serve their Organization.
1. They accept that they may receive updates later than the rest of GitLab.com.
1. They accept that they may receive updates later than the rest of GitLab.com. Note that when GitLab does a security release, the Delivery team makes sure that production (every cell) runs the security release version before making the release public. This does not mean that outside of a security release, all the cells run the same version of GitLab. See [this private discussion](https://gitlab.com/gitlab-com/gl-security/appsec/threat-models/-/issues/45#note_1794904358) for more information.
1. They want to use an environment with higher degree of isolation to rest of the system.
1. They want to control all users that contribute to their Organization.
1. Their groups and projects are meant to be private.

2
doc/ci/docker/using_kaniko.md
View File

@ -10,8 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/45512) in GitLab 11.2. Requires GitLab Runner 11.2 and above.
[kaniko](https://github.com/GoogleContainerTools/kaniko) is a tool to build
container images from a Dockerfile, inside a container or Kubernetes cluster.

4
doc/ci/testing/metrics_reports.md
View File

@ -10,8 +10,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9788) in GitLab 11.10. Requires GitLab Runner 11.10 and above.
GitLab provides a lot of great reporting tools for things like [merge requests](../../user/project/merge_requests/index.md) - [Unit test reports](unit_test_reports.md), [code quality](code_quality.md), and performance tests. While JUnit is a great open framework for tests that "pass" or "fail", it is also important to see other types of metrics from a given change.
You can configure your job to use custom Metrics Reports, and GitLab displays a report on the merge request so that it's easier and faster to identify changes without having to check the entire log.
@ -67,6 +65,6 @@ renders in the merge request widget as:
You can see `Metrics reports did not change` when trying to view metrics reports in merge requests. Reasons for this are:
- The target branch for the merge request doesn't have a baseline metrics report for comparison.
- You don't have GitLab license at the Premium tier or above.
- You don't have a paid subscription.
There is [an issue open](https://gitlab.com/gitlab-org/gitlab/-/issues/343065) to improve this message.

3
doc/ci/testing/unit_test_reports.md
View File

@ -10,9 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/45318) in GitLab 11.2. Requires GitLab Runner 11.2 and above.
> - [Renamed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/39737) from JUnit test reports to Unit test reports in GitLab 13.4.
It is very common that a [CI/CD pipeline](../pipelines/index.md) contains a
test job that verifies your code.
If the tests fail, the pipeline fails and users get notified. The person that

2
doc/ci/variables/index.md
View File

@ -363,7 +363,7 @@ kubectl config set-cluster e2e --server="$KUBE_URL" --certificate-authority="$KU
WARNING:
Be careful when assigning the value of a file variable to another variable in GitLab 15.6 or older.
The other variable takes the content of the file as its value, **not** the path to the file.
In GitLab 15.7 and newer, this behavior [was fixed](https://gitlab.com/gitlab-org/gitlab/-/issues/29407) and the other variable now takes the path to the file as the value.
In GitLab 15.7 and later, this behavior [was fixed](https://gitlab.com/gitlab-org/gitlab/-/issues/29407) and the other variable now takes the path to the file as the value.
#### Use a `.gitlab-ci.yml` variable as a file type variable

6
doc/ci/yaml/index.md
View File

@ -2970,11 +2970,11 @@ This example creates four paths of execution:
can refer to jobs in the same stage as the job you are configuring. This feature is
enabled on GitLab.com and ready for production use. On self-managed [GitLab 14.2 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/30632)
this feature is available by default.
- In GitLab 14.0 and older, you can only refer to jobs in earlier stages. Stages must be
- In GitLab 14.0 and earlier, you can only refer to jobs in earlier stages. Stages must be
explicitly defined for all jobs that use the `needs` keyword, or are referenced
in a job's `needs` section.
- In GitLab 13.9 and older, if `needs` refers to a job that might not be added to
a pipeline because of `only`, `except`, or `rules`, the pipeline might fail to create. In GitLab 13.10 and later, use the [`needs:optional`](#needsoptional) keyword to resolve a failed pipeline creation.
- If `needs` refers to a job that might not be added to
a pipeline because of `only`, `except`, or `rules`, the pipeline might fail to create. Use the [`needs:optional`](#needsoptional) keyword to resolve a failed pipeline creation.
- If a pipeline has jobs with `needs: []` and jobs in the [`.pre`](#stage-pre) stage, they will
all start as soon as the pipeline is created. Jobs with `needs: []` start immediately,
and jobs in the `.pre` stage also start immediately.

2
doc/development/packages/harbor_registry_development.md
View File

@ -99,7 +99,7 @@ sequenceDiagram
## Policy
The`read_harbor_registry` policy for groups and projects is used to control whether users have access to Harbor registry.
This policy is enabled for every user with the Reporter role and above.
This policy is enabled for every user with at least the Reporter role.
## Frontend Development

2
doc/development/secure_coding_guidelines.md
View File

@ -632,7 +632,7 @@ This outputs `1` followed by the content of `/etc/passwd`.
### TLS minimum recommended version
As we have [moved away from supporting TLS 1.0 and 1.1](https://about.gitlab.com/blog/2018/10/15/gitlab-to-deprecate-older-tls/), you must use TLS 1.2 and above.
As we have [moved away from supporting TLS 1.0 and 1.1](https://about.gitlab.com/blog/2018/10/15/gitlab-to-deprecate-older-tls/), you must use TLS 1.2 and later.
#### Ciphers

2
doc/integration/saml.md
View File

@ -404,7 +404,7 @@ You can configure GitLab to use multiple SAML IdPs if:
- Each provider has a unique name set that matches a name set in `args`. At least
one provider must have the name `saml` to mitigate a
[known issue](https://gitlab.com/gitlab-org/gitlab/-/issues/366450) in GitLab
14.6 and newer.
14.6 and later.
- The providers' names are used:
- In OmniAuth configuration for properties based on the provider name. For example,
`allowBypassTwoFactor`, `allowSingleSignOn`, and `syncProfileFromProvider`.

2
doc/topics/autodevops/upgrading_auto_deploy_dependencies.md
View File

@ -75,7 +75,7 @@ If your Auto DevOps project has an active environment deployed with the v1 `auto
#### Kubernetes 1.16+
The v2 auto-deploy-image drops support for Kubernetes 1.15 and lower. If you need to upgrade your
The v2 auto-deploy-image drops support for Kubernetes 1.15 and earlier. If you need to upgrade your
Kubernetes cluster, follow your cloud provider's instructions. Here's
[an example on GKE](https://cloud.google.com/kubernetes-engine/docs/how-to/upgrading-a-cluster).

2
doc/user/application_security/dast/browser/checks/16.2.md
View File

@ -24,7 +24,7 @@ NGINX:
For NGINX based websites, set the `server_tokens` configuration value to `off` in the `nginx.conf` file.
IIS:
For IIS based websites version 10 and above you can use the `removeServerHeader` element to the `requestFiltering`
For IIS-based websites version 10 and later, you can use the `removeServerHeader` element to the `requestFiltering`
section of the `Web.config` file.
For all other server types, please consult your product's documentation on how to redact the version information from

2
doc/user/application_security/dast/browser/checks/548.1.md
View File

@ -25,7 +25,7 @@ For NGINX based websites, ensure all `location` definitions have the `autoindex
`nginx.conf` file.
IIS:
For IIS based websites version 7.0 and above you can use the `<directoryBrowse enabled="false" />` element
For IIS-based websites version 7.0 and later, you can use the `<directoryBrowse enabled="false" />` element
in the `applicationHost.config` or `Web.config` files.
For all other server types, please consult your product's documentation on how to disable directory

5
doc/user/application_security/dependency_scanning/index.md
View File

@ -281,10 +281,7 @@ The following languages and dependency managers are supported:
<li>
<a id="notes-regarding-supported-languages-and-package-managers-7"></a>
<p>
<ul>
<li>Support for <a href="https://www.scala-sbt.org/">sbt</a> 1.3 and above was added in GitLab 13.9.</li>
<li>Support for sbt 1.0.x was <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/415835">deprecated in GitLab 16.8</a>.</li>
</ul>
Support for sbt 1.0.x was <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/415835">deprecated</a> in GitLab 16.8.
</p>
</li>
<li>

10
doc/user/group/value_stream_analytics/index.md
View File

@ -544,11 +544,11 @@ The chart shows data for the last 500 workflow items.
Access permissions for value stream analytics depend on the project type.
| Project type | Permissions |
|--------------|----------------------------------------|
| Public | Anyone can access. |
| Internal | Any authenticated user can access. |
| Private | Any member Guest and above can access. |
| Project type | Permissions |
|--------------|---------------------------------------------------|
| Public | Anyone can access. |
| Internal | Any authenticated user can access. |
| Private | Any user with at least the Guest role can access. |
## Troubleshooting

2
doc/user/permissions.md
View File

@ -178,7 +178,7 @@ The following table lists project permissions available for each role:
| [Projects](project/index.md):<br>Edit project badges | | | | ✓ | ✓ | |
| [Projects](project/index.md):<br>Edit project settings | | | | ✓ | ✓ | |
| [Projects](project/index.md):<br>[Export project](project/settings/import_export.md) | | | | ✓ | ✓ | |
| [Projects](project/index.md):<br>Manage [project access tokens](project/settings/project_access_tokens.md) | | | | ✓ | ✓ | Project access tokens are supported for self-managed instances on Free and above. They are also supported on GitLab.com Premium and above (excluding [trial licenses](https://about.gitlab.com/free-trial/)). |
| [Projects](project/index.md):<br>Manage [project access tokens](project/settings/project_access_tokens.md) | | | | ✓ | ✓ | For self-managed GitLab, project access tokens are available in all tiers. For GitLab.com, project access tokens are supported in the Premium and Ultimate tier (excluding [trial licenses](https://about.gitlab.com/free-trial/)). |
| [Projects](project/index.md):<br>Manage [Project Operations](../operations/index.md) | | | | ✓ | ✓ | |
| [Projects](project/index.md):<br>Rename project | | | | ✓ | ✓ | |
| [Projects](project/index.md):<br>Share (invite) projects with groups | | | | ✓ | ✓ | When [Share Group Lock](group/access_and_permissions.md#prevent-a-project-from-being-shared-with-groups) is enabled the project can't be shared with other groups. It does not affect group with group sharing. |

6
doc/user/project/issue_board.md
View File

@ -57,7 +57,11 @@ the issue board feature.
> - Multiple issue boards per project [moved](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/53811) to GitLab Free in 12.1.
> - Multiple issue boards per group are available in GitLab Premium.
Multiple issue boards allow for more than one issue board for a given project in the Free tier or group in the Premium and Ultimate tier.
Multiple issue boards allow for more than one issue board for:
- A project in all tiers
- A group in the Premium and Ultimate tier
This is great for large projects with more than one team or when a repository hosts the code of multiple products.
Using the search box at the top of the menu, you can filter the listed boards.

2
package.json
View File

@ -59,7 +59,7 @@
"@gitlab/cluster-client": "^2.1.0",
"@gitlab/favicon-overlay": "2.0.0",
"@gitlab/fonts": "^1.3.0",
"@gitlab/svgs": "3.90.0",
"@gitlab/svgs": "3.91.0",
"@gitlab/ui": "78.1.1",
"@gitlab/visual-review-tools": "1.7.3",
"@gitlab/web-ide": "^0.0.1-dev-20240226152102",

2
qa/gdk/Dockerfile.gdk
View File

@ -1,4 +1,4 @@
ARG GDK_SHA=6a9828e36b3f2d66c3f4b5f7cddf1f768d38bbf0
ARG GDK_SHA=e8a2f3c30d3031c5574957efbaa917bacdeb3f1a
# Use tag prefix when running on 'stable' branch to make sure 'protected' image is used which is not deleted by registry cleanup
ARG GDK_BASE_TAG_PREFIX

2
spec/finders/repositories/branch_names_finder_spec.rb
View File

@ -2,7 +2,7 @@
require 'spec_helper'
RSpec.describe Repositories::BranchNamesFinder do
RSpec.describe Repositories::BranchNamesFinder, feature_category: :source_code_management do
let(:project) { create(:project, :repository) }
describe '#execute' do

8
yarn.lock
View File

@ -1321,10 +1321,10 @@
stylelint-declaration-strict-value "1.10.4"
stylelint-scss "6.0.0"
"@gitlab/svgs@3.90.0":
version "3.90.0"
resolved "https://registry.yarnpkg.com/@gitlab/svgs/-/svgs-3.90.0.tgz#6f42ac4fac96b3f4e732f29c8815fb8bbcac10dd"
integrity sha512-Y4iwYZ7mtWPBob7SB9tFRqLmGJyMRTXVY12yCd+7gkD5o6GJAyUriV0eVeWtNSZHkPRfT91226a3nbCmBuu7ew==
"@gitlab/svgs@3.91.0":
version "3.91.0"
resolved "https://registry.yarnpkg.com/@gitlab/svgs/-/svgs-3.91.0.tgz#e99bc5467318cc8c156e02c574f5e65941b767f0"
integrity sha512-ozINZKyUlu5UQlP++9SntWQDqsgDSYawTPw+qhKQTdyn4Ut2NMsvSFyR5J2pax5IWu+SpLrn3WuPgNybK+4LqQ==
"@gitlab/ui@78.1.1":
version "78.1.1"