Skip to content

Fix Account & Session Center reliability for v2.5.1 - #20

Merged
bubblegump30 merged 3 commits into
mainfrom
release/v2.5.1-source
Nov 8, 2026
Merged

bubblegump30 merged 3 commits into
mainfrom
release/v2.5.1-source

Conversation

@bubblegump30

@bubblegump30 bubblegump30 commented Nov 8, 2026 •

Copy link
Copy Markdown
Owner

Fixes Account & Session Center cancellation, policy retry, join tracking, background draft preservation and process-scan consistency for v2.5.1. Application styling and existing functionality are retained.

New behavioral regressions reproduce closure during authentication/handoff, Stop all during ticket acquisition, failed/initial policy retries, ended-session snapshot cleanup and a replacement session being falsely ended against an older process scan. Four original backend failures were reproduced before fixes. All 223 automated tests now pass. Actual Electron renderer checks preserve blurred scheduler/appearance/settings input identity and values across the background poll.

Windows source/release/layout verification gates run in CI. Synthetic verification does not terminate Roblox or change real accounts/Windows policies. Stable packaging includes Setup, Portable, Fast Folder, source and checksums. Existing optional-feature limits, CPU/FPS permission requirements and unsigned/exact-file VirusTotal notices remain documented.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-08T06:31:21.204490Z 51eca9b PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 51eca9b2d1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread package-lock.json Outdated
Comment on lines 127 to 129
"version": "2.5.1",
"resolved": "https://registry.npmjs.org/@electron/notarize/-/notarize-2.5.1.tgz",
"integrity": "sha512-jNT8nwH1f9X5GEITXaQ8IF/KdskvIkOFfB2CvwumsveVidzpSc+mvhhTMdAGSYF3O+Nq49lJ7y+ssODRXu06+A==",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Restore the unrelated notarize dependency's lockfile entries

On a clean dependency install, this changes the fetched @electron/notarize artifact to 2.5.1 while retaining the integrity hash recorded for 2.5.0. npm's package-lock documentation defines integrity as the hash “for the artifact that was unpacked in this location,” so a different version's tarball cannot satisfy this entry. The Windows release workflow's Install dependencies step runs npm ci before layout verification and packaging, making this inconsistent lock entry a release blocker. Restore the notarize version, resolved URL, and app-builder-lib dependency requirement to their original values rather than including this transitive package in the application version bump.

Useful? React with 👍 / 👎.

@bubblegump30
bubblegump30 merged commit 16fbbbe into main Nov 8, 2026
1 check passed
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