1.1.0 minor version#482
Merged
Merged
Conversation
Merge v1.0-dev changes to dev
Merge release date change from v1.0-dev to dev
chore(docs): fix spec version
Revert changes to 1.0.0.md to match main
Updating 1.0.1 release data
dev: update from main
initialize src/arazzo.md from versions/1.0.1.md
Initialize `src/arazzo.md` and move WIP schemas to `src/schemas/validation`
Merge Dev to v1.0-dev
Merge Dev to v1.1-dev
The example indicates that when YAML format is translated to JSON, the brackets SHOULD be added to the condition.
Clarify origin or runtime expressions ABNF non-terminals
fix: fix referenced stepId in examples
- `retryAfter` and `retryLimit` fields are not required in the `failureAction` schema when the `type` keyword equals `retry`. - update bnpl example to add failureObject fixes #342
per the spec, the `retry` does not require stepId or workflowId to be strictly defined fixes #341
…ject-schema fix(schema): remove conditional statement for type: retry in failure action object
…ema-retry fix(schema): remove enumeration in failure action object
refactor(arazzo): remove brackets around condition
feat: added support for AsyncAPI v3
Add seven fixture-driven schema tests covering async step validation that was already encoded in the v1.1 schema but not explicitly exercised by the suite. The new fail fixtures cover mutually exclusive operation targets, missing action on channelPath steps, and dependsOn validation for empty arrays, invalid reference syntax, and duplicate entries. The new pass fixtures cover receive steps without correlationId and reusable parameter references on async steps. Each negative fixture was authored from an otherwise-valid baseline and checked by applying the minimal invalidating change, so the failures remain attributable to the intended schema branch rather than unrelated missing fields or malformed top-level structure.
Add five fixture-driven schema tests covering OpenAPI step validation paths that were already enforced by the v1.1 schema but were not explicitly exercised by the test suite. The new pass fixtures cover operationPath-only steps and reusable parameter references for OpenAPI operations. The new fail fixtures cover mutually exclusive operationId/operationPath targets, missing operation targets, and duplicate parameter entries. Each negative fixture was validated against a repaired baseline first so the final failing YAML is attributable to the intended schema branch rather than unrelated structural mistakes.
Add six fixture-driven schema tests covering workflow-step validation paths that were already enforced by the v1.1 schema but were not explicitly exercised by the suite. The new pass fixtures cover the minimal valid workflow-step shape and reusable parameter references on workflow steps. The new fail fixtures cover missing workflowId, duplicate workflow-step parameters, and rejection of async-only fields such as action and channelPath on workflow steps. Each negative fixture was validated against a repaired baseline first so the final failing YAML remains attributable to the intended schema branch rather than unrelated document-shape problems.
Add six pass fixtures that intentionally capture current JSON Schema validator behavior in cases where structural validation succeeds without proving full semantic compliance. These characterization cases cover source-type mismatches between OpenAPI and AsyncAPI step usage, permissive operationPath and channelPath string handling, and the current acceptance of requestBody on workflow steps because requestBody is defined on step-object-base. Also add a short informative note to the specification text clarifying that JSON Schema validation alone does not establish full Arazzo conformance and that some constraints require source resolution or other semantic validation across referenced documents.
Drop the recently added note in src/arazzo.md while keeping the characterization fixtures unchanged.
…on-clarity Clarify Criterion Object condition evaluation semantics
chore(repo): Update README for 1.1 release prep
Add missing schema validation fixtures for async, OpenAPI, and workflow steps
V1.1 release prep
frankkilcommins
force-pushed
the
v1.1.0-rel
branch
from
dc13f60 to
8dd3773
Compare
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
5 participants
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.
Arazzo - 1.1.0 release PR (to main)
Enhancements:
resolves #270
fixes #366
fixes #438
fixes #434
Bugs/Fixes:
fixes #253
fixes #330
fixes #424
fixes #425
fixes #426
fixes #428
fixes #437
fixes #427
fixes #423
House-keeping:
fixes #468
fixes #462