# Clerk Changelog — Page 22

# SAML Native Flows
URL: https://clerk.com/changelog/2025-02-05-saml-native.md
Date: 2025-02-05
Category: SSO
Description: Introducing SAML Native Flows for Expo and iOS SDKs, enabling secure enterprise authentication directly within your mobile apps

We're excited to announce support for SAML on both Expo and iOS SDKs.

Visit our documentation for step-by-step integration guides with [`@clerk/expo`](/docs/references/expo/use-sso) or [iOS](https://clerk.github.io/clerk-ios/documentation/clerk/signin/authenticatewithredirectstrategy)

---

# Ruby Backend SDK 4.0
URL: https://clerk.com/changelog/2025-01-30-ruby-sdk-4.md
Date: 2025-01-30
Category: SDK
Description: With expanded support for Rails, Rails API, Sinatra, Rack and more

We're excited to announce the release of the Clerk Ruby Backend SDK 4.0! Below is a quick preview of the major changes that we've made.

## First-Class Framework Support

In the past, outside of the standard Rails configuration, you had to create your own adapters and helpers to work with Clerk. With this release, we've added or expanded on first-class support for Rails, Rails API, Sinatra, and Rack so that everything works out of the box for the most popular frameworks and configurations.

Here's a quick preview of what 4.0 offers:

```ruby {{ title: 'Standalone SDK Usage' }}
Clerk.configure do |config|
  config.secret_key = 'sk_live_*****'
end

sdk = Clerk::SDK.new
sdk.users.get_user('*****')
```

```ruby {{ title: 'Ruby on Rails' }}
class AdminController < ApplicationController
  include Clerk::Authenticatable

  def index
    @user = clerk.user
  end
end
```

```ruby {{ title: 'Sinatra' }}
# Sinatra
class App < Sinatra::Base
  register Sinatra::Clerk

  get "/admin" do
    @user = clerk.user
    erb :index, format: :html5
  end
end
```

## OpenAPI

We've also brought the SDK into full alignment with our Backend API thanks to now generating parts of the SDK from our [OpenAPI spec](https://github.com/clerk/openapi-specs).

You can view the full generated [documentation on GitHub](https://github.com/clerk/clerk-http-client-ruby/tree/main/.generated#documentation-for-api-endpoints).

## Upgrading

Upgrade your gem by installing version `~> 4.0.0`:

```ruby {{ filename: 'Gemfile' }}
gem 'clerk-skd-ruby', '~> 4.0.0', require: 'clerk'
```

## Breaking Changes

Please note that this release contains a number of breaking changes. Please refer to the [upgrade guide](/docs/references/ruby/v4-upgrade-guide) for more information.

---

# Member search added to <OrganizationProfile />
URL: https://clerk.com/changelog/2025-01-28-search-on-org-profile.md
Date: 2025-01-28
Category: Orgs
Description: Easily find organization members on `<OrganizationProfile />` by searching for any information related to them.

Our `<OrganizationProfile />` component now supports searching across various member details such as email addresses, phone numbers, web3 wallets, usernames, user IDs, and first or last names. The search supports partial matches, making it easier than ever to locate the member you need.

Check it out now on your [`<OrganizationProfile />`](/docs/components/customization/organization-profile) component!

---

# Stable release of React Router SDK
URL: https://clerk.com/changelog/2025-01-23.md
Date: 2025-01-23
Category: SDK
Description: The React Router SDK is no longer in beta.

Back in December we announced the [Beta release of our React Router SDK](/changelog/2024-12-12-react-router-beta), a new official SDK that allows developers to add authentication and authorization into their React Router application in a matter of minutes.

After fixing some bugs and receiving positive feedback on the SDK we're transitioning the React Router SDK from beta to stable. The best part? You can just upgrade! There are **no changes** between the beta and stable release.

Upgrade your package by installing version `^1.0.0`:

```shell
npm install @clerk/react-router@latest
```

---

# Combined sign-in-or-up
URL: https://clerk.com/changelog/2025-01-16-sign-in-or-up.md
Date: 2025-01-16
Category: Product
Description: Start collecting sign-in and sign-ups within a single flow.

The `<SignIn />` component now allows users to sign up if they don't already have an existing account. When attempting a sign-in and no existing account is found, users will be prompted to continue through the flow to create an account, without needing to navigate to a separate route where `<SignUp />` is mounted.

The combined flow is a great option when email-based authentication strategies are used, as the sign-in and sign-up flows tend to be very similar.

To start using the combined sign-in-or-up flow, remove your existing `<SignUp />` usage, and unset `CLERK_SIGN_UP_URL`. Your existing `<SignIn />` component will now handle sign ups.

While this is the new default behavior, you can opt out of the combined flow by defining your `CLERK_SIGN_UP_URL`.

For more information, including how to build a dedicated `<SignUp />` page, visit the [documentation](/docs/references/nextjs/custom-sign-up-page).

---

# End of Support for Node SDK
URL: https://clerk.com/changelog/2025-01-10-node-sdk-eol.md
Date: 2025-01-10
Category: SDK
Description: Completing transition period for Clerk Node SDK

Today marks the end of support for `@clerk/clerk-sdk-node` as previously announced in our [October 2024 deprecation notice](/changelog/2024-10-08-express-sdk#deprecating-clerk-clerk-sdk-node). While we will no longer maintain this package, we've ensured a smooth transition path for all our users.

## What This Means

- The `@clerk/clerk-sdk-node` package has been moved to a separate [repository](https://github.com/clerk/sdk-node) for archival purposes
- Express users can migrate to the `@clerk/express` package, [see migration guide](/docs/upgrade-guides/node-to-express)
- Other Node.js projects should use our [JavaScript Backend SDK](/docs/references/backend/overview)