Repository navigation
chore(entity-mapping-client): mappings:validate / validate-flow, block_id - #616
Merged
Merged
Conversation
- validateMapping / validateMappingFlow (mappings:validate, mappings:validate-flow) - block_id on journey mapping sources - queryMappingHistory removed (endpoint removed in entity-mapping-api) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0122KFtFiMcCXxE3nkAHyUYE
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
Updates
@epilot/entity-mapping-clientto the current entity-mapping-api spec (0.10.5 → 0.11.0). On merge, CI regenerates and releases@epilot/sdkand@epilot/cli, so agents using the SDK or the epilot CLI can call the new mapping check.validateMapping(POST /v1/mappings:validate) andvalidateMappingFlow(POST /v1/mappings:validate-flow), both read-only: check map-entity mappings against their source (a journey byjourney_id, or an entity schema) before saving (entity-mapping-api!255, in prod since 2026-11-17)block_idon journey mapping sourcesqueryMappingHistory(GET /v1/mappings/history) removed; the endpoint itself was removed in entity-mapping-api!252, so calls already fail. Hence the minor bump.How it was generated
docs.api.epilot.ioisn't reachable from the environment this was made in, so the spec was built the way entity-mapping-api'spublish-openapistep builds the published file (openapicmd read --server https://entity-mapping.sls.epilot.io --exclude-ext x-internalonopenapi.ymlfrom main), thenupdate-openapi.js+typegen+build. Re-runningnpm run openapiagainst the published spec should give the sameopenapi.json.Test plan
npm run buildand the client's vitest (3 passed);biome checkcleanvalidateMapping, +validateMappingFlow, −queryMappingHistory, nothing elseGenerated by Claude Code