Metadata-Version: 2.1
Name: charm-refresh
Version: 3.0.0.1
Summary: In-place rolling refreshes of stateful charmed applications 
Author: Carl Csaposs
Author-email: carl.csaposs@canonical.com
Requires-Python: >=3.8
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Requires-Dist: charm-api (>=0.1.1)
Requires-Dist: charm-json (>=0.1.1)
Requires-Dist: httpx (>=0.28.1)
Requires-Dist: lightkube (>=0.15.4)
Requires-Dist: ops (>=2.9.0)
Requires-Dist: packaging (>=24.1)
Requires-Dist: pyyaml (>=6.0.2)
Requires-Dist: tomli (>=2.0.1)
Description-Content-Type: text/markdown

# charm-refresh
> [!CAUTION]
> Developer usage documentation is currently a work in progress and will describe the public interface. Until then, there is no public interface and any usage of charm-refresh is subject to breaking changes in any release—expect for usages explicitly approved by @carlcsaposs-canonical

## Versioning
W.X.Y.Z

W is incremented for changes that break `juju refresh` from the previous W.* versions

X.Y.Z is incremented as a [semantic version](https://semver.org/)—X is incremented for breaking changes to the public interface

If W > 0, the public API is stable—regardless of whether X == 0. (The semantic version rules that normally apply when X == 0 should only be applied when W == 0.) When W is incremented, X must be reset to 0.

