Repository navigation
chore(main): release specification/assets/provider-tck 0.1.0 - #447
Merged
aepfli merged 1 commit intoOct 16, 2026
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Docstring Coverage |  |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
| Description check | |
The description documents the 0.1.0 release of specification/assets/provider-tck and matches the changelog and manifest changes. |
| Title check | |
The title clearly identifies the release of specification/assets/provider-tck as version 0.1.0 and matches the changeset. |
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
toddbaert
pushed a commit
that referenced
this pull request
Oct 16, 2026
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>
Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
openfeaturebot
changed the title
openfeaturebot
force-pushed
the
release-please--branches--main--components--specification/assets/provider-tck
branch
from
October 16, 2026 12:31
6b65d46 to
9d80550
Compare
toddbaert
approved these changes
Oct 16, 2026
aepfli
deleted the
release-please--branches--main--components--specification/assets/provider-tck
branch
October 16, 2026 15:11
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.1.0 (2026-10-16)
Features
This PR was generated with Release Please. See documentation.