You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Chat - Markdown with code block is shown with box in preview #69102
Version Number: 9.1.98-2 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - internal Team
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Aug 23, 2025
Triggered auto assignment to @JmillsExpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Aug 23, 2025
Triggered auto assignment to @JS00001 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 23, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Aug 23, 2025
💬 A slack conversation has been started in #expensify-open-source
lanitochka17 commentedon Aug 23, 2025
Production:
0-02-01-9d12a469f582e007a67f0f7e4c88ca13ab90f77d84018e78a614d53f605340a1_9acfef8d03b7066c.1.mp4
mountiny commentedon Aug 23, 2025
I believe based on the convo here https://expensify.slack.com/archives/C01GTK53T8Q/p1755961028012119?thread_ts=1755900632.602309&cid=C01GTK53T8Q this is now expected after the markdown bump #68850 (comment) cc @dmkt9 @ikevin127
We reverted it now but lets make sure this is included in the expected behaviour in tests in the next PR