chore(journey-client): serve a published revision by id - #490
Draft
stewarthsoj wants to merge 1 commit into
Draft
Conversation
Regenerates the journey client from journey-config spec 1.6.0: getJourney takes an optional revision_id and answers with the revision the served configuration came from. getJourneyV2 is unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0123k71emMcLvapztKWqmRTe
stewarthsoj
changed the title
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
1 participant
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
Regenerates
@epilot/journey-clientfrom journey-config spec1.6.0, so the runtime can ask for a specific published revision.The
apps/journey-app-v3pins a save-and-continue session to the revision it started on and refetches with thatrevision_idon resume.What changed
clients/journey-clientregenerated:getJourneytakes an optionalrevision_idquery parameter, and its200response gainsrevision_id(a newJourneyServedRevisionschema in the responseallOf).0.7.0→0.8.0(minor — one parameter and one response field added, nothing changed), CHANGELOG entry and a changeset for the aggregate@epilot/sdkminor.packages/epilot-sdk-v2regenerated for the journey API (types, compact definition, docs). Only journey files changed this run.getJourneycarries therevision_idparameter.Test plan
openapi(local spec) →typegen→typescript→bundle-definitionclean;info.version1.6.0,getJourneyparametersid, version, revision_id, source, orgId, prod server URL preserved.vitestgreen in the client (4 tests, incl. the new parameter assertion);pnpm lint(biome) clean across 524 files.getJourneyV2verified unchanged — norevision_idparameter, norevision_idin its response — so config-engine, Configuration Hub and blueprint-manifest-api are unaffected.0.8.0and callgetJourney({ id, revision_id })from the builder against dev for a typed response — same gate.