chore(release): v0.7.2 — Duffel Cars + auto-publish + post-#93 fix#100
Merged
Conversation
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>
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
Patch bump off v0.7.1. Three pieces of substantive work since v0.7.1, all merged green individually:
@otaip/adapter-duffelgains the Cars API (search → quote → book → get → cancel). Three-step flow, geo-coordinate based, same Bearer +Duffel-Versionheaders as flights. 8 openDOMAIN_QUESTIONmarkers (DQ-C1..C8) captured indocs/knowledge-base/cars.md.@otaip/corethrough itspackage.jsonexportsmap →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.gh release createtoRELEASE_PATsorelease: publishedevents propagate to the Publish workflow. This is the first release that should auto-publish to npm without a manual workflow_dispatch.What npm sees
@otaip/adapter-duffel@0.7.2for the first time —@otaip/adapter-duffelwas already at 0.7.2 in source (#99) but unpublished until this release tag fires.Files changed
package.jsonfiles bumped0.7.1 → 0.7.2(root + 16 workspace +@otaip/platform-ui;@otaip/adapter-duffelwas already at 0.7.2).CHANGELOG.md— new## 0.7.2entry covering feat(adapter-duffel): add Cars API (search → quote → book) v0.7.2 #99, fix(release): unbreak Release workflow's Count agents step #97, ci(release): use RELEASE_PAT so Publish workflow auto-fires #98.VERSIONING.md— next-release pointer updated tov0.7.3.Test plan
pnpm -r typecheck— clean.RELEASE_PATwired up. Expected chain:v0.7.2tag + GitHub release.release: publishedevent auto-fires Publish workflow.npm view @otaip/core versionreturns0.7.2.npm view @otaip/adapter-duffel versionreturns0.7.2(Cars now consumable from npm).If the chain breaks: check
RELEASE_PAThasn't expired or lostContents: write; manualgh workflow run publish.ymlis the fallback.🤖 Generated with Claude Code