Skip to content

chore(deps): bump hyperpolymath/smtp-notify-action from 0.5.0 to 0.5.1 - #24

Merged
hyperpolymath merged 1 commit into
mainfrom
dependabot/github_actions/hyperpolymath/smtp-notify-action-0.5.1
Nov 2, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
dependabot/github_actions/hyperpolymath/smtp-notify-action-0.5.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026

Copy link
Copy Markdown
Contributor

Bumps hyperpolymath/smtp-notify-action from 0.5.0 to 0.5.1.

Release notes

Sourced from hyperpolymath/smtp-notify-action's releases.

v0.5.1

Protocol-neutral server_address metadata

server_address is the host input for both SMTP and NNTP, and remained the only input in action.yml still described as SMTP-only ('SMTP server host name'). It now reads:

description: 'Server host name (SMTP or NNTP, per protocol: `protocol`)'

The secure and diagnose folded scalar descriptions were also rewrapped to line width (Reports → reports after the colon in diagnose), and the download URL in action.yml now points to v0.5.1.

Because workflow editors, consumers, and GitHub Marketplace read action.yml from the release tag — and tags are immutable here — this ships as v0.5.1 rather than moving v0.5.0. v0.5.0 remains supported in SECURITY.md since the binary and input surface are unchanged.

For the full NNTP posting (protocol: nntp, newsgroups) and Marketplace readiness notes introduced in the 0.5 series, see v0.5.0 and CHANGELOG.adoc.

Provenance

Zero Zig or Idris2 source files changed between v0.5.0 and v0.5.1. CI rebuilt both static musl binaries from this tag and verified they hash byte-identically to the unchanged SHA-256 pins inside action.yml before publishing. SHA256SUMS is attached:

2683da8f619dd5f310c9f6884da39e825c807c2c86a6319c19aba39b27f9c5c9  smtp-notify-x86_64-linux-musl
a58138308fb9832e1ceb551a12f1b04e591dc38ba5fd336c9acfb3f263161f29  smtp-notify-aarch64-linux-musl
Changelog

Sourced from hyperpolymath/smtp-notify-action's changelog.

== v0.5.1 — 2026-10-24

A metadata correction, and the release to publish the Marketplace listing from. The binary is byte-identical 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 action.yml from the tag, which is the same property that made v0.5.0 necessary in the first place.

NOTE: The v0.5.0 heading below carries a note that the tag had to be pushed immediately after its merge. That was done, and the release published the same day; the note is left in place because it describes a property of the release process, not a pending task.

=== Fixed

  • server_address is no longer described as SMTP-only. The field is the host for both protocols, and the description said 'SMTP server host name' — the last input description that still read as if the news transport did not exist. It now reads 'Server host name (SMTP or NNTP, per protocol: protocol)'. Cosmetic, but workflow editors and consumers read action.yml from the release ref, which is why it ships as a new tag rather than a main-only edit.

=== Changed

  • The asset URL names v0.5.1. The pins do not move: the binary did not change.
  • The secure and diagnose input descriptions were rewrapped to the file's line width (and Reports lowercased after the colon in diagnose).
  • README.adoc's three pinned examples and .github/SECURITY.md's supported-versions table follow the current release.
Commits
  • e384daf fix(action): protocol-neutral server_address wording (needs tag v0.5.1) (#28)
  • See full diff in compare view

Dependabot compatibility score

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 commands and options

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [hyperpolymath/smtp-notify-action](https://github.com/hyperpolymath/smtp-notify-action) from 0.5.0 to 0.5.1.
- [Release notes](https://github.com/hyperpolymath/smtp-notify-action/releases)
- [Changelog](https://github.com/hyperpolymath/smtp-notify-action/blob/main/CHANGELOG.adoc)
- [Commits](hyperpolymath/smtp-notify-action@v0.5.0...v0.5.1)

---
updated-dependencies:
- dependency-name: hyperpolymath/smtp-notify-action
  dependency-version: 0.5.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 2, 2026
@coderabbitai

coderabbitai Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: e81c9d59-efbd-47de-8317-29cc363f6239

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@hyperpolymath
hyperpolymath enabled auto-merge (squash) November 2, 2026 19:18
@hyperpolymath
hyperpolymath merged commit f0f7896 into main Nov 2, 2026
4 checks passed
@hyperpolymath
hyperpolymath deleted the dependabot/github_actions/hyperpolymath/smtp-notify-action-0.5.1 branch November 2, 2026 19:18
hyperpolymath added a commit that referenced this pull request Nov 2, 2026
Carry forward Dependabot PR #24 (smtp-notify-action v0.5.1), repoint the secret-scanner reusable to the canonical metadatastician/standards slug, remove unnecessary secrets inheritance, reconcile actions.lock and the inline pin, and add workflow-contract regression checks. Includes the D199 implementation handoff and the open-work audit. No admin bypass, force-push, or required-context removal.
hyperpolymath added a commit that referenced this pull request Nov 2, 2026
Temporarily take main's versions of actions.lock and push-email-notify.yml so the merged PR #24 can be merged into this branch without a force-push. The follow-up commit reapplies the repaired lockfile and inline SHA.
hyperpolymath added a commit that referenced this pull request Nov 3, 2026
…kflow contracts (#25)

Follow-up to #24.

## What this fixes

- Repairs the Secret Scanner startup failure. The canonical
`metadatastician/standards` reusable workflow is blocked by this
repository's Actions allowlist, and GitHub Actions does not follow the
pre-transfer `hyperpolymath/standards` redirect for job-level `uses:`.
This PR vendors the canonical scanner locally at standards SHA
`8d1a2aab4211493cf42f147f2080f024605797dc`, pins the estate-baseline
fetches explicitly, and preserves the required check context `scan /
gitleaks`.
- Repairs `actions.lock` for `gh-actions-lock` v0.4.0: no synthetic
reusable-workflow lock edges, vendored scanner checkout uses are locked,
SMTP inline SHA matches the lockfile.
- Adds YAML-aware workflow contract checks and regression fixtures for
moved reusable owners, floating pins, SPDX-first headers, missing lock
entries, synthetic reusable-only lock edges, floating/stale SMTP refs,
and the local vendored scanner allowlist contract.
- Disables CodeRabbit finishing-touches autofix/CI-fix/merge-conflict
writes in `.coderabbit.yaml`.
- Reconciles with `main` without force-push: signed alignment commit,
GitHub update-branch merge, then signed reapply of the repaired files.

## Verification at `49939bb7930eaf38512d83f962267b7acb89ee6f`

- `scan / gitleaks`: SUCCESS
- `scan / rust-secrets`: SUCCESS
- `scan / shell-secrets`: SUCCESS
- `Workflow and lock contracts`: SUCCESS
- CodeQL / Analyze (actions) / GitGuardian / semgrep: SUCCESS
- Local contract fixtures: 15 passed, 0 failed
- All review threads resolved; stale CodeRabbit CHANGES_REQUESTED review
dismissed.

## Merge blocker

`gh pr merge 25 --squash` is refused by base-branch policy. The PR
history still contains unsigned CodeRabbit commit
`60e9736c27b38f48f3a67e3c1fd7adb377102c50`; `required_signatures` has no
bypass actors. Signed child commits, reverts, and merge commits do not
remove that unsigned ancestor.

Policy-compliant recovery is to recreate the branch from `main` with
signed cherry-picks and open a replacement PR, then close this one. This
session is constrained to the existing branch and must not force-push or
use administrator bypass.

---------

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants