Skip to content

Commit a08a59c

Browse files
Dustin CollinsRobert Marshall
authored andcommitted
Update package signature dates to reflect GPG key extension
GPG key now expires on 2026-02-27. Changelog: changed
1 parent 52b45f1 commit a08a59c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/update/package_signatures.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,16 +29,16 @@ script specified in the installation instructions.
2929
| EMail | `[email protected]` |
3030
| Comment | `package repository signing key` |
3131
| Fingerprint | `F640 3F65 44A3 8863 DAA0 B6E0 3F01 618A 5131 2F3F` |
32-
| Expiry | `2024-03-01` |
32+
| Expiry | `2026-02-27` |
3333

3434
This key is active from **2020-04-06**. Existing users who already have
3535
configured the GitLab apt/yum package repositories will have to fetch and add this
3636
key to their trusted keyring again to continue installing packages from those
3737
repositories without apt/yum complaining about mismatches, which is described
3838
below.
3939

40-
This key's expiration was extended from **2022-03-02** to **2024-03-01**.
41-
If you encounter a complaint of expiration on `2022-03-02`, perform the steps
40+
This key's expiration was extended from **2024-03-01** to **2026-02-27**.
41+
If you encounter a complaint of expiration on `2024-03-01`, perform the steps
4242
in [Update keys after expiry extension](#update-keys-after-expiry-extension)
4343
to incorporate the updated public key content.
4444

0 commit comments

Comments
 (0)