chore(release): pull main into develop post release v1.139.1

[achettyiitr]

What are the changes introduced in this PR?

• Backmerge main to develop.

Summary by CodeRabbit

Release Notes v1.139.1

• Bug Fixes
  • Enabled audience support for Mailchimp destination

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This patch release (1.139.1) enables audience support for the Mailchimp destination by updating the configuration flag and bumping the version number with corresponding changelog documentation.

Changes

Cohort / File(s)	Summary
Release Management package.json, CHANGELOG.md	Version bump from 1.139.0 to 1.139.1 with new Bug Fixes entry documenting the Mailchimp audience support enablement.
Destination Configuration src/configurations/destinations/mailchimp/db-config.json	Updated isAudienceSupported flag from false to true to enable audience functionality for Mailchimp destination.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 The Mailchimp gates unlock today,
Audiences can now have their say!
One-point-one-three-nine, so bright,
A patch that sets audiences right. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is incomplete and lacks required sections from the template, including objectives, Linear task reference, checklist items, and detailed explanation of changes.	Complete the description template with all required sections: explain the changes in detail, reference the Linear task, list any dependent changes, fill out the developer and reviewer checklists, and clarify the purpose of enabling audience support for Mailchimp.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title clearly describes a backmerge of main into develop post-release v1.139.1, which aligns with the changeset containing version bumps and Mailchimp configuration updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore.main-to-develop

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (a3f4ad6) to head (4728d9a).
⚠️ Report is 7 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff            @@
##           develop     #2366   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           72        72           
  Branches         8         8           
=========================================
  Hits            72        72           

☔ 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.