Fix broken specs : Generate new GPG key in place of expired one
What does this MR do?
Fixes #32956 (closed)
See #32956 (comment 223524940) for how I generated the new key (see 1password for passphrase)
spec/lib/gitlab/gpg/invalid_gpg_signature_updater_spec.rb spec/lib/gitlab/gpg/commit_spec.rb spec/models/gpg_key_spec.rb spec/features/profiles/gpg_keys_spec.rb
all pass with this commit (and failed without)
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation created/updated or follow-up review issue created
-
Code review guidelines - [-] Merge request performance guidelines
-
Style guides - [-] Database guides
-
Separation of EE specific content
Performance and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by 🤖 GitLab Bot 🤖