fix: update source URL to genagent org#42
Merged
joshrotenberg merged 1 commit intomainfrom Apr 11, 2026
Merged
Conversation
Repository moved from joshrotenberg/codex_wrapper_ex to genagent/codex_wrapper_ex as part of consolidating the GenAgent ecosystem under a dedicated org. Update package metadata and README badge URLs so the hex package and CI badge reflect the canonical location. GitHub auto-redirects from the old URL so existing published versions remain reachable.
This was referenced Apr 11, 2026
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.
Summary
Repository moved from `joshrotenberg/codex_wrapper_ex` to
`genagent/codex_wrapper_ex` as part of consolidating the
GenAgent ecosystem under a dedicated org. Update package
metadata and README badges so the next published release
reflects the canonical location.
Files
package `links:`)
Why a patch release?
GitHub auto-redirects from the old URL, so existing published
versions remain reachable and there's no user-visible break.
But the stale URL is baked into the hex package metadata for
v0.2.2 -- the only way to correct it is to publish a new
version. Using `fix:` prefix so release-please cuts 0.2.3.