<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stripe on Bruno Pedro</title><link>https://brunopedro.com/categories/stripe/</link><description>Recent content in Stripe on Bruno Pedro</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 02 Dec 2022 16:07:18 +0100</lastBuildDate><atom:link href="https://brunopedro.com/categories/stripe/index.xml" rel="self" type="application/rss+xml"/><item><title>Calendar-Based API Versioning</title><link>https://brunopedro.com/2022/12/01/calendar-based-api-versioning/</link><pubDate>Thu, 01 Dec 2022 18:57:41 +0100</pubDate><guid>https://brunopedro.com/2022/12/01/calendar-based-api-versioning/</guid><description>&lt;p>&lt;a href="https://github.com/timrogers">Tim Rogers&lt;/a>, a Product Manager at GitHub, recently &lt;a href="https://github.blog/2022-11-28-to-infinity-and-beyond-enabling-the-future-of-githubs-rest-api-with-api-versioning/">announced&lt;/a> that they are moving from incremental API versioning to something they&amp;rsquo;re calling &amp;ldquo;calendar-based.&amp;rdquo; The announcement explains what calendar-based versioning is and why GitHub is adopting it now. Calendar-based versioning allows GitHub to introduce breaking changes regularly without upsetting API consumers. Consumers won&amp;rsquo;t get mad because they can &lt;em>pin&lt;/em> their requests to a particular API version, so they&amp;rsquo;re sure it won&amp;rsquo;t contain any breaking changes.&lt;/p></description></item></channel></rss>