Skip to content

chore: Release 5.2.8#865

Open
onesignal-deploy wants to merge 2 commits intomainfrom
rel/5.2.8
Open

chore: Release 5.2.8#865
onesignal-deploy wants to merge 2 commits intomainfrom
rel/5.2.8

Conversation

@onesignal-deploy
Copy link
Copy Markdown
Collaborator

Channels: Current

🛠️ Native Dependency Updates

  • Update Android SDK from 5.8.0 to 5.8.1
    • feat: SDK-4417: emit ossdk.features_enabled in Otel per-event payload (#2631)
    • push token on startup when notification permission already granted (#2622)
    • fix: clear unprocessedOpenedNotifs queue after replaying to new listener (#2632)
    • fix: login/logout race causes subsequent calls to target previous user (#2618)

Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — straightforward release PR bumping version 5.2.7→5.2.8 and Android SDK 5.8.0→5.8.1.

Extended reasoning...

Overview

This PR is a routine version bump for the OneSignal Unity SDK release 5.2.8. It updates the version string from 5.2.7 to 5.2.8 across all package.json files, asmdef versionDefines, the Version/VersionHeader constants in OneSignal.cs and OneSignalPlatform.cs, the iOS setSdkVersion call (050207050208), the demo project bundleVersion, and the packages-lock.json. It also bumps the underlying Android native SDK dependency from 5.8.0 to 5.8.1 in OneSignalAndroidDependencies.xml, the demo's mainTemplate.gradle, and AndroidResolverDependencies.xml.

Security risks

None. Version bumps for a third-party native SDK and string constants do not introduce security-relevant logic. The Android SDK 5.8.1 changelog cited in the description (token-on-startup, login/logout race fix, listener replay queue clear) describes upstream behavior fixes, not security-sensitive code in this Unity wrapper.

Level of scrutiny

Low. Every change in this PR is mechanical and consistent — all version strings move in lockstep across the 14 modified files, the encoded version header (050207050208) matches the semantic version, and dependency declarations agree between the package descriptor and the demo's resolver outputs. No logic or API surface changes.

Other factors

The bug hunting system found no issues. The PR follows the established pattern for prior release PRs (e.g., #864 for 5.2.7). No outstanding reviewer comments.

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.

1 participant