Skip to content

chore(release): pull hotfix-release/v1.126.1 into main#5044

Merged
ItsSudip merged 5 commits intomainfrom
hotfix-release/v1.126.1
Mar 16, 2026
Merged

chore(release): pull hotfix-release/v1.126.1 into main#5044
ItsSudip merged 5 commits intomainfrom
hotfix-release/v1.126.1

Conversation

@devops-github-rudderstack
Copy link
Contributor

👑 An automated PR

ItsSudip and others added 5 commits March 16, 2026 11:00
## What are the changes introduced in this PR?

Added one check for validating if the context is defined for an identify
call or not.

## What is the related Linear task?

Resolves INT-6054

## Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If
there are any dependent changes, **mandatorily** mention them here

### Any changes to existing capabilities/behaviour, mention the reason &
what are the changes ?

N/A

### Any new dependencies introduced with this change?

N/A

### Any new generic utility introduced or modified. Please explain the
changes.

N/A

### Any technical or performance related pointers to consider with the
change?

N/A

@coderabbitai review

<hr>

### Developer checklist

- [ ] My code follows the style guidelines of this project

- [ ] **No breaking changes are being introduced.**

- [ ] All related docs linked with the PR?

- [ ] All changes manually tested?

- [ ] Any documentation changes needed with this change?

- [ ] Is the PR limited to 10 file changes?

- [ ] Is the PR limited to one linear task?

- [ ] Are relevant unit and component test-cases added in **new
readability format**?

### Reviewer checklist

- [ ] Is the type of change in the PR title appropriate as per the
changes?

- [ ] Verified that there are no credentials or confidential data
exposed with the changes.
#5038)

## What are the changes introduced in this PR?

We are getting some unexpected errors, so adding a logger to verify why
those error might happen. Along with that, we are considering all 2xx as
a success scenario as we can't consider them as failures.

## What is the related Linear task?

Resolves INT-6069

## Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If
there are any dependent changes, **mandatorily** mention them here

### Any changes to existing capabilities/behaviour, mention the reason &
what are the changes ?

N/A

### Any new dependencies introduced with this change?

N/A

### Any new generic utility introduced or modified. Please explain the
changes.

N/A

### Any technical or performance related pointers to consider with the
change?

N/A

@coderabbitai review

<hr>

### Developer checklist

- [ ] My code follows the style guidelines of this project

- [ ] **No breaking changes are being introduced.**

- [ ] All related docs linked with the PR?

- [ ] All changes manually tested?

- [ ] Any documentation changes needed with this change?

- [ ] Is the PR limited to 10 file changes?

- [ ] Is the PR limited to one linear task?

- [ ] Are relevant unit and component test-cases added in **new
readability format**?

### Reviewer checklist

- [ ] Is the type of change in the PR title appropriate as per the
changes?

- [ ] Verified that there are no credentials or confidential data
exposed with the changes.
🔒 Scanned for secrets using gitleaks 8.28.0

## What are the changes introduced in this PR?

We are considering email form data fields as well.

## What is the related Linear task?

Resolves INT-

## Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If
there are any dependent changes, **mandatorily** mention them here

### Any changes to existing capabilities/behaviour, mention the reason &
what are the changes ?

N/A

### Any new dependencies introduced with this change?

N/A

### Any new generic utility introduced or modified. Please explain the
changes.

N/A

### Any technical or performance related pointers to consider with the
change?

N/A

@coderabbitai review

<hr>

### Developer checklist

- [ ] My code follows the style guidelines of this project

- [ ] **No breaking changes are being introduced.**

- [ ] All related docs linked with the PR?

- [ ] All changes manually tested?

- [ ] Any documentation changes needed with this change?

- [ ] Is the PR limited to 10 file changes?

- [ ] Is the PR limited to one linear task?

- [ ] Are relevant unit and component test-cases added in **new
readability format**?

### Reviewer checklist

- [ ] Is the type of change in the PR title appropriate as per the
changes?

- [ ] Verified that there are no credentials or confidential data
exposed with the changes.
…5041)

🔒 Scanned for secrets using gitleaks 8.28.0

We are getting email inside `data.checkout` for checkout-related events
like `checkout_started`, `checkout_address_info_submitted`,
`payment_info_submitted`, etc. But we are not mapping them properly to
`context.traits.email`, which is breaking the event flow in downstream
destinations like Google Ads enhanced conversion. So, updated the logic
to consider the mapping for checkout-related events.

## What is the related Linear task?

Resolves INT-6075

## Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If
there are any dependent changes, **mandatorily** mention them here

### Any changes to existing capabilities/behaviour, mention the reason &
what are the changes ?

N/A

### Any new dependencies introduced with this change?

N/A

### Any new generic utility introduced or modified. Please explain the
changes.

N/A

### Any technical or performance related pointers to consider with the
change?

N/A

@coderabbitai review

<hr>

### Developer checklist

- [ ] My code follows the style guidelines of this project

- [ ] **No breaking changes are being introduced.**

- [ ] All related docs linked with the PR?

- [ ] All changes manually tested?

- [ ] Any documentation changes needed with this change?

- [ ] Is the PR limited to 10 file changes?

- [ ] Is the PR limited to one linear task?

- [ ] Are relevant unit and component test-cases added in **new
readability format**?

### Reviewer checklist

- [ ] Is the type of change in the PR title appropriate as per the
changes?

- [ ] Verified that there are no credentials or confidential data
exposed with the changes.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 16, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: dfea304b-c925-4790-a808-24f0cb0fcebe

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)
Validation error: Unrecognized key(s) in object: 'auto_resolve_threads'
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch hotfix-release/v1.126.1
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

CodeRabbit can use Trivy to scan for security misconfigurations and secrets in Infrastructure as Code files.

Add a .trivyignore file to your project to customize which findings Trivy reports.

@codecov
Copy link

codecov bot commented Mar 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.27%. Comparing base (d281d8f) to head (86acb0b).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5044      +/-   ##
==========================================
- Coverage   92.32%   92.27%   -0.05%     
==========================================
  Files         657      656       -1     
  Lines       36139    35915     -224     
  Branches     8531     8470      -61     
==========================================
- Hits        33365    33142     -223     
+ Misses       2557     2535      -22     
- Partials      217      238      +21     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sonarqubecloud
Copy link

@ItsSudip ItsSudip merged commit ccae181 into main Mar 16, 2026
37 checks passed
@ItsSudip ItsSudip deleted the hotfix-release/v1.126.1 branch March 16, 2026 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants