tree b8cbee65a3444326f4d4c134a905e9c577669eeb
parent bd1518d487119378e54c00d45d04e29223320299
author Dmitri Shuralyov <dmitshur@golang.org> 1753999432 -0400
committer Gopher Robot <gobot@golang.org> 1761239423 -0700

internal/task: support security field in the announce-rc template

We want to make it clear to users who start testing and using release
candidate versions in production that they can receive security fixes
while continuing to use RCs. So when RCs have security fixes included,
we include that information in the corresponding release announcement
emails, just like we do for minor releases. So, add necessary support
for security fields to the RC workflow and template, too.

A few notes:
- I'm working on a combined minors+RC release workflow, at which point
  we could have a single release announcement for all 3 releases if we
  wanted. (Though it's possible we'll decide it's better to continue to
  use separate emails even when a single workflow sends them out.)
  There's a bit of preparation to be able to do this, so it's not in
  scope here. That said, I did aim to unify the language used across
  release types where it made sense.
- Since I needed to add a new test case, it was convenient to make
  the template say "1 security fix" instead of "1 security fixes".
- The social media post templates already support security inputs.
  Nothing to do there except add a test case so we can't break it.
- By now go.dev/security is a top-level security page, and the security
  policy is a sub-page. Updated old links to point to the new location.
- Removed an obsolete go1.23rc1-specific section. It was a no-op by now.

Fixes golang/go#71574.

Change-Id: I19131776f89f4cafe829258d46a449be92e0c843
Reviewed-on: https://go-review.googlesource.com/c/build/+/692236
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Roland Shoemaker <roland@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>