diff options
| author | Zhineng Li <im@zhineng.li> | 2026-07-12 18:31:46 +0800 |
|---|---|---|
| committer | Zhineng Li <im@zhineng.li> | 2026-07-12 18:31:46 +0800 |
| commit | 7397ee1ef6c8f921ebb1f63d3e0179f2883522f5 (patch) | |
| tree | b72a000987d67f1b6dad61c9ee7f92195450fce9 /README | |
| parent | 5698e045510950fbceb8ec2cde83ea48b94b9589 (diff) | |
| download | afterglow-metadata-7397ee1ef6c8f921ebb1f63d3e0179f2883522f5.tar.gz afterglow-metadata-7397ee1ef6c8f921ebb1f63d3e0179f2883522f5.zip | |
Diffstat (limited to 'README')
| -rw-r--r-- | README | 21 |
1 files changed, 21 insertions, 0 deletions
@@ -11,3 +11,24 @@ metadata, set the bucket name in the `R2_BUCKET` environment variable and specify the release tag with `TAG`, then run the Makefile target: R2_BUCKET=<your-bucket-name> TAG=<version> make deploy + + +Versioning +---------- + +This package follows the version format `MAJOR.MINOR.YYYYMMDD`. + +The patch component uses a date instead of an incrementing number to +make the freshness of the metadata immediately visible. + +- **Major** version increments indicate breaking changes to the metadata + schema. +- **Minor** version increments indicate backward-compatible changes to + the metadata schema. +- **Patch** version represents the metadata snapshot date in `YYYYMMDD` + format and indicates when the metadata was generated from Alibaba + Cloud. + +Consumers should depend on `^MAJOR.MINOR`, for example: + + "lizhineng/afterglow-metadata": "^1.0" |
