The GitHub Actions job "npm_and_yarn in /javascript for minimatch - Update 
#1248998692" on fory.git/main has failed.
Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]).

Head commit for run:
6545c873099cba25fec3d7b9cad51dfd2e9be12f / Shawn Yang <[email protected]>
feat(swift): implement schema evolution compatible mode for fory swift (#3363)

## Why?

Swift xlang compatible mode was missing key schema-evolution behaviors
used by cross-language tests, so several compatibility scenarios were
not covered end-to-end.


## What does this PR do?

- Implements compatible-mode schema evolution in Fory Swift
serialization/deserialization, including schema-hash-aware struct
handling and field skipping for unknown/removed fields.
- Adds dynamic type-info handling for heterogeneous arrays and maps in
compatible mode.
- Improves non-tracking reference canonicalization for collection/map
elements when global reference tracking is enabled.
- Extends Swift type/meta plumbing (`Context`, `Serializer`,
`TypeResolver`, `SchemaHash`, `ForyTypeId`) and macro output to align
with xlang compatible encoding requirements.
- Reworks `ForySwiftXlangPeer` case handlers to round-trip major xlang
scenarios through native Swift serializers
(schema-consistent/compatible, polymorphism, nullable fields,
refs/circular refs, unsigned).
- Expands Java `SwiftXlangTest` with explicit `@Test` entries so Maven
Surefire discovers inherited xlang cases consistently.
- Updates a Swift unit test expectation to account for schema hash in
the struct header.


## Related issues

Closes #3362

#3349 
#1017 

## Does this PR introduce any user-facing change?



- [ ] Does this PR introduce any public API change?
- [ ] Does this PR introduce any binary protocol compatibility change?

## Benchmark

Report URL: https://github.com/apache/fory/actions/runs/22170962035

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to