Bump to v0.48.0

[JoshuaBatty]

waiting on

• remove local fixtures-std and fixtures-core dirs and use std v0.47.0 for lsp tests #5274
• Update forc-crypto to use latest libraries #5273
• feat!: add transaction policies support #5281

[IGI-111]

@ironcev Can you look at that failing test?

[JoshuaBatty]

I think it was locked to v0.47 of the std lib. I've just updated it to

[[package]]
name = 'trait_cannot_find_in_scope_issue'
source = 'member'

[kayagokalp]

I think it was locked to v0.47 of the std lib. I've just updated it to

[[package]]
name = 'trait_cannot_find_in_scope_issue'
source = 'member'

I feel like this might not work because forc will realize lock file is not valid and it will try to fetch. std v0.48 is not released yet but forc will try to get that one. We should always point to std by path in test suite to prevent issues popping out while releasing.

[project]
name = "trait_cannot_find_in_scope_issue"
authors = ["Fuel Labs <contact@fuel.sh>"]
entry = "main.sw"
license = "Apache-2.0"


[dependencies]
std = { path = "../../../../../sway-lib-std" }

Note: I am writing this without having access to the file structure at the moment so amount of ../s might be invalid in the given example above

[JoshuaBatty]

Ok good idea @kayagokalp i'll update it now. We should probably make sure this pattern is done is all tests in a follow up PR

[kayagokalp]

d6c8c15 was missing the lock file for the test with std pointing to local. That would also cause test suite to fail as forc will throw warnings. I added the lock file back with std pointed to local version. (simply executed forc build after d6c8c15) in 2875be8.

Sorry for pushing to your branch unannounced 😅

[JoshuaBatty]

Thanks, @kayagokalp :)