fix(deps): update xstate monorepo to v5 (major)

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
@xstate/vue (source)	^2.0.0 -> ^5.0.0
xstate (source)	^4.38.3 -> ^5.22.0

---

Warning

Deprecated preset: Kong/public-shared-renovate:kong-frontend-config

Your config references a deprecated preset. To prevent disruption, this file now composes the org default building blocks and layers a few tweaks so behavior stays close to the historical frontend configuration.

What’s different from the default

• Weekday automerge cadence and daily run windows (schedule:automergeWeekdays + schedule:daily + :noUnscheduledUpdates)
• Automerge enabled for minor and patch updates with required status checks
• Adds the mend-bot label alongside Renovate’s standard dependency labeling
• Timezone set to America/New_York
• Disables specific actions: Kong/kong-api-tests and the-actions-org/workflow-dispatch
• Extra grouping for GitHub Actions: non-major stable updates grouped under "non-major github actions with stable versions"

Recommended migration

Prefer switching to the default preset and applying only the bits you still need locally. Example configuration to replicate this preset’s behavior on top of the default:

{
  "extends": [
    "Kong/public-shared-renovate",
    "schedule:automergeWeekdays",
    "schedule:daily",
    ":automergeMinor",
    ":automergePatch",
    ":automergeRequireAllStatusChecks",
    ":labels(dependencies,mend-bot)",
    ":noUnscheduledUpdates",
    ":timezone(America/New_York)"
  ],
  "packageRules": [
    {
      "matchPackageNames": ["*"],
      "matchDepTypes": ["action"],
      "matchUpdateTypes": ["minor", "patch"],
      "matchCurrentVersion": "!/^v0/",
      "groupName": "non-major github actions with stable versions"
    }
  ]
}

To disable the same actions locally, add the helpers after the default in your extends list:

[
  "Kong/public-shared-renovate",
  "Kong/public-shared-renovate//helpers/disable-action(Kong/kong-api-tests)",
  "Kong/public-shared-renovate//helpers/disable-action(the-actions-org/workflow-dispatch)"
]

Timeline

This compatibility preset will be removed in January 2026. Please migrate to the default preset with local overrides before then.

---

Release Notes

statelyai/xstate (@​xstate/vue)

v5.0.0

Compare Source

Patch Changes

• Updated dependencies [e07a7cd8462473188a0fb646a965e61be1ce6ae3]:
  • xstate@​5.20.0

v4.0.4

Compare Source

Patch Changes

• Updated dependencies [479c74b83fa77c57c48f54cf0e9dcfab5fe6cae5]:
  • xstate@​5.19.4

v4.0.3

Compare Source

Patch Changes

• Updated dependencies [b453b2d72ba12d0fe46a995f9ccced8000fd0cc9]:
  • xstate@​5.19.3

v4.0.2

Compare Source

Patch Changes

• Updated dependencies [d99df1d8f4fe49145c9974465b65028bf19b365f]:
  • xstate@​5.19.2

v4.0.1

Compare Source

Patch Changes

• Updated dependencies [bf6119a7310a878afbf4f5b01f5e24288f9a0f16]:
  • xstate@​5.19.1

v4.0.0

Compare Source

Patch Changes

• Updated dependencies [8c4b70652acaef2702f32435362e4755679a516d]:
  • xstate@​5.19.0

v3.1.4

Compare Source

Patch Changes

• Updated dependencies [25963966c394fc904dc9b701a420b6e204ebe7f7]:
  • xstate@​5.18.2

v3.1.3

Compare Source

Patch Changes

• #​5055 ad38c35c37 Thanks @​SandroMaglione! - Updated types of useActor, useMachine, and useActorRef to require input when defined inside types/input.

  Previously even when input was defined inside types, useActor, useMachine, and useActorRef would not make the input required:

  const machine = setup({
    types: {
      input: {} as { value: number }
    }
  }).createMachine({});
  
  function App() {
    // Event if `input` is not defined, `useMachine` works at compile time, but risks crashing at runtime
    const _ = useMachine(machine);
    return <></>;
  }

  With this change the above code will show a type error, since input is now required:

  const machine = setup({
    types: {
      input: {} as { value: number }
    }
  }).createMachine({});
  
  function App() {
    const _ = useMachine(machine, {
      input: { value: 1 } // Now input is required at compile time!
    });
    return <></>;
  }

  This avoids runtime errors when forgetting to pass input when defined inside types.

v3.1.2

Compare Source

Patch Changes

• #​4844 5aa6eb05c Thanks @​davidkpiano! - The useSelector(…) hook from @xstate/react is now compatible with stores from @xstate/store.

  import { createStore } from '@​xstate/store';
  import { useSelector } from '@​xstate/react';
  
  const store = createStore(
    {
      count: 0
    },
    {
      inc: {
        count: (context) => context.count + 1
      }
    }
  );
  
  function Counter() {
    // Note that this `useSelector` is from `@xstate/react`,
    // not `@xstate/store/react`
    const count = useSelector(store, (state) => state.context.count);
  
    return (
      <div>
        <button onClick={() => store.send({ type: 'inc' })}>{count}</button>
      </div>
    );
  }

v3.1.1

Compare Source

Patch Changes

• #​4759 f112081b9 Thanks @​davidkpiano! - Fix send(…) type for useActor(…)

v3.1.0

Compare Source

Minor Changes

• #​4231 c2402e7bc Thanks @​davidkpiano! - The actor passed to useSelector(actor, selector) is now allowed to be undefined for an actor that may not exist yet. For actors that may be undefined, the snapshot provided to the selector function can also be undefined:

  const count = useSelector(maybeActor, (snapshot) => {
    // `snapshot` may be undefined
    return snapshot?.context.count;
  });
  
  count; // number | undefined

v3.0.3

Compare Source

Patch Changes

• Updated dependencies [b453b2d72ba12d0fe46a995f9ccced8000fd0cc9]:
  • xstate@​5.19.3

v3.0.2

Compare Source

Patch Changes

• #​4604 3ad929eb4 Thanks @​tkofh! - The useActor hook now correctly types it's send function when passed an ActorLogic.

v3.0.1

Compare Source

Patch Changes

• #​5197 5e05d5908093bfd3435dc2243e066e4e91b3ebc5 Thanks @​davidkpiano! - The emitted event type can no longer be accidentally overridden in the emitted event payload. See #​5196 for the issue.

v3.0.0

Compare Source

Major Changes

• #​5175 38aa9f518ee2f9a5f481306a1dc68c0ad47d28d5 Thanks @​davidkpiano! - The createStore function now only accepts a single configuration object argument. This is a breaking change that simplifies the API and aligns with the configuration pattern used throughout XState.

  // Before
  // createStore(
  //   {
  //     count: 0
  //   },
  //   {
  //     increment: (context) => ({ count: context.count + 1 })
  //   }
  // );
  
  // After
  createStore({
    context: {
      count: 0
    },
    on: {
      increment: (context) => ({ count: context.count + 1 })
    }
  });

• #​5175 38aa9f518ee2f9a5f481306a1dc68c0ad47d28d5 Thanks @​davidkpiano! - You can now enqueue effects in state transitions.

  const store = createStore({
    context: {
      count: 0
    },
    on: {
      incrementDelayed: (context, event, enq) => {
        enq.effect(async () => {
          await new Promise((resolve) => setTimeout(resolve, 1000));
          store.send({ type: 'increment' });
        });
  
        return context;
      },
      increment: (context) => ({ count: context.count + 1 })
    }
  });

• #​5175 38aa9f518ee2f9a5f481306a1dc68c0ad47d28d5 Thanks @​davidkpiano! - The fromStore(config) function now only supports a single config object argument.

  const storeLogic = fromStore({
    context: (input: { initialCount: number }) => ({
      count: input.initialCount
    }),
    on: {
      inc: (ctx, ev: { by: number }) => ({
        ...ctx,
        count: ctx.count + ev.by
      })
    }
  });

• #​5175 38aa9f518ee2f9a5f481306a1dc68c0ad47d28d5 Thanks @​davidkpiano! - The createStoreWithProducer(…) function now only accepts two arguments: a producer and a config ({ context, on }) object.

  // Before
  // createStoreWithProducer(
  //   producer,
  //   {
  //     count: 0
  //   },
  //   {
  //     increment: (context) => {
  //       context.count++;
  //     }
  //   }
  // );
  
  // After
  createStoreWithProducer(producer, {
    context: {
      count: 0
    },
    on: {
      increment: (context) => {
        context.count++;
      }
    }
  });

• #​5175 38aa9f518ee2f9a5f481306a1dc68c0ad47d28d5 Thanks @​davidkpiano! - Only complete assigner functions that replace the context fully are supported. This is a breaking change that simplifies the API and provides more type safety.

  const store = createStore({
    context: {
      items: [],
      count: 0
    },
    on: {
  -   increment: { count: (context) => context.count + 1 }
  -   increment: (context) => ({ count: context.count + 1 })
  +   increment: (context) => ({ ...context, count: context.count + 1 })
    }
  })

• #​5175 38aa9f518ee2f9a5f481306a1dc68c0ad47d28d5 Thanks @​davidkpiano! - Emitted event types are now specified in functions on the emits property of the store definition:

  const store = createStore({
    // …
    emits: {
      increased: (payload: { upBy: number }) => {
        // You can execute a side-effect here
        // or leave it empty
      }
    },
    on: {
      inc: (ctx, ev: { by: number }, enq) => {
        enq.emit.increased({ upBy: ev.by });
  
        // …
      }
    }
  });

Minor Changes

• #​5175 38aa9f518ee2f9a5f481306a1dc68c0ad47d28d5 Thanks @​davidkpiano! - Added store.trigger API for sending events with a fluent interface:

  const store = createStore({
    context: { count: 0 },
    on: {
      increment: (ctx, event: { by: number }) => ({
        count: ctx.count + event.by
      })
    }
  });
  
  // Instead of manually constructing event objects:
  store.send({ type: 'increment', by: 5 });
  
  // You can now use the fluent trigger API:
  store.trigger.increment({ by: 5 });

  The trigger API provides full type safety for event names and payloads, making it easier and safer to send events to the store.

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone America/New_York, Automerge - Monday through Friday ( * * * * 1-5 ) in timezone America/New_York.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.