[Snyk] Upgrade amf-client-js from 5.0.4 to 5.7.0#1
Open
7azimo01 wants to merge 1 commit into
Open
Conversation
Snyk has created this PR to upgrade amf-client-js from 5.0.4 to 5.7.0. See this package in npm: amf-client-js See this project in Snyk: https://app.snyk.io/org/apple.hazem/project/0f7d0400-3a62-4dd0-96e4-61767fd43760?utm_source=github&utm_medium=referral&page=upgrade-pr
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
2 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.
Snyk has created this PR to upgrade amf-client-js from 5.0.4 to 5.7.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 775 versions ahead of your current version.
The recommended version was released 2 months ago.
Release notes
Package name: amf-client-js
Java 21 support
Dependency Changes
Behavior Changes
What's Changed
Full Changelog: 5.6.4...5.7.0
What's Changed
New Contributors
Full Changelog: 5.6.3...5.6.4
W-15053499 - Publish 5.6.4-0
What's Changed
Full Changelog: 5.6.2...5.6.3
Bug fixing
What's Changed
Full Changelog: 5.6.1...5.6.2
AVRO Support in AMF
We're happy to announce we've added support for AVRO Schema 1.9.0 in AMF:
an AVRO Schema has the following properties:
.jsonor.avscfile$schema)Where we support and DON'T support AVRO Schemas
We Support AVRO Schemas (inline or inside a
$ref):.avscfile type to indicate that's an avro fileAvroConfigurationschemaFormatMUST be declared and specify it's an AVRO payloadAvroSchemaDocumentcan only be parsed with the specificAvroConfigurationWe don't support AVRO Schemas:
Known AVRO Validation limitations
We're using the Apache official libraries for JVM and JS. The validation libraries differ in interfaces and implementations, and each has some known constraints:
JVM avro validation constraints
Both JVM & JS validation constraints
"default"values are not being validated when the type isbytes,map, orarray"default": []) even though the Avro Schema Specification has some examples with itMore information here
for more information on how to use AVRO in amf check the
adrs/0014-avro-support.mdfile.Full Changelog: 5.5.4...5.6.1
AVRO Support in AMF
We're happy to announce we've added support for AVRO Schema 1.9.0 in AMF:
an AVRO Schema has the following properties:
.jsonor.avscfile$schema)Where we support and DON'T support AVRO Schemas
We Support AVRO Schemas (inline or inside a
$ref):.avscfile type to indicate that's an avro fileAvroConfigurationschemaFormatMUST be declared and specify it's an AVRO payloadAvroSchemaDocumentcan only be parsed with the specificAvroConfigurationWe don't support AVRO Schemas:
Known AVRO Validation limitations
We're using the Apache official libraries for JVM and JS. The validation libraries differ in interfaces and implementations, and each has some known constraints:
JVM avro validation constraints
Both JVM & JS validation constraints
"default"values are not being validated when the type isbytes,map, orarray"default": []) even though the Avro Schema Specification has some examples with itMore information here
for more information on how to use AVRO in amf check the
adrs/0014-avro-support.mdfile.Full Changelog: 5.5.4...5.6.0
AVRO transformation and rendering support (ALPHA)
In the previous release we added support for AVRO parsing, which means creating an
AvroConfigurationwith anAvroParsePluginand with that create aBaseUnitClientthat has theparse()method that parses an AVRO Schema and returns anAvroSchemaDocument.This release, we've added support for the
transform()andrender()methods, letting the user resolve the model and export it to.jsonldor to.jsonagain.To do this, we've created the
AvroRenderPluginand added it to theAvroConfigurationas well as the necessary transformation pipelines. Now the AVRO Configuration is much more complete and looks like this:We're expecting to continue this growth and launch AVRO Validation in the next release, will keep you updated.
For more information about transformation and rendering check the following documentation:
What's Changed
Full Changelog: 5.5.3...5.5.4
AVRO Support (ALPHA)
AVRO Schema Support in Async
Added support to parsing of AVRO Schemas in Async 2.x payload definitions (inlined or referencing to an external file).
This support is currently limited, only for parsing, not for validation or emission.
AVRO Schema Fragment
Added support to parsing of AVRO Schemas as a fragment using the new
AvroConfiguration, returning anAvroSchemaDocument. This is only for AVRO Schema files parsed using this specific configuration, files referenced from an Async 2.x API will be processed asExternalFragmentas usual.This support is currently limited, only for parsing, not for validation or emission.
What's Changed
Full Changelog: 5.5.2...5.5.3
W-15904614 - Publish 5.5.2-0