I've been using the GiantBomb API for a while. I use 2 endpoints - 'games' & 'game'. For both these endpoints, the field 'original_release_date' almost always contained the release date of the game.
I've recently noticed that for most games this field now returns null, even for games for which in the past it returned values. I can't say how long ago this started happening, but it definitely did. I have an automated test that I run every once in a while to see that my API integration is correct, and that test started failing for this reason.
It looks like for most cases I can workaround by using the 'expected_release_year', 'expected_release_month' & 'expected_release_day' fields, which return non-null values (even for games which have already been released, which is slightly confusing).
Can anyone confirm that there were api or data changes on the side of GiantBomb?