Backport candidate: #[serde(default)] for SimplifiedShow.available_markets to 0.15.x #572

Status

The fix for this issue is already in master via #559 (commit ef49d81, "Deprecate renamed/removed fields"). That PR added #[serde(default)] to SimplifiedShow.available_markets (alongside the equivalent change on SimplifiedAlbum, FullAlbum, etc.).

So this is no longer a "fix needed in master" report — it's a backport / migration question:

• Several downstream consumers (e.g. aome510/spotify-player) still pin rspotify = "0.15.x". Bumping to 0.16 is a much larger change because of the broader Spotify Feb 2026 API changes (Spotify Web API changes (February 2026) #550) that landed in the same release.
• For those downstream users, the parse failure from current_user_saved_shows() is real on 0.15.3 and only resolvable today via either a registry-level patch or a 0.15.x backport of the serde(default) annotation.

Question for maintainer

Would a 0.15.x backport branch be acceptable? If so, I can prepare a PR that cherry-picks ef49d81 (or just the SimplifiedShow portion of it) into a 0.15.x line. If a backport branch isn't planned, that's also a fine answer — downstream projects will just have to bump at their own pace.

Repro (kept from original report for context)

rspotify 0.15.3 against GET /v1/me/shows on an account with a mix of recent and older saved shows. Some shows omit available_markets in the response and serde rejects the whole page:

missing field `available_markets` at line 1 column N

rspotify-model/src/show.rs:21 declares:

pub available_markets: Vec<String>,

In master (post-#559) the same field has #[serde(default)] and parses cleanly.