Commit generated clients + Hex release story#2
Merged
Conversation
- Un-ignore client source (clients/ is committed now) so hex.pm source links resolve and published versions are reproducible; each client's _build/deps/mix.lock stay ignored per-client. - Generator preserves each client's mix.exs @Version across regenerations (was hardcoded 0.1.0 and clobbered every regen), so release bumps persist. - Client mix.exs gains a GitHub source_url + link. - New `mix googly.release [Name] [--minor|--no-bump]`: bump + mix hex.publish (package + ExDoc) per client, authed via HEX_API_KEY. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…googly_document_ai) Generated source is now tracked (see prior commit). Regenerate with `mix googly.generate`; never hand-edit. 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Sets up the Hex release story for the generated clients.
clients/un-ignored) so hex.pm "source" links resolve and published versions are reproducible/auditable. Each client's_build/deps/mix.lockstay ignored per-client.mix.exs@versionacross regenerations (it was hardcoded0.1.0and clobbered on everymix googly.generate), so release bumps stick. Verified: a bumped version survives a regenerate.mix.exsmetadata: added a GitHubsource_url+ link.mix googly.release [Name] [--minor|--no-bump]: bumps the version (patch default),mix deps.get, thenmix hex.publish --yes(package + ExDoc) per client, authed viaHEX_API_KEY.Release flow
Testing
mix test— 60 passing.googly_cloud_storagecompiles with--warnings-as-errors.@versionsurvives regeneration and per-client build artifacts stay gitignored.The second commit is the 747-file generated client source (auto-generated — never hand-edited).