Repository navigation
Prepare release 5.2.0 - #332
Conversation
🛣️ Rokt Platform Paved Roads Scan Complete✅ No paved-road issues detected Scanned files against 7 rules. · Reviewed commit: 📜 Scan history (1 scan)
ℹ️ About Rokt Platform Paved Roads AgentThis scan was performed by the Rokt Platform Paved Roads Agent, an automated paved-road standards review tool for pull requests. See the User Guide for details on severity levels, feedback reactions, and scan configuration. Reply |
🔒 Security Scan Complete✅ No security issues detected Scanned files against 50 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.
Nothing blocking. The comments below are optional suggestions. There is no need to push a fix for them before merging.
Beyond the inline finding, I checked whether RoktSampleApp has the same stale-lockfile problem. It doesn't: there's no committed lockfile there. VERSION, Rokt.Widget/package.json, the Rokt.Widget lockfile root entries and the new CHANGELOG compare links all use 5.2.0 consistently.
Extended reasoning...
This is a release-prep version bump from 5.1.2 to 5.2.0 across VERSION, package manifests, lockfiles and CHANGELOG.md, with no code changes and no security-sensitive surface. The confirmed inline finding about the stale SDK tarball reference in the ExpoTestApp lockfile means this should not be approved as-is.
Preparing for release 5.2.0 from
maintenance/5.x.Changelog
Added
Fixed
Changed