fix(solutions): cross-team-bug-relay v0.1.3 — add required id to input schema - #91
Merged
Merged
Conversation
…t schema The platform's JsonSchema config object requires a top-level id: field; schemas/bug-relay-input.yaml only carried lookup_key, so every 'import solution cross-team-bug-relay' failed with 'Required string value is missing for field id' — the released v0.1.2 bundle is un-importable. Adds the id, bumps the sample to v0.1.3, regenerates samples.json. Caught by firstlanding's new solution install-flow e2e matrix, which imports and provisions every solution-kind catalog sample. Co-Authored-By: Claude Fable 5 <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
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.
What changed
schemas/bug-relay-input.yamlgains the top-levelid:field the platform'sJsonSchemaconfig object requires. Without it, everyimport solution cross-team-bug-relayfails withRequired string value is missing for field 'id'— the released v0.1.2 bundle is un-importable, which also blocks installing the catalog's first AutomationTemplate. The sample is bumped to v0.1.3 andsamples.jsonregenerated (archastro create solutionmanifest).Same defect exists in the not-yet-merged
cross-org-migration-scopesample; that one-line fix was pushed to its own draft PR #90 branch.How it was caught
firstlanding's new solution install-flow e2e matrix (PR 3 of the webhooks/automations privacy plan) imports and provisions every solution-kind catalog sample. Its first run failed on exactly the two samples shipping
schemas/*.yamlwithoutid:.Testing
id:added,import solution cross-team-bug-relaysucceeds against a local platform, and installing all three templates (Bug Reporter, Bug Resolver agents + the Cross-Team Bug Relay automation) provisions cleanly — verified via the firstlandingsolution_matrixsynthetics suite running against this checkout (ARCHASTRO_SAMPLES_DIR).scripts/build-releases.sh --only cross-team-bug-relaypacks v0.1.3 green.Note: the automation install additionally needs the firstlanding-side
AutomationProvisionerorg-resolution fix (onfeat/solution-install-e2e-matrix) when the installer is an org-less developer/S2S caller; org-user installs work without it.🤖 Generated with Claude Code