15 ms·

Well, you don’t need the header

• chrismeller 4y ago
  You don’t need it if you’re expecting the current 2022-11-28 version, but it seems like you’ll need it to “opt-in” to any future ones, which presumably includes new endpoints that don’t even exist in the current.
  • timrogers 4y ago
    Author here. We consider new endpoints to be non-breaking changes, so they’ll be available in 2022-11-28.
    • chrismeller 4y ago
      Ah, ok. Well personally that seems even worse. Adding new things to the existing “version” just seems crazy.
      • akoncius 4y ago
        depends on how you define "version" here. seems that github took "version changes when backwards compatibility is broken" version which can mean that you can deploy 20 new features but if those are new then "version" does not change. that would be my guess