Publish flow_runner to public hex.pm instead of the turnio org - #343
Merged
Conversation
flow_runner is AGPL-3.0 OSS, so a dedicated private hex.pm organisation adds no value — it only forces every consumer to authenticate to the org (and ship the org read-key) to fetch a public package. Drop the `organization: "turnio"` from the package config so releases publish to public hex.pm, matching how the `expression` package is already published. Bump to 6.15.1 as the first public release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Why
flow_runneris AGPL-3.0 open source, but it's currently published to the privateturniohex.pm organisation. We get no benefit from that:engage) mustmix hex.organization auth turnioand ship the org read-key just to fetch a public package — the key is currently hardcoded in plaintext across several Dockerfiles.The sibling
expressionpackage (aflow_runnerdependency) is already published to public hex.pm — this change simply bringsflow_runnerin line with it.What
organization: "turnio"frompackage()inmix.exs, somix hex.publish(viareleases.ymlon tag push) targets public hex.pm.flow_runneris currently free on public hex.pm).~> 6.15.1.No org auth is needed in
releases.yml— it already publishes with a user-levelHEX_API_KEY.Rollout
v6.15.1to trigger the release workflow → publishesflow_runnerto public hex.pm.engage: droporganization: "turnio"from the dep, re-pointmix.locktohexpm, and remove allmix hex.organization auth turniocalls + the plaintext read-key from Dockerfiles / Makefile / CI / dependabot.🤖 Generated with Claude Code