Skip to content

Prepares the statifier_oban 0.1.0 Hex release - #23

Merged
johnnyt merged 2 commits into
mainfrom
sob-qyl-hex-release
Aug 23, 2026
Merged

Prepares the statifier_oban 0.1.0 Hex release#23
johnnyt merged 2 commits into
mainfrom
sob-qyl-hex-release

Conversation

@johnnyt

@johnnyt johnnyt commented Aug 23, 2026

Copy link
Copy Markdown
Member

Works sob-qyl, under the operator's release-campaign consent given in session 2026-08-22 ("release these as hex packages ... satellites at 0.1.0"). Blocked on statifier 2.0.0 reaching Hex (riddler/statifier-ex#222): the dep swaps to {:statifier, "~> 2.0"} here, and Hex refuses to publish over a git dep.

  • package/0 and docs/0 added; version stays 0.1.0 (no bump - none needed, and version moves are the operator's here).
  • Engine dep default arm: git pin -> {:statifier, "~> 2.0"}; STATIFIER_PATH override unchanged.
  • CHANGELOG.md created; [0.1.0] assembled from the five fragments, fragments deleted.
  • README gains an install section; the stale "scaffold only" Status paragraph now describes what shipped (durable delayed sends end to end, the invoke handler base).

Gate green with STATIFIER_PATH at the 2.0.0 release branch (84 tests, 95.3% coverage). Before merge: mix deps.get (no override) to move mix.lock's statifier entry to the Hex release, gate re-run. After merge: tag v0.1.0, mix hex.publish (operator).

Adds package/0 (statifier_oban, MIT, lib + mix.exs + README + LICENSE +
CHANGELOG in the tarball) and the docs/0 hexdocs configuration (README
landing page, the ADR set). The version was already 0.1.0 and does not
move.

The engine dependency's default arm swaps from the git pin to
{:statifier, "~> 2.0"} - statifier 2.0.0 is on Hex, ending the pin
arrangement (st-ADR-0066) - with the STATIFIER_PATH override unchanged,
and the mix.exs comment explaining why the package could not ship goes
with the pin.

CHANGELOG.md is created with the [0.1.0] section assembled from the
five changelog.d/ fragments, deleted here per the fragment protocol.
README gains an install section, and its Status paragraph - still
claiming "nothing is implemented yet, scaffold only" - is updated to
what actually shipped: delayed sends through Oban end to end, and the
Oban-backed invoke handler base.

Before merge, once statifier 2.0.0 is live on Hex, mix deps.get
refreshes mix.lock's statifier entry from the git pin to the Hex release
and the gate re-runs without the STATIFIER_PATH override. Tagging v0.1.0
and mix hex.publish stay the operator's actions after merge.

Refs: sob-qyl
statifier 2.0.0 is live on Hex, so mix.lock's engine entry moves from
the git pin to the Hex release, and the gate runs green against it with
no STATIFIER_PATH override - the pre-merge step the release PR named.

Refs: sob-qyl
@johnnyt

johnnyt commented Aug 23, 2026

Copy link
Copy Markdown
Member Author

statifier 2.0.0 is live on Hex - mix.lock now locks the Hex release and the full gate is green with no override: 84 tests, 95.3% coverage. Ready to merge; after merge: tag v0.1.0, mix hex.publish (operator).

@johnnyt
johnnyt merged commit a2d10e7 into main Aug 23, 2026
1 check passed
@johnnyt
johnnyt deleted the sob-qyl-hex-release branch August 23, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant