diff --git a/specification.json b/specification.json index 0f6dd400..0f45dabc 100644 --- a/specification.json +++ b/specification.json @@ -265,8 +265,8 @@ "RFC 2119 keyword": null, "children": [ { - "id": "Conditional Requirement 1.4.14.1", - "machine_id": "conditional_requirement_1_4_14_1", + "id": "Conditional Requirement 1.4.15.1", + "machine_id": "conditional_requirement_1_4_15_1", "content": "Condition: `Flag metadata` MUST be immutable.", "RFC 2119 keyword": "MUST", "children": [] diff --git a/specification/assets/gherkin/evaluation_v2.feature b/specification/assets/gherkin/evaluation_v2.feature index 4f2c706f..8754b1eb 100644 --- a/specification/assets/gherkin/evaluation_v2.feature +++ b/specification/assets/gherkin/evaluation_v2.feature @@ -488,9 +488,9 @@ Feature: Flag Evaluations - Complete OpenFeature Specification Coverage And the hook order should be maintained - # Testing immutability requirements (Spec 1.4.15/1.4.14.1) + # Testing immutability requirements (Spec 1.4.15/1.4.15.1) # Testing: flag metadata must be immutable - @immutability @spec-1.4.14.1 + @immutability @spec-1.4.15.1 Scenario: Evaluation context immutability Given a Boolean-flag with key "boolean-flag" and a fallback value "false" And an evaluation context with modifiable data diff --git a/specification/sections/01-flag-evaluation.md b/specification/sections/01-flag-evaluation.md index 08be8091..807677bf 100644 --- a/specification/sections/01-flag-evaluation.md +++ b/specification/sections/01-flag-evaluation.md @@ -382,7 +382,7 @@ This `flag metadata` field is intended as a mechanism for providers to surface a > The implementation language supports a mechanism for marking data as immutable. -##### Conditional Requirement 1.4.14.1 +##### Conditional Requirement 1.4.15.1 > Condition: `Flag metadata` **MUST** be immutable.