{{ message }}
Repository navigation
Commit dec5134
authored
chore: release the conformance assets as 0.1.0, not 1.0.0 (#448)
Stops [#447](#447) from cutting
the conformance assets as **1.0.0**.
## Why it proposed 1.0.0
`.release-please-manifest.json` carries
`"specification/assets/provider-tck": "0.0.0"`. release-please reads
`0.0.0` as *no release yet*, so it never bumps from it — it falls back
to its default initial version, which is `1.0.0`. `bump-minor-pre-major:
true` is already set and had no effect here, because there is no prior
version to bump minor-instead-of-major.
## Why 1.0.0 is the wrong number
It is a compatibility claim, and `go get` is where it gets read.
- **Appendix F, which gives these assets their meaning, is not merged**
([#439](#439)) and marks itself
experimental.
- The **capability vocabulary** is still under review, and tags are the
suite's public surface: adding, splitting or renaming one changes what
every adopter's run means. `@string-typing` was split out of
`@fully-typed-values` during review, which is exactly the kind of change
1.0.0 promises not to make.
- The **control-API surface** (`openapi/control-api.yaml`) and the
**report schema**
([#425](#425)) are both open
questions.
- [#430](#430) and
[#433](#433) are open gaps in
what the assets assert.
## What this changes
One line: `initial-version: "0.1.0"` on the assets package.
`0.1.0` rather than `0.0.1` because the first release is a feature, not
a fix, and because it leaves both digits meaningful — patch for fixture
corrections, minor for new scenarios. Both are expected: the testbed
already owes two fixtures
([flagd-testbed#392](open-feature/flagd-testbed#392)),
and the open questions above will add scenarios.
## What to expect on merge
release-please re-runs on push to `main` and should update #447 to
propose **0.1.0**, tagging `specification/assets/provider-tck/v0.1.0`
once that is merged. Nothing is tagged by this PR.
Four conformance implementations currently pin these assets by commit,
because no tag exists yet. That tag is what lets Go name a version
instead of a pseudo-version, so the number it carries is worth getting
right before the first one is published — a tag is not practical to take
back.
Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>1 parent 2c5e8bb commit dec5134
1 file changed
Lines changed: 1 addition & 0 deletions

0 commit comments