chore(deps): bump hyperpolymath/smtp-notify-action from 0.5.0 to 0.5.1 in the actions group (#72)

Bumps the actions group with 1 update:
[hyperpolymath/smtp-notify-action](https://github.com/hyperpolymath/smtp-notify-action).

Updates `hyperpolymath/smtp-notify-action` from 0.5.0 to 0.5.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/hyperpolymath/smtp-notify-action/releases">hyperpolymath/smtp-notify-action's
releases</a>.</em></p>
<blockquote>
<h2>v0.5.1</h2>
<h3>Protocol-neutral <code>server_address</code> metadata</h3>
<p><code>server_address</code> is the host input for both SMTP and NNTP,
and remained the only input in <code>action.yml</code> still described
as SMTP-only (<code>'SMTP server host name'</code>). It now reads:</p>
<pre lang="yaml"><code>description: 'Server host name (SMTP or NNTP, per
protocol: `protocol`)'
</code></pre>
<p>The <code>secure</code> and <code>diagnose</code> folded scalar
descriptions were also rewrapped to line width (<code>Reports</code> →
<code>reports</code> after the colon in <code>diagnose</code>), and the
download URL in <code>action.yml</code> now points to
<code>v0.5.1</code>.</p>
<p>Because workflow editors, consumers, and GitHub Marketplace read
<code>action.yml</code> from the release tag — and tags are immutable
here — this ships as <code>v0.5.1</code> rather than moving
<code>v0.5.0</code>. <code>v0.5.0</code> remains supported in
<code>SECURITY.md</code> since the binary and input surface are
unchanged.</p>
<p>For the full NNTP posting (<code>protocol: nntp</code>,
<code>newsgroups</code>) and Marketplace readiness notes introduced in
the 0.5 series, see <strong><a
href="https://github.com/hyperpolymath/smtp-notify-action/releases/tag/v0.5.0">v0.5.0</a></strong>
and <code>CHANGELOG.adoc</code>.</p>
<h3>Provenance</h3>
<p>Zero Zig or Idris2 source files changed between <code>v0.5.0</code>
and <code>v0.5.1</code>. CI rebuilt both static musl binaries from this
tag and verified they hash byte-identically to the unchanged SHA-256
pins inside <code>action.yml</code> before publishing.
<code>SHA256SUMS</code> is attached:</p>

<pre><code>2683da8f619dd5f310c9f6884da39e825c807c2c86a6319c19aba39b27f9c5c9
smtp-notify-x86_64-linux-musl
a58138308fb9832e1ceb551a12f1b04e591dc38ba5fd336c9acfb3f263161f29
smtp-notify-aarch64-linux-musl
</code></pre>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/hyperpolymath/smtp-notify-action/blob/main/CHANGELOG.adoc">hyperpolymath/smtp-notify-action's
changelog</a>.</em></p>
<blockquote>
<p>// SPDX-License-Identifier: MPL-2.0
= Changelog
:toc: macro
:toclevels: 2</p>
<p>All notable changes to this action are recorded here. The format
follows
<a
href="https://keepachangelog.com/en/1.1.0/%5BKeep">https://keepachangelog.com/en/1.1.0/[Keep</a>
a Changelog]; versions follow
<a
href="https://semver.org/spec/v2.0.0.html%5BSemantic">https://semver.org/spec/v2.0.0.html[Semantic</a>
Versioning].</p>
<p>The unit of release is the <em>action ref</em>: the tag or commit you
pin determines both
<code>action.yml</code> and, through the SHA-256 pins inside it, the
exact binary that runs.</p>
<p>toc::[]</p>
<p>== v0.6.0-rc.1 — 2026-10-24 (pre-release)</p>
<p>Pre-release adding <code>protocol: nntps</code> as a direct,
fail-closed spelling for NNTP
over implicit TLS (port 563), alongside SemVer pre-release support in
<code>release.yml</code>. Published as a GitHub pre-release so
<code>v0.5.1</code> remains <code>Latest</code>
(and the Marketplace-eligible stable release) while <code>protocol:
nntps</code> and D-015
(live news-server verification) are exercised.</p>
<p>=== Added</p>
<ul>
<li><em><code>protocol: nntps</code>
(<code>SMTP_PROTOCOL=nntps</code>).</em> Selects NNTP over implicit TLS
(RFC 4642 §2.1, default port 563) directly without needing a separate
<code>secure:</code> line. Fail-closed against conflicting transport
inputs: pairing
<code>protocol: nntps</code> with <code>secure:
false</code>/<code>starttls</code> or <code>secure: plaintext</code>
refuses the run before opening a socket rather than silently downgrading
TLS
or silently ignoring <code>secure</code> (D-011).</li>
<li><em>Pre-release tag handling in
<code>.github/workflows/release.yml</code>.</em> Tags carrying a
SemVer pre-release suffix (<code>*-*</code>, such as
<code>v0.6.0-rc.1</code>) now pass
<code>--prerelease</code> to <code>gh release create</code>, keeping the
latest stable tag as
<code>Latest</code>.</li>
</ul>
<p>=== Changed</p>
<ul>
<li><code>action.yml</code> asset URL names <code>v0.6.0-rc.1</code> and
pins the rebuilt static musl
binaries (<code>adc643aa…</code> for <code>x86_64-linux-musl</code>,
<code>16206d7d…</code> for
<code>aarch64-linux-musl</code>).</li>
</ul>
<p>== v0.5.1 — 2026-10-24</p>
<p>A metadata correction, and the release to publish the Marketplace
listing from.
The binary is <em>byte-identical</em> to v0.5.0's — the two SHA-256 pins
are unchanged
and re-verified by the release workflow — so v0.5.0 remains supported
and
correct for anyone already pinned to it. A new tag rather than an edit
of the
existing one because a tag is immutable here: consumers pin SHAs, and
GitHub
reads <code>action.yml</code> <em>from the tag</em>, which is the same
property that made v0.5.0
necessary in the first place.</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/e384daf6167a7a7567642d6a62060106244d2413"><code>e384daf</code></a>
fix(action): protocol-neutral server_address wording (needs tag v0.5.1)
(<a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/28">#28</a>)</li>
<li>See full diff in <a
href="https://github.com/hyperpolymath/smtp-notify-action/compare/c1c9fa07992a02c1fd3d67a0dc1b08cccb852aef...e384daf6167a7a7567642d6a62060106244d2413">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=hyperpolymath/smtp-notify-action&package-manager=github_actions&previous-version=0.5.0&new-version=0.5.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

.github/workflows/actions.lock

@@ -44,7 +44,7 @@ workflows:
         - 'actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e'
         - 'actions/upload-pages-artifact@56afc609e74202658d3ffba0e8f6dda462b719fa'
     '.github/workflows/push-email-notify.yml':
-        - 'hyperpolymath/smtp-notify-action@ede1191ef6ff3ac02c4f4d9efdf837ee517e11d7'
+        - 'hyperpolymath/smtp-notify-action@e384daf6167a7a7567642d6a62060106244d2413'
 dependencies:
     'actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7':
         ref: 'v5.0.4'
@@ -150,9 +150,9 @@ dependencies:
         commit: 'sha1-89f3c2702f4f650a92aa7411502f38da06abd562'
         owner_id: 6759885
         repo_id: 1275650185
-    'hyperpolymath/smtp-notify-action@ede1191ef6ff3ac02c4f4d9efdf837ee517e11d7':
-        ref: 'v0.2.0'
-        commit: 'sha1-ede1191ef6ff3ac02c4f4d9efdf837ee517e11d7'
+    'hyperpolymath/smtp-notify-action@e384daf6167a7a7567642d6a62060106244d2413':
+        ref: 'v0.5.1'
+        commit: 'sha1-e384daf6167a7a7567642d6a62060106244d2413'
         owner_id: 6759885
         repo_id: 1352485172
     'peter-evans/repository-dispatch@28959ce8df70de7be546dd1250a005dd32156697':

.github/workflows/push-email-notify.yml

@@ -40,7 +40,7 @@ jobs:
     timeout-minutes: 5
     steps:
       - name: Send push notification email
-        uses: hyperpolymath/smtp-notify-action@c1c9fa07992a02c1fd3d67a0dc1b08cccb852aef # v0.5.0
+        uses: hyperpolymath/smtp-notify-action@e384daf6167a7a7567642d6a62060106244d2413 # v0.5.1
         with:
           server_address: ${{ secrets.SMTP_HOST }}
           server_port: ${{ secrets.SMTP_PORT }}