Release 9.10.1

[SpertsyanKM]

Release PR

What's New

— Improved security of network communication with Qonversion servers.

Summary by CodeRabbit

• Chores
  • Updated the SDK and package version to 9.10.1.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: qonversion/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 0f360c7d-1c3c-4a01-9b31-4f2461a1a628

📥 Commits

Reviewing files that changed from the base of the PR and between e946226 and 184c4eb.

📒 Files selected for processing (2)

• Runtime/Scripts/Internal/QonversionInternal.cs
• package.json

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• qonversion/go-micro (manual)

Limit details: You’ve used all 8 included reviews currently available. Your 59 included PR review attempts over the past 7 days set your current allowance at 8 reviews per hour.

---

📝 Walkthrough

Walkthrough

The package version and the internal Unity SDK version reported to native code change from 9.10.0 to 9.10.1.

Changes

Version alignment

Layer / File(s)	Summary
Version metadata alignment package.json, Runtime/Scripts/Internal/QonversionInternal.cs	The package version and QonversionInternal.SdkVersion change from 9.10.0 to 9.10.1.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 184c4

No actionable merge-blocking risk is identified in this version-alignment change.

---

Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

• Ignore (reviewers only)

❌ Failed checks (1 error, 1 inconclusive)

Check name	Status	Explanation	Resolution
Rollout And Recovery Evidence	❌ Error	The PR is a release PR, not only a metadata edit. It changes the runtime SDK version from 9.10.0 to 9.10.1, and the release notes claim a security behavior change. The repository has a merge-triggered…	Do not merge or enable the automatic publish path until the release record documents: verification of the network-security change and version alignment; the exact activation order from merge to publication and downstream use; stop signals a…
Title check	❓ Inconclusive	The title identifies the release version but does not name the affected system area or the behavioral outcome required by the check.	Update the title to include both details, for example: "Qonversion Unity SDK: improve network communication security in release 9.10.1".

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Behavior And Regression Safety	✅ Passed	The pull request changes only two release metadata values. It updates QonversionInternal.SdkVersion from 9.10.0 to 9.10.1, and the initialization path passes that value to StoreSdkInfo. It upd…
Security And Tenant Isolation	✅ Passed	PASS. The reviewed range changes only two version literals: SdkVersion from 9.10.0 to 9.10.1 and package.json version from 9.10.0 to 9.10.1. SdkVersion is passed to StoreSdkInfo; the p…
Contract And Data Compatibility	✅ Passed	PASS. The authoritative diff contains only two version-value changes: package.json changes 9.10.0 to 9.10.1, and QonversionInternal.cs changes the private SdkVersion value from 9.10.0 to 9.10.1. The e…

Full details: Rollout And Recovery Evidence

Explanation

The PR is a release PR, not only a metadata edit. It changes the runtime SDK version from 9.10.0 to 9.10.1, and the release notes claim a security behavior change. The repository has a merge-triggered publish workflow that invokes a reusable release publisher when a release branch PR with the one-click-release label merges to main. The PR description contains no verification results, activation order, stop signals, monitoring limits, rollback steps, or forward-recovery steps. The exact diff contains only the version changes, so it provides no bounded rollout or recovery evidence for the released behavior.

Resolution

Do not merge or enable the automatic publish path until the release record documents: verification of the network-security change and version alignment; the exact activation order from merge to publication and downstream use; stop signals and an owner who can halt publication; and tested rollback or forward-recovery steps. Add a manual approval or equivalent gate before the merge-triggered publisher can mutate the release channel.

• Fix all pre-merge checks with AI

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

Usage-based review receipt

• Mode: Continue automatically
• Reviewed files: 2
• Charged: $0.50
• View usage details

Note

This review was completed with usage-based billing: files reviewed beyond your plan's included limits are billed at $0.25/file. View usage-based billing.

---

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

[coderabbitai]

Pre-merge checks failed. Please resolve the failing checks before merging.