- follow pajamas design pattern.

Update npm registy doc with a few changes

See merge request gitlab-org/gitlab!57032

Do not send emails for in-product marketing twice to a user

See merge request gitlab-org/gitlab!55840

Initial edits to top-level page

See merge request gitlab-org/gitlab!56887

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/324250
Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/300312

Create 13.10 What's New entry

See merge request gitlab-org/gitlab!57119

Do not render empty title in HelpPopover

See merge request gitlab-org/gitlab!57025

Do not render title in HelpPopover if it was not provided.

(Also use `GlSafeHtmlDirective` instead of `v-html`).

External users cannot create snippets

See merge request gitlab-org/gitlab!53911

Change node to site for Geo datatypes page

See merge request gitlab-org/gitlab!56799

Compress images in docs

See merge request gitlab-org/gitlab!57078

Add paragraph on how to remove billable users

See merge request gitlab-org/gitlab!56991

Fix order-dependent DesignManagement::SaveDesignsService spec

See merge request gitlab-org/gitlab!57127

Run CI_PRE_CLONE_SCRIPT in sub-shell

See merge request gitlab-org/gitlab!57128

Change highlight color for higher contrast

See merge request gitlab-org/gitlab!57092

in in-page search settings feature

Edited for style and redid screenshot

See merge request gitlab-org/gitlab!57035

Add request method to the endpoint_id for Grape

See merge request gitlab-org/gitlab!57091

This spec uses `build_stubbed`, which uses IDs starting at 1000 and
incrementing on their own internal counter. It appears that we had a
combination of specs where this ID matched an actual database ID of a
user with access (probably `developer` in this spec file), which is
unlikely but not impossible.

By using `non_existing_record_id` as the ID for this stubbed record, we
ensure that can't happen.

Enable DISTINCT optimization for ObjectHierarchy globally [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!57052

Refactor(createFlash): use non-deprecated function

See merge request gitlab-org/gitlab!56948

Migrate away from `deprecatedCreateFlash` and use
`createFlash` instead.

Manual changes

Epic:
https://gitlab.com/groups/gitlab-org/-/epics/3895

Correctly translate weight for Russian

See merge request gitlab-org/gitlab!56986

Fix typo in docs

See merge request gitlab-org/gitlab!57116

Docs - Correct Web IDE configuration file example

See merge request gitlab-org/gitlab!57099

Migrate cycle-analytics/banner_spec to VTU

See merge request gitlab-org/gitlab!57024

Fix ruby alpine CI template

See merge request gitlab-org/gitlab!57109

Merge branch '323986-f-u-f-55810-add-vue-component-specs-for-custom-tracking-behavior' into 'master'

Track opening the trial status popover with the tracking mixin

See merge request gitlab-org/gitlab!56996

Push confidential notes ff to mr fe

See merge request gitlab-org/gitlab!56798

Improve Gitaly Cluster documentation

See merge request gitlab-org/gitlab!56807

This adds a context around expiring members

See merge request gitlab-org/gitlab!57028

The context will be different depending on the type of member that is
being expired:

For a `GroupMember` the `source` relation will be a group, so the
`meta.root_namespace` will the root ancestor of that group.

For a `ProjectMember` the `source` relation will be a project. So the
`meta.project` will be set to that project, and the
`meta.root_namespace` will become the root namespace of that project.

The `meta.user` will always be set to the username of the user for
which the membership is being expired.

COPY Gemfile Gemfile.lock . is invalid syntax.
When using COPY with more than one source file,
the destination must be a directory and end with a /
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>