Changelog: removed

Changelog: changed

* `duo_features_enabled` was already an attribute on the
  `project_settings` table
* This MR uses the cascading settings framework to add this attribute to
  the `namespace_settings` table as well: https://docs.gitlab.com/ee/development/cascading_settings.html
* Other cascading settings assume that projects inherit the setting
  value from their parent group. For this setting, we want each project
  to be able to have a distinct setting value that may be different from
  its parent group. To do this, a new `CascadingProjectSettingAttribute`
  module was added that has very similar functionality to the
  `CascadingNamespaceSettingsAttribute` module.
* THis MR adds the cascading setting and behavior but the setting will
  not affect Duo Chat or Code Suggestions settings until a follow-on MR.
* https://gitlab.com/gitlab-org/gitlab/-/issues/441481

Changelog: added
EE: true

cyclonedx report dependsOn attribute.

EE: true

This reverts merge request !139630

This commit makes sure the references FKs for ci_job_artifacts
are now defined a the routing table level so all other new
partitions will inherit from them.

Changelog: other

Changelog: added

Changelog: changed
EE: true

Changelog: other

Changelog: removed

This commit adds a migration to create a new constraint for
ci_stages for self-managed users. The constraint was
successfully added on gitlab.com this weekend. This is a
prerequisite in order to partition this table.

Changelog: other

We found that the 'has_merge_request' column could have empty values,
which wasn't what we wanted. We've now made sure that this column
can't be empty, just like other similar columns in the same table.

Changelog: other

Signed-off-by: Siddharth Asthana <siddharthasthana31@gmail.com>

The syntax inside the CI config has been added in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/135430
This implementation is working with the feature flag
ci_retry_on_exit_codes.

This change introduces a background migration to purge `security_scans`
records associated with `security_findings` without `finding_data` set.

These kinds of records do not exist on GitLab.com as the `finding_data`
column was introduced in '15.6' and the records created before that
milestone are already removed from the database by the data retention
policy of 3 months on the `security_findings` table but there is no
guarantee for the self-hosted installations.

Therefore, the background migration introduced in this MR will only run
for self-hosted installations.

Changelog: added

Changelog: added

Changelog: added

This MR includes:
- Dropping the column 'package_name_pattern_ilike_query'
  because it this column is not needed anymore
- Changes for the 2nd part for dropping a column based
  on the GitLab guide, see
  https://docs.gitlab.com/ee/development/database/avoiding_downtime_in_migrations.html#dropping-columns
- Changes relevant for protected packages

Changelog: removed

Changelog: changed
EE: true

This MR sets up validation for semantic versioning when releasing a new
vesion of the catalog resource.

* Add migration for adding columns to support parsing of SemVer
* Updates the Versions::CreateService to use `release.tag` for
  versioning
* Updates specs that were not using semantic version, thus testing the
  semantic version validation further
* Quarantines an out of date feature spec

Changelog: added

This change adds violation_data for violations
so that details about policy violations can be persisted
and resurfaced to the user.

Changelog: other

Changelog: added

Changelog: added
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144534

Changelog: other

This allows admin access to CI/CD variables as a customizable ability,
so that it can be added onto any base role.

EE: true

This table belonged to an old version of product
analytics that is no longer used.

No production has been stored here for years.

Changelog: removed

- On member_id, member_namespace_id, new_access_level to ensure
  only one record per member per namespace for the accesslevel exists
  in pending state

Changelog: added

Since an index on [name, pipeline_id] has been introduced, we can
remove the old index on [pipeline_id, name].

Changelog: performance

This is the second migration to validate the foreign key synchronously

See https://docs.gitlab.com/ee/development/database/add_foreign_key_to_existing_column.html#add-a-migration-to-validate-the-fk-synchronously

Changelog: added

This is the second step to synchronously create indexes for p_ci_builds
See https://docs.gitlab.com/ee/development/database/adding_database_indexes.html#add-a-migration-to-create-the-index-synchronously

And prepare the foreign key to prevent invalid records
See https://docs.gitlab.com/ee/development/database/add_foreign_key_to_existing_column.html#prevent-invalid-records

Changelog: added

Changelog: changed

This commit creates the routing table for ci_job_artifacts.

Changelog: other

Maxime Orefice 创作于 1 year ago ，Maxime Orefice 提交于 1 year ago

This commit enqueues a job which will create a new constraint this
weekend on ci_job_artifacts. This is a prerequisite in order to
partition this table.

Changelog: other

Direct Transfer API shows failures for the things that we could not
import. If a subrelation of a top level relation failed to import
(e.g. MR diff note) - we still show top level relation as the one
that failed to import. In reality, the top level relation is imported,
but a subrelation did not.

Update relation to include the failed to import subrelation, so it's
more obvious what exactly failed to import.

Changelog: added

Changelog: added
EE: true

in place of component_id.

EE: true
Changelog: fixed

Instance setting `math_rendering_limits_enabled` can now
be queried and set on groups as well. It is a cascading
setting, so it can be locked at any level.

Changelog: added

This is the second step to synchronously create indexes for p_ci_builds
See https://docs.gitlab.com/ee/development/database/adding_database_indexes.html#add-a-migration-to-create-the-index-synchronously

And prepare the foreign key to prevent invalid records
See https://docs.gitlab.com/ee/development/database/add_foreign_key_to_existing_column.html#prevent-invalid-records

Changelog: added