Propagate tag schema changes to API versions 2.7-2.15 #364
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.
Why?
PR #360 updated the Unstable spec with
applied_at/applied_bynullable fields andtag_basicschema changes, but the backend PR (intercom/intercom#468217) changed v3 controllers that serve all API versions. Versions 2.7-2.15 were out of sync with what the API actually returns.How?
Applied the same five changes from Unstable to all stable versions (2.7-2.15): made
applied_at/applied_bynullable in the tag schema, addedtag_basicschema where missing, switched workspace tag endpoints to referencetag_basic, fixed a pre-existing double-nesteditemsbug in the company tags schema, and addedapplied_at/applied_byto entity tag endpoint examples.Generated with Claude Code