Update 'security-release' strings to 'patch release'
The 'security-release' term is used in several files on release-tools. These should be replaced by the term 'Patch release'
Click to expand
lib/tasks/security.rake:9: desc 'Create a security release task issue'
lib/tasks/security.rake:37: desc 'Prepare for a new security release'
lib/tasks/security.rake:43: desc 'Publish the current security release'
lib/tasks/security.rake:53: desc "Check a security release's build status"
lib/tasks/security.rake:68: desc 'Tag a new security release'
lib/tasks/security.rake:101: desc 'Tag a new Gitaly security release'
lib/tasks/security.rake:107: desc 'Link/Unlink security-target issues for a security release'
lib/tasks/security.rake:127: desc 'Notify JiHu about the security release'
lib/tasks/security.rake:132: desc 'Notify a stage team about the security release'
lib/tasks/security.rake:169: desc 'Deploy the security release blog post'
lib/tasks/security.rake:197: desc 'Notify the completion of the security release'
lib/release_tools/cherry_pick/auto_deploy_service.rb:108: If it is not (for example during a security release), manually trigger the `gitlab-org/gitlab@master -> gitlab-org/security/gitlab@master` merge-train pipeline schedule:
lib/release_tools/security/target_issues_processor.rb:16: logger.info("#{security_target_issues.count} target issues found. They will be evaluated and considered for linking to the security release tracking issue: #{security_release_tracking_issue.web_url}.")
lib/release_tools/security/target_issues_processor.rb:21: logger.info("#{target_issue.web_url} is already linked to the security release tracking issue and still ready to be processed.")
lib/release_tools/security/target_issues_processor.rb:25: logger.info("#{target_issue.web_url} is not ready to be processed or linked to the security release tracking issue.")
lib/release_tools/security/target_issues_processor.rb:30: logger.info("#{target_issue.web_url} is ready to be processed and will be linked to the security release tracking issue.")
lib/release_tools/security/target_issues_processor.rb:37: logger.info("#{target_issue.web_url} will be unlinked from the security release tracking issue as it is no longer ready to be processed.")
lib/release_tools/security/issue_table/service.rb:5: # Create a table summarising the status of all security issues as a comment on the security release issue.
lib/release_tools/security/issue_table/service.rb:71: "Editing security release table issue comment",
lib/release_tools/security/issue_table/service.rb:75: logger.info("Creating security release table issue comment", issue: release_issue.web_url)
lib/release_tools/security/notify_stable_branch_creation.rb:63: following the security release MR template. If this backport is not needed, please
lib/release_tools/security/prepare/notify_jihu.rb:48: search: 'GitLab patch and security release dates'
lib/release_tools/security/tracking_issue.rb:10: # Represent the cadence to schedule planned security releases
lib/release_tools/security/tracking_issue.rb:29: 'upcoming security release,security,meta'
lib/release_tools/security/issue_links_validator.rb:5: # Validation of security issues linked to next security release tracking issue
lib/release_tools/security/issue_links_validator.rb:16: patch release, they can be linked as blockers to this security release.
lib/release_tools/security/issue_links_validator.rb:53: # Do not unlink security issues that block the security release.
lib/release_tools/security/implementation_issue_validator.rb:106: error("`#{versions_type}` don't match the security release versions", <<~ERROR)
lib/release_tools/security/implementation_issue_validator.rb:107: The `#{versions_type}` defined on [CVES issue](#{cves.web_url}) does not match the security release versions:
lib/release_tools/security/release_preparation/generate_blog_post.rb:20: logger.info("Printing blog post for security release")
lib/release_tools/security/release_preparation/generate_blog_post.rb:31: logger.info('Creating security release blog post')
lib/release_tools/security/release_preparation/generate_blog_post.rb:111: Generating security release blog post failed. If this job continues to fail,
lib/release_tools/security/finalize/notify_next_release_managers.rb:74: #{message_prefix}. Please set a due date for the next security release based on the [upcoming dates defined for planned releases](https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/19967).
lib/release_tools/security/finalize/notify_next_release_managers.rb:82: If the job continues to fail, notify #{next_release_managers.join(', ')} about the security release on #{security_tracking_issue.web_url}
lib/release_tools/security/finalize/notify_release_complete.rb:17: logger.info('Notifying security release completion', versions: versions)
lib/release_tools/security/finalize/notify_release_complete.rb:60: The security release blog post couldn't be found or the pipeline in ChatOps failed to be created.
lib/release_tools/security/merge_requests_validator.rb:20: applied or your issue will not be linked to the security release tracking issue.
lib/release_tools/security/issue_crawler.rb:5: # Crawling of security release issues to determine their associated security
lib/release_tools/security/issue_crawler.rb:18: # for the next security release.
lib/release_tools/security/issue_crawler.rb:32: # Returns all security issues for the upcoming security release.
lib/release_tools/security/issue_crawler.rb:65: # Returns issues that are related to the security release tracking issue.
lib/release_tools/security/issue_crawler.rb:73: # are ready to be evaluated for the next security release.
lib/release_tools/qa/issue.rb:12: # can't distinguish between a regular and security release, so default
lib/release_tools/project/base_project.rb:68: # based on the security release status, as using `#to_s` could make one
lib/release_tools/public_release/release.rb:143: # public project path. This way even during a security release we fetch
lib/release_tools/changelog_compiler.rb:11: # any knowledge of regular releases, security releases, etc; it's up to a
lib/release_tools/gitlab_client.rb:662: label = 'upcoming security release'
Binary file lib/release_tools/.gitlab_client.rb.swp matches
lib/release_tools/deployments/metadata.rb:6: # versions and if a deployment/release is a security release.
lib/release_tools/deployments/metadata.rb:14: # Returns `true` if the release is a security release.
spec/support/shared_examples/project_shared_examples.rb:8: it 'returns only dev and security remotes during a security release' do
spec/support/shared_examples/project_shared_examples.rb:24: context 'with a security release' do
spec/support/shared_examples/project_shared_examples.rb:51: context 'with a security release' do
spec/lib/tasks/security_rake_spec.rb:41: it 'publishes the security release blog post' do
spec/lib/release_tools/metrics/track_release_tagged_spec.rb:45: context 'for security release' do
spec/lib/release_tools/metrics/track_release_tagged_spec.rb:46: it 'increments the package tagging metric for regular security releases' do
spec/lib/release_tools/metrics/track_release_tagged_spec.rb:55: context 'for critical security release' do
spec/lib/release_tools/metrics/track_release_tagged_spec.rb:56: it 'increments the package tagging metric for critical security releases' do
spec/lib/release_tools/security/implementation_issue_validator_spec.rb:151: context 'when the security release versions match the affected versions' do
spec/lib/release_tools/security/implementation_issue_validator_spec.rb:159: context 'when the security release versions do not match the affected versions' do
spec/lib/release_tools/security/implementation_issue_validator_spec.rb:168: .to include("`affected_versions` don't match the security release versions")
spec/lib/release_tools/security/implementation_issue_validator_spec.rb:203: context 'when the security release versions match the fixed versions' do
spec/lib/release_tools/security/implementation_issue_validator_spec.rb:211: context 'when the security release versions do not match the fixed versions' do
spec/lib/release_tools/security/implementation_issue_validator_spec.rb:220: .to include("`fixed_versions` don't match the security release versions")
spec/lib/release_tools/security/prepare/notify_jihu_spec.rb:63: context 'during a critical security release' do
spec/lib/release_tools/security/tracking_issue_spec.rb:22: context 'when performing a critical security release' do
spec/lib/release_tools/security/tracking_issue_spec.rb:40: it { is_expected.to include('upcoming security release') }
spec/lib/release_tools/security/security_mirror_notification_service_spec.rb:75: context 'when running the security release pipeline' do
spec/lib/release_tools/security/issue_crawler_spec.rb:56: context 'when there are no security release issues' do
spec/lib/release_tools/security/issue_crawler_spec.rb:64: context 'when there are security release issues' do
spec/lib/release_tools/security/issue_helper_spec.rb:42: context 'critical security release' do
spec/lib/release_tools/security/notify_stable_branch_creation_spec.rb:21: following the security release MR template. If this backport is not needed, please
spec/lib/release_tools/security/finalize/close_implementation_issues_spec.rb:114: context 'with a security release pipeline' do
spec/lib/release_tools/security/finalize/close_tracking_issue_spec.rb:41: context 'with a security release pipeline' do
spec/lib/release_tools/security/finalize/close_tracking_issue_spec.rb:67: context 'with a security release pipeline' do
spec/lib/release_tools/security/issue_links_validator_spec.rb:180: patch release, they can be linked as blockers to this security release.
spec/lib/release_tools/patch_release/security_issue_spec.rb:30: context 'with a regular security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:36: context 'with a critical security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:67: it 'includes a step to perform a security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:111: context 'with a regular security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:115: context 'with a critical security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:127: context 'with a regular security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:131: context 'with a critical security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:143: it 'creates a security release pipeline' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:157: it "creates a security release pipeline on the ops instance" do
spec/lib/release_tools/patch_release/security_issue_spec.rb:169: context 'critical security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:170: it "creates a security release injecting the SECURITY variable" do
spec/lib/release_tools/patch_release/security_issue_spec.rb:204: it 'returns the security release tracking issue' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:214: it 'returns the security release type' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:218: context 'on a critical security release' do
spec/lib/release_tools/patch_release/security_issue_spec.rb:219: it 'returns the associated security release type' do
spec/lib/release_tools/patch_release/blog_merge_request_spec.rb:531: context 'critical security release' do
spec/lib/release_tools/public_release/release_spec.rb:51: context 'for a security release' do
spec/lib/release_tools/gitlab_client_spec.rb:1174: .with('gitlab-org/gitlab', labels: 'upcoming security release', state: 'opened')
spec/lib/release_tools/gitlab_client_spec.rb:1181: it 'fetches the current security release task issue' do
spec/lib/release_tools/gitlab_client_spec.rb:1199: it 'fetches the security release blog post from the security repository' do
spec/lib/release_tools/gitlab_client_spec.rb:1214: it 'fetches the security release blog post from the canonical repository' do
spec/lib/release_tools/shared_status_spec.rb:53: it 'allows enabling of security releases for the duration of the block' do
spec/lib/release_tools/slack/tag_notification_spec.rb:39: context 'with a non-security release' do
spec/lib/release_tools/slack/tag_notification_spec.rb:56: context 'with a security release' do
spec/lib/release_tools/slack/security/team_notifier_spec.rb:72: context 'during a critical security release' do
spec/lib/release_tools/auto_deploy/post_deploy_migrations/deployment_tracker_spec.rb:111: context 'with a security release' do
spec/lib/release_tools/deployments/metadata_spec.rb:8: it 'returns true when the version is a security release' do
spec/lib/release_tools/deployments/metadata_spec.rb:32: it 'returns true when the version is a security release' do
spec/fixtures/merge_requests/patch_release_blog_post.html.md:20:GitLab releases patches for vulnerabilities in dedicated security releases. There are two types of security releases:
spec/fixtures/merge_requests/patch_release_blog_post.html.md:21:a monthly, scheduled security release, released a week after the feature release (which deploys on the 3rd Thursday of each month),
spec/fixtures/merge_requests/patch_release_blog_post.html.md:22:and ad-hoc security releases for critical vulnerabilities. For more information, you can visit our [security FAQ](https://about.gitlab.com/security/faq/).
spec/fixtures/merge_requests/patch_release_blog_post.html.md:23:You can see all of our regular and security release blog posts [here](/releases/categories/releases/).
spec/fixtures/merge_requests/patch_release_blog_post.html.md:31:upgrade to the latest security release for their supported version. You can read more
spec/fixtures/merge_requests/patch_release_blog_post.html.md:98:## We’re combining patch and security releases
spec/fixtures/merge_requests/single_patch_blog_merge_request_template.html.md:43:## We’re combining patch and security releases