[MelvinBot]

Details

Upgrades reassure 1.4.0 → 1.6.0, which bumps transitive mathjs 13.2.3 → 15.2.0 to fix two high-severity Dependabot alerts (unsafe object property setter). 1.6.1 is skipped because .npmrc min-release-age=7 blocks it.

Usage: dev-only. reassure runs the perf tests in tests/perf-test/ (npm run perf-test) and the reassurePerfTests.yml workflow. validateReassureOutput reads its output.json. Not part of the published package.

Change Log

1.6.0

• feat: calculate stability measures for test runs
• feat: disable owner stacks to improve render duration stability
• chore: switch to oxfmt

1.5.1

• Updated @callstack/reassure-danger

1.5.0

• feat: support async render/cleanup from React Native Testing Library v14
• chore: Jest 30 support
• chore: bump simple-git, update eslint to v10, upgrade deps (mathjs ^15.2.0, pretty-format ^30, zod ^4)

1.4.1 (reassure-measure only)

• deps: mathjs ^15.1.0, pretty-format ^30.2.0

Source: reassure CHANGELOG

Related Issues

https://github.com/Expensify/react-native-onyx/security/dependabot?q=is%3Aopen+package%3Amathjs

Linked E/App PR

Expensify/App#102135

Automated Tests

None added; dependency bump only. Melvin ran these locally on Node 24.22.1:

• npm run typecheck, npm run lint: pass
• npm test: 707/707 pass
• npx reassure: 101/101 perf tests pass
• reassure-compare + node .github/actions/javascript/validateReassureOutput: output.json parsed fine

Manual Tests

1. npm ci, then npm ls mathjs. Confirm only mathjs@15.2.0.
2. npm run perf-test. Confirm all perf tests pass and .reassure/current.perf is written.
3. Confirm the Reassure Performance Tests workflow passes on this PR.

Author Checklist

• I linked the correct issue in the ### Related Issues section above
• I linked the corresponding Expensify/App PR in the ### Linked E/App PR section above, and verified this change against it (E/App CI passed and manual testing completed)
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[chatgpt-codex-connector]

Codex Review Summary

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-26T13:11:13.646604Z	f0406da	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.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[madmax330]

I have read the CLA Document and I hereby sign the CLA

[madmax330]

recheck

[madmax330]

@MelvinBot can you fix the conflicts again?

Also find a PR that updates the react-native-onyx package and link it here as the related PR please

[amyevans]

@madmax330 I think Melvin doesn't respond in public repos other than App, you can get him to update the PR from your Slack DM if you want though (but looks like you're all set here...) 😄

[os-botify]

🚀 Published to npm in 3.0.135 🎉