v6.3.4

v6.3.4

AMF 5.6.4
CustomValidator-scalajs v0.6.2
CustomValidator-js v1.7.2
amf-antlr-parsers v0.7.27

What's Changed

• W-17249173: Add OAS 3.1 Profile

v6.3.3

v6.3.3

AMF 5.6.3
CustomValidator-scalajs v0.6.1
CustomValidator-js v1.7.2
amf-antlr-parsers v0.7.27

What's Changed

• W-16814887: Avro map values is now expecting a scalar (will not add and eol after suggestion)
• W-16814386: Fixed suggestions inside fields when a more precise type is declared
• W-16595822: Fixed suggestions on array inside servers node
• W-17007396: Enhancement in suggestions styler so that we can suggest values in complex nodes

v6.3.2

Release v6.3.2

Check AMF dependencies versions on dependencies.properties file.

• JVM asset
• Node Client
• JS Server

What's Changed

This version consists on the adoption of AMF 5.6.2

Bugs Fixed

• W-16834047: Error publishing AVRO schema with union types

v6.3.1

Release v6.3.1

Check AMF dependencies versions on dependencies.properties file.

• JVM asset
• Node Client
• JS Server

What's Changed

This version consists on the adoption of AMF 5.6.1

v6.3.0

Release v6.3.0

Check AMF dependencies versions on dependencies.properties file.

• JVM asset
• Node Client
• JS Server

What's Changed

This version provides support for AVRO Schema 1.9.0:

• as a standalone document
• inside Async APIs

an AVRO Schema has the following properties:

• It's defined in a .json or .avsc file
• It doesn't have a special key that indicates it's an AVRO Schema, nor it's version (like JSON Schema does with it's $schema)

Where we support and DON'T support AVRO Schemas

We Support AVRO Schemas (inline or inside a $ref):

• as a standalone document or file

  • we encourage users to use the .avsc file type to indicate that's an avro file
  • must use the specific AvroConfiguration

• inside a message payload in an AsyncAPI

  • the key schemaFormat MUST be declared and specify it's an AVRO payload

• an AvroSchemaDocument can only be parsed with the specific AvroConfiguration
  We don't support AVRO Schemas:

• inside components --> schemas in an AsyncAPI

  • because we can't determine if it's an AVRO Schema or any other schema

  Bugs Fixed

  • W-16618010: Suggestions under new schema name does not include $ref option when using JSON API Spec language

v6.2.3

Release v6.2.3

Check AMF dependencies versions on dependencies.properties file.

• JVM asset
• Node Client
• JS Server

What's Changed

This version adopts AMF 5.5.4

What's Changed

• W-16203018: Remote Credential leak via RAML Include in Code Builder Extensions

Full Changelog: v6.2.2...v6.2.3

v6.2.2

Release v6.2.2

Check AMF dependencies versions on dependencies.properties file.

• JVM asset
• Node Client
• JS Server

What's Changed

This version adopts AMF 5.5.3

What's Changed

• W-15997710: JSON Schema in tree / isolated issues Stage 3

Full Changelog: v6.2.1...v6.2.2

v6.2.1

Release v6.2.1

Check AMF dependencies versions on dependencies.properties file.

• JVM asset
• Node Client
• JS Server

What's Changed

This version adopts AMF 5.5.2-0

What's Changed

• W-15832126: Fix $ref suggestion
• W-15610633: New servers suggestion
• W-15832126: Fix $ref suggestion
• W-15900977: Fix duplicated suggestions under message node

Full Changelog: v6.2.0...v6.2.1

v6.2.0

Release v6.2.0

Check AMF dependencies versions on dependencies.properties file.

• JVM asset
• Node Client
• JS Server

What's Changed

This version consists on the adoption of AMF 5.5.1

What's Changed

• W-15677504: Change uri encode on getting configuration state from WCM
• Added support for AsyncAPI 2.6.0

Full Changelog: v6.1.2...v6.2.0

v6.1.2

Release v6.1.2

Check AMF dependencies versions on dependencies.properties file.

• JVM asset
• Node Client
• JS Server

What's Changed

This version consists on the adoption of AMF 5.5.0-0

Full Changelog: v6.1.1...v6.1.2