ci: update SVN deploy message

[sherwinski]

One Line Summary

Updates the commit message to be more consistent with past releases. This is what gets displayed on https://plugins.trac.wordpress.org/browser/onesignal-free-web-push-notifications/trunk

Motivation

Consistency in SVN commit messages

Scope

• Affected: Publishing update to SVN
• Not affected:

Testing

N/A

Affected code checklist

• PHP plugin code (v3/)
• v2/ legacy code
• JS / CSS assets
• Build / CI
• Tests
• Documentation (README, readme.txt, etc.)

Checklist

• Code follows existing style in the touched files
• Tested manually in the relevant editor(s)
  • Gutenberg/Block editor
  • Classic editor
• No new lint or test errors introduced
• Linear ticket / GitHub issue linked above
• readme.txt and plugin version bumped if user-facing (release PRs only)

[claude]

LGTM — trivial one-line tweak to the SVN commit message template.

Extended reasoning...

Overview

This PR changes a single line in .github/workflows/publish-svn.yml, swapping the SVN commit message from "Deploy v${version} to trunk" to "${version} release" to match the format used in past WordPress.org plugin releases.

Security risks

None. The change only affects the human-readable commit message text passed to svn commit -m. It does not alter authentication, secret handling, file selection/rsync rules, tagging logic, or any other behavior. The interpolated value (steps.version.outputs.bare) is the same value used elsewhere in the workflow and is derived from the git tag.

Level of scrutiny

Very low. This is a cosmetic CI change with no functional impact on what gets published or how. The only observable difference is the message displayed in the WordPress.org plugin trac browser.

Other factors

The change is self-contained, the motivation (consistency with past release messages) is clearly stated, and the bug hunting system flagged nothing.