Add latest changes from gitlab-org/gitlab@master

9 files changed, 112 insertions, 158 deletions

diff --git a/doc/.vale/gitlab/Uppercase.yml b/doc/.vale/gitlab/Uppercase.yml
index f53e1c72dcb..039ad7c5f03 100644
--- a/doc/.vale/gitlab/Uppercase.yml
+++ b/doc/.vale/gitlab/Uppercase.yml
@@ -39,6 +39,7 @@ exceptions:
   - CORE
   - CORS
   - CPU
+  - CRAN
   - CRIME
   - CRM
   - CRUD
@@ -188,6 +189,7 @@ exceptions:
   - SAST
   - SATA
   - SBOM
+  - SBT
   - SCIM
   - SCM
   - SCP
diff --git a/doc/.vale/gitlab/spelling-exceptions.txt b/doc/.vale/gitlab/spelling-exceptions.txt
index fa702cedc6f..81b21f026f4 100644
--- a/doc/.vale/gitlab/spelling-exceptions.txt
+++ b/doc/.vale/gitlab/spelling-exceptions.txt
@@ -196,6 +196,7 @@ corpuses
 Coursier
 CPU
 CPUs
+CRAN
 cron
 crond
 cronjob
@@ -826,6 +827,7 @@ Salesforce
 sandboxing
 sanitization
 SBOMs
+SBT
 sbt
 scalers
 scatterplot
diff --git a/doc/administration/object_storage.md b/doc/administration/object_storage.md
index 8b7f49d77d9..b304aaa3adc 100644
--- a/doc/administration/object_storage.md
+++ b/doc/administration/object_storage.md
@@ -482,7 +482,7 @@ To migrate existing local data to object storage see the following guides:
 - [LFS objects](lfs/index.md#migrating-to-object-storage)
 - [Uploads](raketasks/uploads/migrate.md#migrate-to-object-storage)
 - [Merge request diffs](merge_request_diffs.md#using-object-storage)
-- [Packages](packages/index.md#migrating-local-packages-to-object-storage) (optional feature)
+- [Packages](packages/index.md#migrate-local-packages-to-object-storage) (optional feature)
 - [Dependency Proxy](packages/dependency_proxy.md#migrate-local-dependency-proxy-blobs-and-manifests-to-object-storage)
 - [Terraform state files](terraform_state.md#migrate-to-object-storage)
 - [Pages content](pages/index.md#migrate-pages-deployments-to-object-storage)
@@ -537,7 +537,7 @@ supported by consolidated configuration form, refer to the following guides:
 | [Container Registry](packages/container_registry.md#use-object-storage) (optional feature) | **{dotted-circle}** No |
 | [Merge request diffs](merge_request_diffs.md#using-object-storage) | **{check-circle}** Yes |
 | [Mattermost](https://docs.mattermost.com/administration/config-settings.html#file-storage)| **{dotted-circle}** No |
-| [Packages](packages/index.md#using-object-storage) (optional feature) | **{check-circle}** Yes |
+| [Packages](packages/index.md#use-object-storage) (optional feature) | **{check-circle}** Yes |
 | [Dependency Proxy](packages/dependency_proxy.md#using-object-storage) (optional feature) | **{check-circle}** Yes |
 | [Autoscale runner caching](https://docs.gitlab.com/runner/configuration/autoscale.html#distributed-runners-caching) (optional for improved performance) | **{dotted-circle}** No |
 | [Terraform state files](terraform_state.md#using-object-storage) | **{check-circle}** Yes |
@@ -648,10 +648,6 @@ if this access is not in place include:
 
   See [the LFS documentation](lfs/index.md#error-viewing-a-pdf-file) for more details.
 
-Getting a `403 Forbidden` response is specifically called out on the
-[package repository documentation](packages/index.md#using-object-storage)
-as a side effect of how some build tools work.
-
 Additionally for a short time period users could share pre-signed, time-limited object storage URLs
 with others without authentication. Also bandwidth charges may be incurred
 between the object storage provider and the client.
diff --git a/doc/administration/packages/index.md b/doc/administration/packages/index.md
index 74d835eb744..6e53d77109f 100644
--- a/doc/administration/packages/index.md
+++ b/doc/administration/packages/index.md
@@ -6,11 +6,13 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # GitLab Package Registry administration **(FREE SELF)**
 
-GitLab Packages allows organizations to use GitLab as a private repository
-for a variety of common package managers. Users are able to build and publish
-packages, which can be easily consumed as a dependency in downstream projects.
+To use GitLab as a private repository for a variety of common package managers, use the Package Registry.
+You can build and publish
+packages, which can be consumed as dependencies in downstream projects.
 
-The Packages feature allows GitLab to act as a repository and supports the following formats:
+## Supported formats
+
+The Package Registry supports the following formats:
 
 | Package type                                                      | GitLab version |
 |-------------------------------------------------------------------|----------------|
@@ -49,204 +51,155 @@ guides you through the process.
 
 <!-- vale gitlab.Spelling = YES -->
 
-## Enabling the Packages feature
+## Rate limits
 
-NOTE:
-After the Packages feature is enabled, the repositories are available
-for all new projects by default. To enable it for existing projects, users
-explicitly do so in the project's settings.
+When downloading packages as dependencies in downstream projects, many requests are made through the
+Packages API. You may therefore reach enforced user and IP rate limits. To address this issue, you
+can define specific rate limits for the Packages API. For more details, see [Package Registry Rate Limits](../../user/admin_area/settings/package_registry_rate_limits.md).
 
-To enable the Packages feature:
+## Change the storage path
 
-**Omnibus GitLab installations**
+By default, the packages are stored locally, but you can change the default
+local location or even use object storage.
 
-1. Edit `/etc/gitlab/gitlab.rb` and add the following line:
+### Change the local storage path
 
-   ```ruby
-   gitlab_rails['packages_enabled'] = true
-   ```
+By default, the packages are stored in a local path, relative to the GitLab
+installation:
 
-1. Save the file and [reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure) for the changes to take effect.
+- Linux package (Omnibus): `/var/opt/gitlab/gitlab-rails/shared/packages/`
+- Self-compiled (source): `/home/git/gitlab/shared/packages/`
 
-**Installations from source**
+To change the local storage path:
 
-1. After the installation is complete, you configure the `packages`
-   section in `config/gitlab.yml`. Set to `true` to enable it:
+::Tabs
 
-   ```yaml
-   packages:
-     enabled: true
+:::TabTitle Linux package (Omnibus)
+
+1. Edit `/etc/gitlab/gitlab.rb` and add the following line:
+
+   ```ruby
+   gitlab_rails['packages_storage_path'] = "/mnt/packages"
    ```
 
-1. [Restart GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure) for the changes to take effect.
+1. Save the file and reconfigure GitLab:
+
+   ```shell
+   sudo gitlab-ctl reconfigure
+   ```
 
-**Helm Chart installations**
+:::TabTitle Self-compiled (source)
 
-1. After the installation is complete, you configure the `packages`
-   section in `global.appConfig.packages`. Set to `true` to enable it:
+1. Edit `/home/git/gitlab/config/gitlab.yml`:
 
    ```yaml
-   packages:
-     enabled: true
+   production: &base
+     packages:
+       enabled: true
+       storage_path: /mnt/packages
    ```
 
-1. [Restart GitLab](../restart_gitlab.md#helm-chart-installations) for the changes to take effect.
+1. Save the file and restart GitLab:
 
-## Rate limits
+   ```shell
+   # For systems running systemd
+   sudo systemctl restart gitlab.target
 
-When downloading packages as dependencies in downstream projects, many requests are made through the
-Packages API. You may therefore reach enforced user and IP rate limits. To address this issue, you
-can define specific rate limits for the Packages API. For more details, see [Package Registry Rate Limits](../../user/admin_area/settings/package_registry_rate_limits.md).
+   # For systems running SysV init
+   sudo service gitlab restart
+   ```
 
-## Changing the storage path
+::EndTabs
 
-By default, the packages are stored locally, but you can change the default
-local location or even use object storage.
+Docker and Kubernetes do not use local storage.
 
-### Changing the local storage path
+- For the Helm chart (Kubernetes): Use object storage instead.
+- For Docker: The `/var/opt/gitlab/` directory is already
+  mounted in a directory on the host. There's no need to change the local
+  storage path inside the container.
 
-The packages for Omnibus GitLab installations are stored under
-`/var/opt/gitlab/gitlab-rails/shared/packages/` and for source
-installations under `shared/packages/` (relative to the Git home directory).
-To change the local storage path:
+### Use object storage
 
-**Omnibus GitLab installations**
+Instead of relying on the local storage, you can use an object storage to store
+packages.
 
-1. Edit `/etc/gitlab/gitlab.rb` and add the following line:
+For more information, see how to use the
+[consolidated object storage settings](../object_storage.md#consolidated-object-storage-configuration).
 
-   ```ruby
-   gitlab_rails['packages_storage_path'] = "/mnt/packages"
-   ```
+### Migrate local packages to object storage
+
+After [configuring the object storage](#use-object-storage), use the following task to
+migrate existing packages from the local storage to the remote storage.
+The processing is done in a background worker and requires **no downtime**.
 
-1. Save the file and [reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure)
-   for the changes to take effect.
+1. Migrate the packages.
 
-**Installations from source**
+   ::Tabs
 
-1. Edit the `packages` section in `config/gitlab.yml`:
+   :::TabTitle Linux package (Omnibus)
 
-   ```yaml
-   packages:
-     enabled: true
-     storage_path: shared/packages
+   ```shell
+   sudo gitlab-rake "gitlab:packages:migrate"
    ```
 
-1. Save the file and [restart GitLab](../restart_gitlab.md#installations-from-source) for the changes to take effect.
-
-### Using object storage
+   :::TabTitle Self-compiled (source)
 
-Instead of relying on the local storage, you can use an object storage to
-store packages.
+   ```shell
+   RAILS_ENV=production sudo -u git -H bundle exec rake gitlab:packages:migrate
+   ```
 
-[Read more about using object storage with GitLab](../object_storage.md).
+   ::EndTabs
 
-NOTE:
-We recommend using the [consolidated object storage settings](../object_storage.md#consolidated-object-storage-configuration). The following instructions apply to the original configuration format.
+1. Track the progress and verify that all packages migrated successfully using
+   the PostgreSQL console.
 
-**Omnibus GitLab installations**
+   ::Tabs
 
-1. Edit `/etc/gitlab/gitlab.rb` and add the following lines (uncomment where
-   necessary):
+   :::TabTitle Linux package (Omnibus) 14.1 and earlier
 
-   ```ruby
-   gitlab_rails['packages_enabled'] = true
-   gitlab_rails['packages_object_store_enabled'] = true
-   gitlab_rails['packages_object_store_remote_directory'] = "packages" # The bucket name.
-   gitlab_rails['packages_object_store_proxy_download'] = false        # Passthrough all downloads via GitLab instead of using Redirects to Object Storage.
-   gitlab_rails['packages_object_store_connection'] = {
-     ##
-     ## If the provider is AWS S3, uncomment the following
-     ##
-     #'provider' => 'AWS',
-     #'region' => 'eu-west-1',
-     #'aws_access_key_id' => 'AWS_ACCESS_KEY_ID',
-     #'aws_secret_access_key' => 'AWS_SECRET_ACCESS_KEY',
-     ## If an IAM profile is being used with AWS, omit the aws_access_key_id and aws_secret_access_key and uncomment
-     #'use_iam_profile' => true,
-     ##
-     ## If the provider is other than AWS (an S3-compatible one), uncomment the following
-     ##
-     #'host' => 's3.amazonaws.com',
-     #'aws_signature_version' => 4             # For creation of signed URLs. Set to 2 if provider does not support v4.
-     #'endpoint' => 'https://s3.amazonaws.com' # Useful for S3-compliant services such as DigitalOcean Spaces.
-     #'path_style' => false                    # If true, use 'host/bucket_name/object' instead of 'bucket_name.host/object'.
-   }
+   ```shell
+   sudo gitlab-rails dbconsole
    ```
 
-1. Save the file and [reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure)
-   for the changes to take effect.
-
-**Installations from source**
+   :::TabTitle Linux package (Omnibus) 14.2 and later
 
-1. Edit the `packages` section in `config/gitlab.yml` (uncomment where necessary):
-
-   ```yaml
-   packages:
-     enabled: true
-     ##
-     ## The location where build packages are stored (default: shared/packages).
-     ##
-     # storage_path: shared/packages
-     object_store:
-       enabled: false
-       remote_directory: packages  # The bucket name.
-       # proxy_download: false     # Passthrough all downloads via GitLab instead of using Redirects to Object Storage.
-       connection:
-       ##
-       ## If the provider is AWS S3, use the following:
-       ##
-         provider: AWS
-         region: us-east-1
-         aws_access_key_id: AWS_ACCESS_KEY_ID
-         aws_secret_access_key: AWS_SECRET_ACCESS_KEY
-         ##
-         ## If the provider is other than AWS (an S3-compatible one), comment out the previous 4 lines and use the following instead:
-         ##
-         #  host: 's3.amazonaws.com'             # default: s3.amazonaws.com.
-         #  aws_signature_version: 4             # For creation of signed URLs. Set to 2 if provider does not support v4.
-         #  endpoint: 'https://s3.amazonaws.com' # Useful for S3-compliant services such as DigitalOcean Spaces.
-         #  path_style: false                    # If true, use 'host/bucket_name/object' instead of 'bucket_name.host/object'.
+   ```shell
+   sudo gitlab-rails dbconsole --database main
    ```
 
-1. Save the file and [restart GitLab](../restart_gitlab.md#installations-from-source) for the changes to take effect.
-
-### Migrating local packages to object storage
+   :::TabTitle Self-compiled (source)
 
-After [configuring the object storage](#using-object-storage), use the following task to
-migrate existing packages from the local storage to the remote storage.
-The processing is done in a background worker and requires **no downtime**.
+   ```shell
+   RAILS_ENV=production sudo -u git -H psql -d gitlabhq_production
+   ```
 
-For Omnibus GitLab:
+   ::EndTabs
 
-```shell
-sudo gitlab-rake "gitlab:packages:migrate"
-```
+1. Verify that all packages migrated to object storage with the following SQL
+   query. The number of `objectstg` should be the same as `total`:
 
-For installations from source:
+   ```shell
+   gitlabhq_production=# SELECT count(*) AS total, sum(case when file_store = '1' then 1 else 0 end) AS filesystem, sum(case when file_store = '2' then 1 else 0 end) AS objectstg FROM packages_package_files;
 
-```shell
-RAILS_ENV=production sudo -u git -H bundle exec rake gitlab:packages:migrate
-```
+   total | filesystem | objectstg
+   ------+------------+-----------
+    34   |          0 |        34
+   ```
 
-You can optionally track progress and verify that all packages migrated successfully using the
-[PostgreSQL console](https://docs.gitlab.com/omnibus/settings/database.html#connecting-to-the-bundled-postgresql-database):
+1. Finally, verify that there are no files on disk in the `packages` directory:
 
-- `sudo gitlab-rails dbconsole` for Omnibus GitLab 14.1 and earlier.
-- `sudo gitlab-rails dbconsole --database main` for Omnibus GitLab 14.2 and later.
-- `sudo -u git -H psql -d gitlabhq_production` for source-installed instances.
+   ::Tabs
 
-Verify `objectstg` below (where `file_store = '2'`) has count of all packages:
+   :::TabTitle Linux package (Omnibus)
 
-```shell
-gitlabhq_production=# SELECT count(*) AS total, sum(case when file_store = '1' then 1 else 0 end) AS filesystem, sum(case when file_store = '2' then 1 else 0 end) AS objectstg FROM packages_package_files;
+   ```shell
+   sudo find /var/opt/gitlab/gitlab-rails/shared/packages -type f | grep -v tmp | wc -l
+   ```
 
-total | filesystem | objectstg
-------+------------+-----------
- 34   |          0 |        34
-```
+   :::TabTitle Self-compiled (source)
 
-Verify that there are no files on disk in the `packages` folder:
+   ```shell
+   sudo -u git find /home/git/gitlab/shared/packages -type f | grep -v tmp | wc -l
+   ```
 
-```shell
-sudo find /var/opt/gitlab/gitlab-rails/shared/packages -type f | grep -v tmp | wc -l
-```
+   ::EndTabs
diff --git a/doc/integration/glab/img/example-output_v15_6.png b/doc/integration/glab/img/example-output_v15_6.png
deleted file mode 100644
index 7d2c5f2e4d9..00000000000
--- a/doc/integration/glab/img/example-output_v15_6.png
+++ /dev/null
diff --git a/doc/integration/glab/img/glabgettingstarted.gif b/doc/integration/glab/img/glabgettingstarted.gif
new file mode 100644
index 00000000000..cf335294e41
--- /dev/null
+++ b/doc/integration/glab/img/glabgettingstarted.gif
diff --git a/doc/integration/glab/index.md b/doc/integration/glab/index.md
index 77239c5f6c5..3951f38dfab 100644
--- a/doc/integration/glab/index.md
+++ b/doc/integration/glab/index.md
@@ -14,7 +14,7 @@ switching between windows and browser tabs.
 - Work with merge requests.
 - Watch running pipelines directly from your CLI.
 
-![command example](img/example-output_v15_6.png)
+![command example](img/glabgettingstarted.gif)
 
 The GitLab CLI uses commands structured like `glab <command> <subcommand> [flags]`
 to perform many of the actions you normally do from the GitLab user interface:
diff --git a/doc/user/group/saml_sso/index.md b/doc/user/group/saml_sso/index.md
index 15593655fac..a60e80d6196 100644
--- a/doc/user/group/saml_sso/index.md
+++ b/doc/user/group/saml_sso/index.md
@@ -342,6 +342,7 @@ To link SAML to your existing GitLab.com account:
 
 1. Sign in to your GitLab.com account. [Reset your password](https://gitlab.com/users/password/new) if necessary.
 1. Locate and visit the **GitLab single sign-on URL** for the group you're signing in to. A group owner can find this on the group's **Settings > SAML SSO** page. If the sign-in URL is configured, users can connect to the GitLab app from the identity provider.
+1. Optional. Select the **Remember me** checkbox to stay signed in to GitLab for 2 weeks. You may still be asked to re-authenticate with your SAML provider more frequently.
 1. Select **Authorize**.
 1. Enter your credentials on the identity provider if prompted.
 1. You are then redirected back to GitLab.com and should now have access to the group. In the future, you can use SAML to sign in to GitLab.com.
diff --git a/doc/user/packages/npm_registry/index.md b/doc/user/packages/npm_registry/index.md
index b1b5e99707b..c62999100c1 100644
--- a/doc/user/packages/npm_registry/index.md
+++ b/doc/user/packages/npm_registry/index.md
@@ -332,7 +332,7 @@ This might be accompanied by another error:
 This is usually a permissions issue with either:
 
 - `'packages_storage_path'` default `/var/opt/gitlab/gitlab-rails/shared/packages/`.
-- The remote bucket if [object storage](../../../administration/packages/index.md#using-object-storage)
+- The remote bucket if [object storage](../../../administration/packages/index.md#use-object-storage)
   is used.
 
 In the latter case, ensure the bucket exists and GitLab has write access to it.