Get portfolio items response type widened to include portfolios
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The response data array for the "get portfolio items" endpoint changed from ProjectCompact to the new PortfolioItemCompact schema, which is an anyOf union of ProjectCompact and PortfolioCompact. This is technically additive (items can now be either projects or portfolios), but clients typed against ProjectCompact will break when they receive a PortfolioCompact object. Additionally, the opt_fields enum for this endpoint was drastically reduced — many previously valid field names (e.g. archived, custom_fields, members, permalink_url, etc.) were removed, which will break any client passing those field names in the query parameter.