Repository navigation
Upgrade ConfigStore to 1.0 #729
Description
Activity
This would be a breaking change wouldn't it?
Kinda sorta. It's unique because it's a dependency for a feature the user doesn't realize exists, resumable uploads. If a resumable upload goes well, the information we cache is destroyed. So, ideally, the cache file is only non-empty for a brief amount of time.
But, it will be something to document for our next release. And since we're pre-1.0, each minor bump lets us go as yolo as we need to.
Is there a centralized location where we would document breaking changes? Or just add release notes to our tag..?
We use the GitHub releases page as a changelog.
On Sunday, July 19, 2015, Dave Gramlich [email protected] wrote:
Is there a centralized location where we would document breaking changes?
—
Reply to this email directly or view it on GitHub
#729 (comment)
.- added a commit that references this issue
on Jan 10, 2023 - added a commit that references this issue
on Feb 25, 2026 - added 2 commits that reference this issue
on Mar 5, 2026 - added 2 commits that reference this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 27, 2026 - added a commit that references this issue
on May 5, 2026
It's just JSON now (formerly YAML), so we will save some processing power by upgrading.