Skip to content

chore(release): v0.7.2 — Duffel Cars + auto-publish + post-#93 fix#100

Merged
telivity-otaip merged 1 commit into
mainfrom
release/v0.7.2
May 7, 2026
Merged

chore(release): v0.7.2 — Duffel Cars + auto-publish + post-#93 fix#100
telivity-otaip merged 1 commit into
mainfrom
release/v0.7.2

Conversation

@telivity-otaip
Copy link
Copy Markdown
Collaborator

@telivity-otaip telivity-otaip commented May 7, 2026

Summary

Patch bump off v0.7.1. Three pieces of substantive work since v0.7.1, all merged green individually:

  • #99@otaip/adapter-duffel gains the Cars API (search → quote → book → get → cancel). Three-step flow, geo-coordinate based, same Bearer + Duffel-Version headers as flights. 8 open DOMAIN_QUESTION markers (DQ-C1..C8) captured in docs/knowledge-base/cars.md.
  • #97 — Hotfix that unbroke the Release workflow's Count agents step. feat(platform-ui): add Platform UI dashboard + developer playground #93's CLI re-export indirection was forcing tsx to resolve @otaip/core through its package.json exports map → dist/index.js (missing on the runner) → ERR_PACKAGE_PATH_NOT_EXPORTED. Every push-to-main since feat(platform-ui): add Platform UI dashboard + developer playground #93 was silently failing the Release workflow.
  • #98 — Switched gh release create to RELEASE_PAT so release: published events propagate to the Publish workflow. This is the first release that should auto-publish to npm without a manual workflow_dispatch.

What npm sees

  • All 16 published packages bump 0.7.1 → 0.7.2.
  • The Cars surface lands on @otaip/adapter-duffel@0.7.2 for the first time — @otaip/adapter-duffel was already at 0.7.2 in source (#99) but unpublished until this release tag fires.

Files changed

Test plan

  • pnpm -r typecheck — clean.
  • No source changes — purely version + docs.
  • On merge: this is the first release with RELEASE_PAT wired up. Expected chain:
    1. Release workflow runs on the merge commit → creates v0.7.2 tag + GitHub release.
    2. release: published event auto-fires Publish workflow.
    3. npm view @otaip/core version returns 0.7.2. npm view @otaip/adapter-duffel version returns 0.7.2 (Cars now consumable from npm).

If the chain breaks: check RELEASE_PAT hasn't expired or lost Contents: write; manual gh workflow run publish.yml is the fallback.

🤖 Generated with Claude Code

Patch bump off v0.7.1. Three pieces:

- #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.
- #97 unbreaks the Release workflow's Count agents step that #93's
  CLI re-export indirection broke. Every push-to-main since #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.
- #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 #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>
@telivity-otaip telivity-otaip merged commit b19b1dd into main May 7, 2026
1 check passed
@telivity-otaip telivity-otaip deleted the release/v0.7.2 branch May 7, 2026 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant