chore(deps): bump hyperpolymath/smtp-notify-action from 0.1.0 to 0.2.0 in the actions group (#68)

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.1.0 to 0.2.0
<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.2.0</h2>
<p>Static, byte-reproducible smtp-notify binaries. CI rebuilt them from
this tag and verified they hash to exactly the SHA-256 pins inside this
tag's action.yml before publishing.</p>
</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.3.0 — 2026-09-09</p>
<h1>[IMPORTANT]</h1>
<p><code>main</code> is not a release, and pinning <code>@main</code> is
not supported.</p>
<p>Between a release commit landing on <code>main</code> and its tag
being pushed, <code>action.yml</code>
on <code>main</code> names assets that do not exist yet, so
<code>@main</code> fails at the download
step. This window is unavoidable rather than an oversight: the release
workflow
refuses to publish unless the asset URL <em>in the tagged commit</em>
already names the
tag being released, so the commit must precede the tag. The window is
minutes
long and is one more reason <code>@main</code> is not a supported
ref.</p>
<h1>Pin a tag, or a commit SHA that is an ancestor of one.</h1>
<p>=== Added</p>
<ul>
<li><em>STARTTLS on the submission port.</em> <code>secure: false</code>
or
<code>secure: starttls</code> now starts in the clear on port 587 and
upgrades the
same connection in place per RFC 3207, including the mandatory second
<code>EHLO</code> after the upgrade. The upgrade is not opportunistic: a
server that
does not advertise <code>STARTTLS</code> fails the step, and that check
runs before
the command is sent, so no credential is ever written to a cleartext
stream. Certificate verification is identical on both TLS paths.</li>
<li><em>EHLO capability parsing</em> (issue <a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/9">#9</a>).
The <code>EHLO</code> reply is parsed into a
<code>Capabilities</code> value — <code>STARTTLS</code>, the
<code>AUTH</code> mechanism list (including
the Exchange <code>AUTH=LOGIN</code> spelling), <code>SIZE</code> and
<code>8BITMIME</code> — and an <code>AUTH</code>
failure now names what the server actually advertised. A mechanism
mismatch and a wrong password no longer look alike in the log.</li>
<li>The proven state machine now carries <em>two</em> tables, selected
by transport,
each proven separately: the implicit-TLS table is proven to contain no
upgrade rows, and the STARTTLS table is proven to <em>reach</em> them
from the
start state. A row that is present but unreachable would have
authenticated in the clear while every prior proof stayed green.</li>
<li><em><code>AUTH LOGIN</code>, and mechanism selection</em> (issue <a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/10">#10</a>).
The mechanism is chosen</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/ede1191ef6ff3ac02c4f4d9efdf837ee517e11d7"><code>ede1191</code></a>
docs: restore the &quot;<a
href="https://github.com/main"><code>@​main</code></a> is not a
release&quot; statement, and say why (<a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/15">#15</a>)</li>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/ea60deb9677c6c6b704c0477cb19de8829f1f50b"><code>ea60deb</code></a>
release: v0.2.0 — action.yml fetches the fixed binaries (<a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/14">#14</a>)</li>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/93ee7573240bb8d7645a8f2ad505ee7ef0795f90"><code>93ee757</code></a>
docs: security policy, contributing guide and changelog (<a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/13">#13</a>)</li>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/4077691bdd4bb01891868b35971bc270004260e5"><code>4077691</code></a>
fix: fail-closed transport, OS gate, server reply text, whole-run
watchdog (<a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/12">#12</a>)</li>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/573018073e48d16aa40c8380f483401a4d95adc2"><code>5730180</code></a>
docs: defect registers — Bustfile (dependencies) and known defects
(ours) (<a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/11">#11</a>)</li>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/f3d5c1ae8d88c47095ec954998bd372fabc4f777"><code>f3d5c1a</code></a>
docs: migration guide from dawidd6/action-send-mail (<a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/8">#8</a>)</li>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/6d6147eb95630efab006a1355f3f112ee6f2be56"><code>6d6147e</code></a>
docs: describe the dawidd6 relationship honestly (<a
href="https://redirect.github.com/hyperpolymath/smtp-notify-action/issues/7">#7</a>)</li>
<li><a
href="https://github.com/hyperpolymath/smtp-notify-action/commit/f9809b102dbd1beb4d4eb30f4064d2fb5683435b"><code>f9809b1</code></a>
fix(ci): strip CRLF from mailpit raw fetch before whole-line greps</li>
<li>See full diff in <a
href="https://github.com/hyperpolymath/smtp-notify-action/compare/1b3b752d39a4fe4c0f28f10905e4608789d3e050...ede1191ef6ff3ac02c4f4d9efdf837ee517e11d7">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.1.0&new-version=0.2.0)](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/push-email-notify.yml

@@ -23,7 +23,7 @@ jobs:
     timeout-minutes: 5
     steps:
       - name: Send push notification email
-        uses: hyperpolymath/smtp-notify-action@1b3b752d39a4fe4c0f28f10905e4608789d3e050 # v0.1.0
+        uses: hyperpolymath/smtp-notify-action@ede1191ef6ff3ac02c4f4d9efdf837ee517e11d7 # v0.2.0
         with:
           server_address: ${{ secrets.SMTP_HOST }}
           server_port: ${{ secrets.SMTP_PORT }}