2.0.0

[legobeat]

This is the release candidate for version 2.0.0.

[legobeat]

Blocking

• deps: Update @metamask/utils and @metamask/rpc-errors  snaps#1728

(#73)

[FrederikBolding]

While this is technically a breaking change in the type I don't think it's really necessary to do a major bump for it. What do you think?

[Mrtenz]

While this is technically a breaking change in the type I don't think it's really necessary to do a major bump for it. What do you think?

If it's breaking, technically or not, I think we should do a major bump. 😅

[legobeat]

While this is technically a breaking change in the type I don't think it's really necessary to do a major bump for it. What do you think?

If we consider that this was a type-only change - TypeScript being a developer tool and strictly optional - I would tend to agree that breaking type interfaces shouldn't necessitate a breaking change.

However:

1. Treating breaking TypeScript interfaces as semver-major is in line with current and recent practice in other repos in the MetaMask org. So it's a bit of a separate discussion.
2. This does in fact change runtime behavior so it's breaking even if we disregard that IMO

I guess two options where both sound reasonable to me:

1. revert Validate snap ids #75 -> release 1.3.0 -> re-apply Validate snap ids #75 -> release 2.0.0
2. go ahead with 2.0.0 in one go as in this pr

[FrederikBolding]

This does in fact change runtime behavior so it's breaking even if we disregard that IMO

Yeah, you are right. However, for our use we do not currently rely on the runtime behaviour. Which is why I brought it up.

But I am fine with following semver properly here as well. Just wanted to voice the option, because it wouldn't be breaking with our usage.