fix(release): unbreak Release workflow's Count agents step#97
Merged
Conversation
#93 moved discoverAgents into @otaip/core and made the CLI a re-export. scripts/count-agents.ts still imported via the CLI, so the indirection forced tsx to resolve `@otaip/core` through its package.json exports map — which points at `./dist/index.js`. The Release workflow runs this script before any build, so the file doesn't exist: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in .../packages/cli/node_modules/@otaip/core/package.json Result: every push-to-main since #93 has failed the Release workflow's "Count agents" step, which means v0.7.0 → v0.7.1 hasn't been tagged or published. Visible to users as "GitHub still shows 0.7.0" + npm still on 0.7.0 for non-hotelbeds packages. Fix: import discoverAgents directly from its source path `packages/core/src/discovery/agent-discovery.js` so tsx walks files instead of resolving a package specifier. The CLI keeps its re-export — every external consumer of `@otaip/cli` is unaffected. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
ntbpy
pushed a commit
to ntbpy/AI_Agent_otaip
that referenced
this pull request
May 11, 2026
fix Patch bump off v0.7.1. Three pieces: - TelivityAI#99 @otaip/adapter-duffel adds Cars (search → quote → book → get → cancel) under /cars/. Same Bearer auth, AbortSignal threading on request(). 8 open DOMAIN_QUESTIONs captured in docs/knowledge-base/cars.md. - TelivityAI#97 unbreaks the Release workflow's Count agents step that TelivityAI#93's CLI re-export indirection broke. Every push-to-main since TelivityAI#93 had been failing silently — that's why v0.7.1's tag was created but the workspace npm bumps lagged behind for a while. - TelivityAI#98 switches gh release create to RELEASE_PAT so the release: published event propagates to the Publish workflow. This is the first release that should auto-publish to npm without a manual workflow_dispatch. Workspace-wide bump: 17 package.json files 0.7.1 → 0.7.2 (@otaip/adapter-duffel was already at 0.7.2 from TelivityAI#99). Going forward, the next release is v0.7.3. See CHANGELOG.md for details. Co-Authored-By: Claude Opus 4.7 (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
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
Hotfix: every push-to-main since #93 (incl. #95 and #96) has failed the Release workflow's Count agents step. Result: v0.7.1 hasn't been tagged or published despite #96 being merged, and the GitHub front page still shows v0.7.0.
Root cause
#93 moved
discoverAgentsinto@otaip/coreand made the CLI a re-export.scripts/count-agents.tsimports through the CLI, so the indirection now forces tsx to resolve@otaip/corethrough itspackage.jsonexportsmap — which points at./dist/index.js. The Release workflow's Count agents step runs before any build, so the file doesn't exist:Fix
Import
discoverAgentsdirectly frompackages/core/src/discovery/agent-discovery.jsso tsx walks files instead of resolving a package specifier. The CLI keeps its re-export untouched — every external consumer of@otaip/cliis unaffected.Test plan
v0.7.1→ triggersPublish to npm→npm view @otaip/core versionreturns0.7.1.🤖 Generated with Claude Code