chore(release): version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@react-native-motion-kit/swipe-deck@1.5.0

Minor Changes

• #23 3fecbb0 Thanks @saseungmin! - Add opt-in upward swipe support across gestures, programmatic actions, events, interaction state,
  and undo, with a public live interaction.intentDirection source for one-at-a-time reaction UI.

  function DeckControls() {
    const { swipeUp } = ProfileDeck.useDeckActions();
  
    return (
      <Pressable onPress={swipeUp}>
        <Text>Super Like</Text>
      </Pressable>
    );
  }
  
  <ProfileDeck.Root
    data={profiles}
    getKey={(item) => item.id}
    allowedDirections={["left", "right", "up"]}
  >
    <ProfileDeck.Card>
      {({ item }) => <ProfileCard profile={item} />}
    </ProfileDeck.Card>
  </ProfileDeck.Root>;

  Upward dismisses are backward-compatible and explicitly opt-in: omitting allowedDirections
  continues to allow only left and right. Gesture-driven up requires the default drag.mode: 'free';
  horizontal drag mode rejects an upward release through the existing snap-back motion, while
  swipeUp() remains available when 'up' is allowed.

  SwipeDirection, committed swipe and undo events, interaction.intentDirection, and
  interaction.dismissDirection now include 'up'. Only centered upward gestures enter the internal
  up cone; upper-left and upper-right diagonals stay horizontal. When the raw semantic winner is not
  allowed, intentDirection, progress, signedProgress, and numeric direction stay neutral while
  physical card translation still follows the finger. Programmatic up actions support the existing
  direct and springboard action-motion recipes, and an upward card can be restored through the
  existing undo flow.

  TypeScript consumers with exhaustive switch statements or Record<SwipeDirection, ...> mappings
  must add an 'up' branch even when a deck does not opt into upward dismisses.

Patch Changes

• #25 9be410c Thanks @saseungmin! - Prevent gesture-driven dismisses from briefly jumping when the finger is released on Android.
  Committed swipes now animate only their primary dismiss axis, preserving the final cross-axis drag
  position instead of restarting an unnecessary timing animation during the gesture handoff.

• #26 85ccb41 Thanks @saseungmin! - Reclaim factory registry entries after the final committed Root or public hook consumer for an
  id unmounts. Stable navigation route keys are now supported as deck instance ids, provided the key
  does not change while the screen is mounted.

  The duplicate-Root rule is unchanged: two simultaneous Roots from the same factory still require
  distinct ids. This release also changes the documented identity contract. Actions and interaction
  shared values stay stable only while at least one committed consumer retains the id; after a gap
  with zero committed consumers and deferred eviction, a later consumer for the same id receives a
  fresh action/interaction identity.