Releases: ChainSafe/gossamer-jam-releases
Releases · ChainSafe/gossamer-jam-releases
Gossamer-Jam v0.7.0.2
The following changes were implemented:
- Add the Forking Feature to the Fuzzer Target (ChainSafe/go-jam#307)
- Pass the Failing Safrole Reports (ChainSafe/go-jam#308)
- Pass the Failing Miscellaneous Reports (ChainSafe/go-jam#314)
- Pass the Failing PVM-Related Reports (ChainSafe/go-jam#315)
- Pass the Failing "New" Reports Except 1758621952 and 1758621879 (ChainSafe/go-jam#318)
- Fix and Pass the Crashing Reports Except 1756791458 and 1757861618 (ChainSafe/go-jam#319)
Gossamer-Jam v0.7.0.1
The following changes were implemented:
- Update the Fuzzer Target to Fuzzer Protocol v1 without the forking feature (ChainSafe/go-jam#298)
- Add the Ancestry Feature to the Fuzzer Target (ChainSafe/go-jam#299)
Gossamer-Jam v0.7.0.0
The binary files adhere to GP 0.7.0.
Furthermore, now the fuzzer target restarts if it encounters an error (ChainSafe/go-jam#296).
Gossamer-Jam v0.6.7.2
The following changes were implemented, based on the feedback given here:
- Fix: Store Entropy Input as Type (ChainSafe/go-jam#286)
- Improve/fix the sanity check for deserializing services (ChainSafe/go-jam#290)
Gossamer-Jam v0.6.7.1
Fuzzer-target should expect GP 0.6.7, not GP 0.6.6 - based on the feedback given here.
Gossamer-Jam v0.6.7.0
The binary files adhere to GP 0.6.7.