Skip to content

Commit

Permalink
Use sha256 instead of sha1 in release announcement
Browse files Browse the repository at this point in the history
The last time perl got released, there was this comment:

https://www.nntp.perl.org/group/perl.perl5.porters/2022/01/msg262480.html

> Why use the old ( and somewhat broken ) SHA1 for message digests?

I decided to look into using SHA256;
I notice that the release managers guide gets the SHA1s from the PAUSE
email. So I've made a PR from PAUSE so that they no longer send SHA1s
(or MD5SUMS for that matter) but just SHA256. That change is live
already, see andk/pause#379

So now the next step is to update the perl release documentation to deal
with the new reality that PAUSE mails no longer incluse sha1s!
  • Loading branch information
mbeijen committed Feb 1, 2022
1 parent b4bc910 commit 75f77d0
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
6 changes: 3 additions & 3 deletions Porting/release_announcement_template.txt
Expand Up @@ -10,10 +10,10 @@ favorite CPAN mirror or find it at:

https://metacpan.org/release/[AUTHOR]/perl-5.[VERSION.SUBVERSION]/

SHA1 digests for this release are:
SHA256 digests for this release are:

[TAR.GZ SHA1] perl-5.[VERSION.SUBVERSION].tar.gz
[TAR.XZ SHA1] perl-5.[VERSION.SUBVERSION].tar.xz
[TAR.GZ SHA256] perl-5.[VERSION.SUBVERSION].tar.gz
[TAR.XZ SHA256] perl-5.[VERSION.SUBVERSION].tar.xz

You can find a full list of changes in the file "perldelta.pod" located in
the "pod" directory inside the release and on the web at
Expand Down
2 changes: 1 addition & 1 deletion Porting/release_managers_guide.pod
Expand Up @@ -1218,7 +1218,7 @@ Be sure to commit your change:
=head3 announce to p5p

Mail perl5-porters@perl.org to announce your new release, with a quote you prepared earlier.
Get the SHA1 digests from the PAUSE email responses.
Get the SHA256 digests from the PAUSE email responses.

Use the template at Porting/release_announcement_template.txt

Expand Down

0 comments on commit 75f77d0

Please sign in to comment.