Release 0.138.0

[odlbot]

cp-at-mit

• Hubspot sync for SCIM created users (Hubspot sync for SCIM created users #3269) (05d17077)

annagav

• Make min max product price required (Make min max product price required #3262) (00e15b9a)

Chris Chudzicki

• Improve rich text field serialization (Improve rich text field serialization #3287) (2695b700)

renovate[bot]

• Update dependency webpack-dev-server to v5 [SECURITY] (Update dependency webpack-dev-server to v5 [SECURITY] #3270) (3f07808c)
• Update dependency lodash to v4.17.23 [SECURITY] (Update dependency lodash to v4.17.23 [SECURITY] #3239) (d9909c47)
• Update actions/cache digest to cdf6c1f (Update actions/cache digest to cdf6c1f #3282) (733011a3)

pre-commit-ci[bot]

• [pre-commit.ci] pre-commit autoupdate ([pre-commit.ci] pre-commit autoupdate #3247) (6e205463)

Dan Subak

• Test datagen for playwright test (Dansubak/202602 test datagen with code for playwright #3280) (c54ce8d2)

[github-actions]

OpenAPI Changes

Show/hide ## Changes for v0.yaml:

## Changes for v0.yaml:


## Changes for v1.yaml:


## Changes for v2.yaml:

Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

[sentry]

Bug: The post_save signal for syncing new users to Hubspot can trigger a race condition, as the Celery task is queued before the database transaction for the user is committed.
_{Severity: HIGH}

Suggested Fix

Wrap the call to sync_hubspot_user(instance) within a transaction.on_commit() lambda. This will defer the execution of the Celery task until after the database transaction that creates the user has successfully committed, preventing the race condition.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: users/signals.py#L14-L15

Potential issue: The `post_save` signal handler `sync_user_to_hubspot_on_create` queues
a Celery task to sync a new user to Hubspot. This signal fires after the user object is
saved but before the database transaction is committed. This creates a race condition
where the Celery worker may try to fetch the user from the database before the record is
visible, causing the task to fail with an object-not-found error. This is a known
anti-pattern, and other signal handlers in the codebase, such as for products, correctly
use `transaction.on_commit()` to defer the task until after the transaction is complete.

_{Did we get this right? 👍 / 👎 to inform future reviews.}