Repository navigation
chore: bump com.rokt:roktsdk from 6.1.3 to 6.1.4 in /Rokt.Widget/android in the gradle-patch-minor group - #309
Conversation
Bumps the gradle-patch-minor group in /Rokt.Widget/android with 1 update: [com.rokt:roktsdk](https://github.com/ROKT/sdk-android-source). Updates `com.rokt:roktsdk` from 6.1.3 to 6.1.4 - [Commits](https://github.com/ROKT/sdk-android-source/commits) --- updated-dependencies: - dependency-name: com.rokt:roktsdk dependency-version: 6.1.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: gradle-patch-minor ... Signed-off-by: dependabot[bot] <support@github.com>
🔒 Security Scan Complete✅ No security issues detected Scanned files against 45 rules. · Reviewed commit: 📜 Scan history (1 scan)
ℹ️ About PR Security AgentThis scan was performed by PR Security Agent, an automated security review tool for pull requests. See the User Guide for details on severity levels, feedback reactions, and scan configuration. Reply |
There was a problem hiding this comment.
Looks good, straightforward dependency version bump.
What was reviewed: the single-line diff bumping com.rokt:roktsdk from 6.1.3 to 6.1.4 in the Android Gradle dependencies block — confirmed no other lines or files changed, and the version string matches the PR description exactly.
Extended reasoning...
The change is a one-line patch-version bump of the com.rokt:roktsdk native dependency in Rokt.Widget/android/build.gradle, generated by dependabot. It touches no application code, no auth/crypto/permissions paths, and has no security-sensitive surface. The diff exactly matches the PR title and description, is minimal and mechanical, and the bug hunting system reported no findings, so this is safe to approve without further human review.
Bumps the gradle-patch-minor group in /Rokt.Widget/android with 1 update: com.rokt:roktsdk.
Updates
com.rokt:roktsdkfrom 6.1.3 to 6.1.4Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions