Skip to content

chore(deps): bump the actions group across 1 directory with 2 updates - #100

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions-8ae9248a72
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions-8ae9248a72

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the actions group with 2 updates in the / directory: julia-actions/setup-julia and hyperpolymath/smtp-notify-action.

Updates julia-actions/setup-julia from 3.0.2 to 3.0.3

Release notes

Sourced from julia-actions/setup-julia's releases.

v3.0.3

What's Changed

  • We upgraded from NodeJS 24.13.0 to 24.14.1 (but still stayed on NodeJS v24). We don't expect this to have any breaking effect on users.
  • We updated some of our dependencies.
  • We set a 7-day dependency cooldown on our dependencies.
  • We made changes to our documentation.

New Contributors

Full Changelog

Full Changelog: julia-actions/setup-julia@v3.0.2...v3.0.3

Commits

Updates hyperpolymath/smtp-notify-action from 0.3.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

v0.5.0

Newsgroup posting, on the same binary

protocol: nntp with newsgroups posts one article over implicit TLS (NNTPS, 563) or STARTTLS on the news port (RFC 4642, 119), authenticating with AUTHINFO USER/PASS. Transport selection is fail-closed and unchanged in shape from the SMTP path: a server that does not advertise the upgrade is refused before any credential is written.

Refusals name their own reason, including the two 4xx codes that are not retries — 440 at POST and 441 at the article, where a class-only rule would have advised a retry and duplicated the post. Malformed newsgroups and CR/LF in a header-bound value are refused before the socket is opened. The body is dot-stuffed on the wire and a Message-ID is generated per run.

The NNTP session is a second proven contract — spec/Nntp/ (6 rows implicit, 8 with STARTTLS, plus the Newsgroups grammar and newsgroupsNoInjection) — emitted into the same src/generated/smtp_fsm.zig, so the existing drift gate covers it. The SMTP section of that file is unchanged.

The Marketplace listing can finally be published

The publish form refuses a description of 125 characters or more (measured on the parsed value, so a folded scalar does not hide it) and reads action.yml from the release tag — which is why this ships as a tag rather than a commit on main. The description is now 110 characters with STARTTLS and 365 in it; the full text lives in the README, which the listing page renders. scripts/check-action.sh and the action-metadata job keep the limit from regressing, with a selftest proving 125 is refused and 124 accepted.

server_port now defaults to empty, meaning the port the protocol and transport imply: SMTP 465/587/25, NNTP 563/119.

Provenance

CI rebuilt both static musl binaries from this tag and verified they hash to exactly the SHA-256 pins inside this tag's action.yml before publishing. SHA256SUMS is attached:

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

See CHANGELOG.adoc for the full entry, and KNOWN-DEFECTS.adoc for what is not proven — notably D-015: no real news server has ever seen this code; the end-to-end evidence is a containerised fixture.

... (truncated)

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.

== v0.5.0 — 2026-10-04

Newsgroup posting, and the release that can finally be listed on the GitHub Marketplace. The two are one release because the description fix can only take effect from a tag — the Marketplace validates action.yml at the release's tag, not on main — and a tag is what this release is for.

NOTE: The tag must be pushed immediately after this merge. Between the two, the tagged commit's action.yml names v0.5.0 assets that do not exist yet, and @main inherits that window; the release workflow refuses to publish unless the asset URL equals the tag, so the window is a property of the release process rather than of this tree. If the tag lands on a later day, correct this heading with a follow-up commit, as was done for v0.4.0.

=== Added

  • protocol input (smtp | nntp, default smtp), chosen explicitly and

... (truncated)

Commits
  • e384daf fix(action): protocol-neutral server_address wording (needs tag v0.5.1) (#28)
  • c1c9fa0 feat(nntp): NNTP posting + unblock the Marketplace listing (needs tag v0.5.0)...
  • 7ea6d7a docs(changelog): date v0.4.0 at its actual tag push (#26)
  • 170f53a ci(secret-scan): canonical estate scanner caller, key scan (D243) (#25)
  • 9f3f89f docs: add Signed commits section to CONTRIBUTING (#24)
  • acd2d3d fix: address CodeRabbit review of #21 — CertificateRequest shape checks, benc...
  • c9b6790 fix: CodeRabbit auto-fixes for PR #21 (#22)
  • 10f080a fix/issue 6 hardening (#21)
  • 5574cdc Resolve community health, accessibility, diagnostics, and benchmark debt
  • 106e28f fix(ci): reconcile the workflows with actions.lock (gh-actions-lock) (#19)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Oct 25, 2026
@coderabbitai

coderabbitai Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

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: 812d51d2-33cb-43ea-8b22-ccf0d62f035e

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

Bumps the actions group with 2 updates in the / directory: [julia-actions/setup-julia](https://github.com/julia-actions/setup-julia) and [hyperpolymath/smtp-notify-action](https://github.com/hyperpolymath/smtp-notify-action).


Updates `julia-actions/setup-julia` from 3.0.2 to 3.0.3
- [Release notes](https://github.com/julia-actions/setup-julia/releases)
- [Commits](julia-actions/setup-julia@v3.0.2...v3.0.3)

Updates `hyperpolymath/smtp-notify-action` from 0.3.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.3.0...v0.5.1)

---
updated-dependencies:
- dependency-name: hyperpolymath/smtp-notify-action
  dependency-version: 0.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: julia-actions/setup-julia
  dependency-version: 3.0.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions-8ae9248a72 branch from cf24c0e to b5eeb60 Compare November 15, 2026 18:34
@sonarqubecloud

Copy link
Copy Markdown

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.

0 participants