Owlet Weekly Update (Week of June 8th)
What is the Owlet Weekly Update?
Welcome to the inaugural edition of the Owlet Weekly Update (working title) — an owlet-sized update (posted every Tuesday to the ReadMe Changelog) where we provide an overview of the bug fixes and minor improvements that went out as part of our new Tuesday release cycle.
As we refine our format and process for providing these updates, we'd love to hear what you think at [email protected]!
Bug Fixes and Minor Improvements
- Performance and stability improvements to our new Markdown engine in the Changelog. 📝
- Fixed an issue where a small portion of our Enterprise customers were seeing a confusing redirect when logging out using our Custom OAuth flow. 🔐
- Fixed a bug where search engines could not access
robots.txtfor private projects. 🤖 - And last but not least... improvements to our release tracking process, so we can provide you with updates like these! 🚀
Bigger Feature Updates and Improvements
Search Improvements
We shipped some huge improvements to our search, including:
- Better search box design
- Improved indexing querying
Be sure to check out Marc's blog post for some background on our design and product development process.
ReadMe Free
We also released a new free plan! We’ve noticed that many companies come to us with only a Swagger/OpenAPI file or a simple list of endpoints. They don’t have the technical design resources or the time to build a full-featured developer hub, let alone an API Reference.
There are a lot of open source tools out there to build an API Reference, some better than others. We want everyone to have the option to use the best-in-class option available without worrying about its cost or added development effort. Our new free pricing tier was created to allow everyone to build a beautiful API Reference section at no cost.