Repository navigation
Move OneTaxonomy to the @extantape scope and ExtantApe repo - #43
Merged
Merged
Conversation
EXTANT APE owns the One tools, so the packages publish under @ExtantApe from 0.1.0-alpha.4 and the repo lives at ExtantApe/OneTaxonomy. This does for OneTaxonomy what OnePedigree already did. All six packages are renamed and bumped in lockstep, every GitHub URL points at the ExtantApe repos, and the Release workflow and RELEASING.md name the mdgilardi npm account. Text that named the old owner or the site that used the tool now says EXTANT APE or uses neutral words, and old task and decision numbers are gone from docs, comments and test names. The shared brand files are copied again so they match OnePedigree byte for byte, and the lock is updated. The example site's import map was regenerated with payload generate:importmap. Kept on purpose: the Mac app's identifier, which still carries the old name, because changing it resets people's settings, and the brand guidelines' line about app identifiers, which is a shared file. The license is unchanged. Tested: build, typecheck, 633 tests, the example site's smoke test (74 checks), the leak check and the OneOrigin check, which warns as expected that the brand source differs until OnePhylogeny moves too. Nothing is published: the @ExtantApe packages need their first release staged and approved. Co-Authored-By: Claude Opus 5.5 <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
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.
Moves OneTaxonomy to EXTANT APE: the packages publish under
@extantapefrom 0.1.0-alpha.4, and the repo lives at ExtantApe/OneTaxonomy. It matches what OnePedigree did in ExtantApe/OnePedigree#41.@extantape/and bumped in lockstep to 0.1.0-alpha.4. Imports, tsconfig paths, examples and apps follow,pnpm-lock.yamlcomes frompnpm install, and the example site's import map was regenerated withpayload generate:importmap.repository,homepageandbugsfields.mdgilardinpm account and drop the old platform repo's sync step.Kept on purpose: the Mac app's identifier in
apps/studio/src-tauri/tauri.conf.json, since changing it resets people's settings, and the shared brand guidelines' line about app identifiers. The license is unchanged.Tested locally: build, typecheck, 633 tests, the example site's smoke test (74 checks), the leak check and
node scripts/oneorigin.mjs check, which warns as expected that the brand source differs until OnePhylogeny moves. Nothing is published or tagged.🤖 Generated with Claude Code