fix(changelog): disable @-mention pings in all publish issues

#755 only stripped @-mentions from the publish-issue changelog for CalVer
releases, on the theory that regular-cadence releases are the noisy ones.
In practice any release that bundles more than a handful of PRs pings
every contributor when the publish issue is created — e.g.
getsentry/publish#9728 for devservices 1.5.2 (SemVer) notified everyone
listed. Nobody needs a notification because their PR shipped in a
release, so apply the same treatment regardless of versioning policy.

The committed CHANGELOG.md is unaffected and keeps @-mentions, since
those don't notify anyone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: vaind

src/commands/prepare.ts

@@ -964,16 +964,11 @@ export async function prepareMain(argv: PrepareOptions): Promise<any> {
     setGitHubActionsOutput('sha', releaseSha);
     setGitHubActionsOutput('previous_tag', oldVersion || '');
     if (changelogBody) {
-      // For CalVer releases, replace @-mentions with bold formatting in the
-      // changelog destined for publish issues, to avoid pinging many
-      // contributors on regular-cadence releases.  The committed CHANGELOG.md
-      // keeps the original @-mentions (they don't create notifications).
-      const isCalVer =
-        argv.newVersion === 'calver' ||
-        getVersioningPolicy() === VersioningPolicy.CalVer;
-      const issueChangelog = isCalVer
-        ? disableChangelogMentions(changelogBody)
-        : changelogBody;
+      // Replace @-mentions with bold formatting in the changelog destined for
+      // publish issues, otherwise every contributor in the release gets
+      // pinged. The committed CHANGELOG.md keeps the original @-mentions
+      // (they don't create notifications).
+      const issueChangelog = disableChangelogMentions(changelogBody);
 
       // Write full changelog to a file to avoid E2BIG when the action.yml
       // "Request publish" step expands it into an environment variable.