Revert "Merge branch 'upgrade-to-semver_dialects-3.0.0' into 'master'"
What does this MR do and why?
Revert "Merge branch 'upgrade-to-semver_dialects-3.0.0' into 'master'"
This reverts merge request !151761 (merged)
Note
This revert was reviewed in Revert "Merge branch 'upgrade-to-semver_dialect... (!152319 - closed) • Thiago Figueiró, Philip Cunningham+ • 17.0. Please see this thread.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Merge request reports
Activity
changed milestone to %17.0
assigned to @philipcunningham
removed pipeline:mr-approved label
- Resolved by Mehmet Emin INAC
Dependency change review report
Please wait to merge until below tasks are completed by @gitlab-com/gl-security/appsec
- Review below metadata report and resolve this thread. Review guidelines are at handbook page.
Modified Dependency: semver_dialects (2.0.2) Location:
Gemfile.lock
Version diffsChecks passed:3/5
-
️ Latest version: 3.0.0 released on: 2024-04-29. URL: https://rubygems.org/gems/semver_dialects -
Latest version is not in use. -
Total downloads: 5861999 -
Reverse dependencies: 0 -
Total number of releases: 15 -
Latest version age (months): 0 -
️ Gem source could not be located in GitHub. -
️ Maintainer emails are private. Email domain check skipped.
This automation is under testing, please leave your feedback in the issue.
1 Warning In a revert merge request? Use the revert merge request template to add labels that skip changelog checks. Reverting something in the current milestone? A changelog isn't required. Skip changelog checks by adding
~"regression:*"
label, then re-run the danger job (there is a link at the bottom of this comment).1 Message CHANGELOG missing: If this merge request needs a changelog entry, add the
Changelog
trailer to the commit message you want to add to the changelog.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Category Reviewer Maintainer backend @leetickett-gitlab
(UTC+1, same timezone as author)
@a_akgun
(UTC+3, 2 hours ahead of author)
Please check reviewer's status!
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
Rubygems
This merge request adds, or changes a Rubygems dependency. Please review the Gemfile guidelines.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermentioned in merge request !152319 (closed)
- Resolved by Mehmet Emin INAC
NON-BLOCKING: This MR has changed Gemfile.checksum. GitLab team members should review the following dependency SAST scans when they finish:If there appear to be any true-positive vulnerabilities identified with CRITICAL or HIGH severity, if the report is misconfigured, or if you have questions, reply to this thread and mention
@gitlab-com/gl-security/appsec
.Otherwise, this does not require an AppSec review.
Please also review the Gemfile development AppSec guidelines. Thank you for keeping GitLab secure!
Generated by depSASTer. Open an issue to provide feedback.
removed pipeline:expedite label
added pipeline:expedite label
enabled an automatic merge when all merge checks for 4f98752f pass
- Resolved by Philip Cunningham
This is the pipeline we'll need to keep an eye on:
https://gitlab.com/gitlab-org/gitlab/-/pipelines/1283207051
We'll need to ensure that the runner type is
green-5.private.runners-manager.gitlab.com
and notgreen-3.saas-linux-small-amd64.runners-manager.gitlab.com
in order for the jobs to pass. The exact name may differ butsmall
is the tell. The individual jobs, not the entire pipeline, should be retried.Edited by Philip Cunningham
mentioned in commit c2973010
Successfully picked into
17-0-auto-deploy-2024050812
.This merge request will receive additional notifications as it's deployed. You can also use the following chatops command to check its status:
/chatops run auto_deploy status https://gitlab.com/gitlab-org/gitlab/-/merge_requests/152342
removed Pick into auto-deploy label
mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#6225 (closed)
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added releasedcandidate label
mentioned in merge request !151298 (merged)
mentioned in merge request !151761 (merged)
mentioned in issue #386070 (closed)
mentioned in issue gl-retrospectives/secure-sub-dept/composition-analysis#45 (closed)
mentioned in issue #462854 (closed)
added releasedpublished label and removed releasedcandidate label