Prepares the statifier_oban 0.1.0 Hex release - #23
Merged
Conversation
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
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). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/0anddocs/0added; version stays 0.1.0 (no bump - none needed, and version moves are the operator's here).{:statifier, "~> 2.0"};STATIFIER_PATHoverride unchanged.CHANGELOG.mdcreated;[0.1.0]assembled from the five fragments, fragments deleted.Gate green with
STATIFIER_PATHat the 2.0.0 release branch (84 tests, 95.3% coverage). Before merge:mix deps.get(no override) to movemix.lock's statifier entry to the Hex release, gate re-run. After merge: tagv0.1.0,mix hex.publish(operator).