Release 302.0.0

[smilingkylan]

Explanation

Bump remote-feature-flag-controller and core package

[mcmire]

It looks like we are introducing a new change to the src/ or tests/ directory of a package and releasing that package in the same PR. I realize we might be doing this to save time, but we don't typically do this as it makes things confusing when looking back at the history. We tend to keep any changes to release PRs just to satisfy the release itself. Can we cut a new release in a separate PR?

(Edit: Oh, I see we have #5341. Perhaps we should merge that first?)

[smilingkylan]

#5341

Are you able to merge that PR? For whatever reason it doesn't seem like it will let me

[mcmire]

@smilingkylan Can we retitle this PR "Release 302.0.0"? We have a workflow in place which will automatically publish the new version when this PR is merged, but that won't happen if this PR is not named correctly.

[cryptodev-2s]

@smilingkylan please update this package in transaction-controller as it's a peer dependency from 1.4.0 to 1.5.0 to fix the lint issue. Also, if you can add a changelog entry for this update under the “Unreleased” section as Changed in the transaction-controller changelog.

[socket-security]

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: npm/@metamask/[email protected]

View full report↗︎

[smilingkylan]

@smilingkylan please update this package in transaction-controller as it's a peer dependency from 1.4.0 to 1.5.0 to fix the lint issue. Also, if you can add a changelog entry for this update under the “Unreleased” section as Changed in the transaction-controller changelog.

You able to take a look now @cryptodev-2s @mcmire . Let me know if I need any more changes.

[cryptodev-2s]

@smilingkylan The lock file needs to be updated. Could you please run yarn to update it?

[cryptodev-2s]

LGTM!

Other PR already merged in