Update serde-json-wasm

[hashedone]

No description provided.

[webmaster128]

You can use those scripts to update and test all dev contracts:

Are contracts using serde-json-wasm directly? Do they need to upgrade their projects?

Could you add a CHANGELOG entry please?

[hashedone]

Yea, I was on it, but didn't aware about scripts. Just forgot to change it to draft. Thanks for hint.

[hashedone]

Now it is ready.

[ueco-jb]

Could you add a CHANGELOG entry please?

Do we want to include in changelog minor dependency update? It's not been the case so far as I can see.

[webmaster128]

Do we want to include in changelog minor dependency update? It's not been the case so far as I can see.

I'm not sure if it affects our users. Is anyone installing that dependecy directly and needs to update contracts? Or is this only used transitive?

Seems like users are unaffected as long as they use our wrappers:

pub fn from_slice<T: DeserializeOwned>(value: &[u8]) -> StdResult<T> {
    serde_json_wasm::from_slice(value).map_err(|e| StdError::parse_err(type_name::<T>(), e))
}

pub fn from_binary<T: DeserializeOwned>(value: &Binary) -> StdResult<T> {
    from_slice(value.as_slice())
}

pub fn to_vec<T>(data: &T) -> StdResult<Vec<u8>>
where
    T: Serialize + ?Sized,
{
    serde_json_wasm::to_vec(data).map_err(|e| StdError::serialize_err(type_name::<T>(), e))
}

pub fn to_binary<T>(data: &T) -> StdResult<Binary>
where
    T: Serialize + ?Sized,
{
    to_vec(data).map(Binary)
}

[webmaster128]

I still think this deserves a ## Fixed entry since it fixes serde bugs in our to_vec and to_binary.

[webmaster128]

Will add a CHANGELOG entry on main. Thank you!

[ethanfrey]

btw, I just released a minor patch (v0.4.1) which includes the fix so u128/i128 work properly (merged like 6 weeks ago, but never in a tagged release).

This should be pulled in automatically, but maybe we can set it to 0.4.1 (also in cosmwasm-template) to ensure people don't have issues there. (Serialising produced unparsable json)

[webmaster128]

Yeah saw this too. I got an update 0.3.x -> 0.4.1 automatically in a consumer project. It's probably hard to install 0.4.0 instead of 0.4.1 now. Let's update but with low prio.

[hashedone]

@webmaster128 it is not hard, but you need to do it intentionally ("=0.4.1" or playing directly with Cargo.lock)

[webmaster128]

Yeah, that's what I meant. Hard to do by accident.