This is an automated email from the ASF dual-hosted git repository.
kriskras99 pushed a change to branch feat/full_enum_support
in repository https://gitbox.apache.org/repos/asf/avro-rs.git
discard f16fc52 temp
discard 5e72d86 feat: Rework `SchemaAwareSerializer` to be more strict and
follow the documented model (no tests)
discard 479ff57 feat: Use `SchemaAwareDeserializer` in the readers and add
tests
discard c3e1848 feat: `SchemaAwareDeserializer` (no tests)
discard de8cced doc: Document the mapping between the Serde and Avro data
models
add 1452bf7 chore(deps): Bump bon from 3.9.0 to 3.9.1 (#511)
new 3d33135 doc: Document the mapping between the Serde and Avro data
models
new 764f119 feat: `SchemaAwareDeserializer` (no tests)
new 2317898 feat: Use `SchemaAwareDeserializer` in the readers and add
tests
new 4da2ebf feat: Rework `SchemaAwareSerializer` to be more strict and
follow the documented model (no tests)
new c3e1825 temp
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (f16fc52)
\
N -- N -- N refs/heads/feat/full_enum_support (c3e1825)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 5 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
Cargo.lock | 8 ++++----
avro/Cargo.toml | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
