Asana breaking change: POST /goals/{goal_gid}/addFollowers
removed `subschema #1, subschema #2` from the `data` response property `allOf` list for the response status `200`
Specification capture: . Published evidence last updated . This is captured contract evidence, not an observed outage or a result from scanning your code.
Which field and classification rule changed?
- Changed field
allOf- Rule ID
response.removed- Classifier version
2026-10-15.2- Direction
- response
- Finding ID
chg_e350275a7339b64537e6bd861e4611deff2496b68af91ff9644627bcc741a6e5
What is the recorded before and after evidence?
Previous specification SHA-256: 1cdf33603c6d8783ff56573066928065a63ee202a7e22200bc58922079aab289
Revised specification SHA-256: e418c0c7538e75757bc03ec8fd90da5a27afc0e0a2b52b64cdfb5f5e8322f366
Publisher version: 1.0 to 1.0.
...
x-insert-after: false
html_notes:
- description: The notes of the goal with formatting as HTML.
+ description: The notes of the goal with formatting as HTML. See [rich
+ text](/docs/rich-text).
example: <body>Start building brand awareness.</body>
type: string
...
of the text value of a custom
field, corresponding to the
- `text_value` plain-text field."
+ `text_value` plain-text field.
+ See [rich
+ text](/docs/rich-text#reading-r\
+ ich-text)."
example: <body>Some Value</body>
nullable: true
...Inspect the complete release · Public source findings · Publisher specification source
How do I check whether this affects my code?
Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.
Check an authorized repository · Review coverage · Inspect classification rules