EXUI-4291: Suppressions - @edium/fsm - major#2158
Open
chrisjones-hmcts wants to merge 14 commits into
Open
Conversation
chrisjones-hmcts
requested review from
RiteshHMCTS,
balajisridharanhmcts and
nathan-clark
chrisjones-hmcts
changed the title
This was referenced May 6, 2026
RiteshHMCTS
previously approved these changes
May 15, 2026
balajisridharanhmcts
previously approved these changes
May 15, 2026
chrisjones-hmcts
dismissed stale reviews from balajisridharanhmcts and RiteshHMCTS
via
0f4a68f
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/EXUI-4291
Change description
Branched off EXUI-4425 to get npm publish changes which will allow us to remove
@edium/fsmfrom consuming repos of toolkit, then updated major version of@edium/fsmwhich is 100% backwards compatible with our previous version used.Does this PR introduce a breaking change? (check one with "x")