fix: remove verbose log

[camsjams]

Fixes #1322

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	85.05% (+0.01% 🔼)	5249/6172
🟡	Branches	66.84% (-0.03% 🔻)	776/1161
🟡	Functions	75.13% (+0.09% 🔼)	858/1142
🟢	Lines	84.93% (+0.01% 🔼)	5029/5921

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟡	... / provider.ts	61.9% (+0.09% 🔼)	50% (-0.67% 🔻)	59.7% (+1.49% 🔼)	62.96% (+0.11% 🔼)

Test suite run success

1262 tests passing in 216 suites.

Report generated by 🧪jest coverage report action from 88e998e

[nedsalk]

IMO it should be noisy so that the user updates their package to the latest version, even if it's a patch version. Sorry, but I'll block this until @digorithm gives his thoughts, because this PR removes patch mismatch warnings altogether.

In the meantime, could you share with us the noisy logs and how they look?

[digorithm]

IMO it should be noisy so that the user updates their package to the latest version, even if it's a patch version. Sorry, but I'll block this until @digorithm gives his thoughts, because this PR removes patch mismatch warnings altogether.

In the meantime, could you share with us the noisy logs and how they look?

Thanks @nedsalk, this is a thoughtful remark. However, patch versions in all repos maintained by Fuel Labs are supposed to be backward compatible, meaning: no breaking changes whatsoever. So a change from 0.x.1 to 0.x.2 should never cause any issue. Given that that's a thing, it doesn't make much sense for us to be noisy about it.

[camsjams]

An example of a mismatch log can be seen in here: #1322

But many TS-SDK developers will be iterating against the live node instead of local, so they'd see this constantly on their console @nedsalk :