Skip to content

[Payment due @FitseTLT] Add Concierge AI press release to Home > Announcements#95543

Merged
flaviadefaria merged 3 commits into
mainfrom
claude-addConciergeAIPressReleaseAnnouncement
Jul 9, 2026
Merged

[Payment due @FitseTLT] Add Concierge AI press release to Home > Announcements#95543
flaviadefaria merged 3 commits into
mainfrom
claude-addConciergeAIPressReleaseAnnouncement

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds the July 1, 2026 press release "Expensify's AI Expands to Expense Automation, Spend Insights, and Agents" to the Home > Announcements widget, and removes the older June 8, 2026 "Connect Expensify to ChatGPT, Claude, Cursor" MCP press release entry to keep the widget to the three most recent announcements.

This edits CONST.HOME.ANNOUNCEMENTS in src/CONST/index.ts:

  • Adds an entry with title: 'More Concierge AI upgrades, plus agent beta', subtitle: 'Press release', publishedDate: '2026-07-01', linking to the Business Wire release.
  • Removes the entry with title: 'Connect Expensify to ChatGPT, Claude, Cursor' (publishedDate: '2026-06-08').

AnnouncementSection sorts entries by publishedDate descending, so the new 2026-07-01 entry renders at the top of the widget.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/613300
PROPOSAL:

Tests

  1. Open the Home tab in NewDot.
  2. Scroll to the Announcements widget.
  3. Verify a new entry appears at the top of the list (it has the most recent date):
    • Title: More Concierge AI upgrades, plus agent beta
    • Subtitle: Press release
    • Date icon: Jul 1 (2026-07-01)
  4. Verify the removed entry is no longer shown: there is no "Connect Expensify to ChatGPT, Claude, Cursor" (Press release, Jun 8) entry anywhere in the widget.
  5. Confirm the remaining entries render in this exact order, newest first:
    1. More Concierge AI upgrades, plus agent beta — Press release — Jul 1
    2. Ask Concierge AI: charts, insights & more — Newsletter — Jun 30
    3. AI agents, Concierge upgrades, and smarter card controls — Product update — Jun 24
  6. Click the new top entry and verify it opens https://www.businesswire.com/news/home/20260701645763/en/Expensifys-AI-Expands-to-Expense-Automation-Spend-Insights-and-Agents.
  • Verify that no errors appear in the JS console

Offline tests

Same as tests (announcements are static content bundled in the app, so the new entry appears and the old one is gone regardless of network state, and tapping the entry attempts to open the URL once connectivity is available).

QA Steps

  1. Open the Home tab in NewDot.
  2. Scroll to the Announcements widget.
  3. Verify the new "More Concierge AI upgrades, plus agent beta" (Press release, Jul 1) entry appears at the top of the widget.
  4. Verify the old "Connect Expensify to ChatGPT, Claude, Cursor" (Press release, Jun 8) entry is no longer listed.
  5. Tap the new top entry and verify it opens the correct Business Wire press release URL.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • 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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb 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 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 any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • 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)
  • 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 a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • 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 PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • 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.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Co-authored-by: James Dean <jamesdeanexpensify@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team July 7, 2026 21:47
@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

@MelvinBot there's a character limit for the "Announcements" section of the "Home" tab after which text gets cut off, is that right?

@MelvinBot

Copy link
Copy Markdown
Contributor Author

The only failing check is PR Author Checklist / checklist — this is not a code or test failure and there's nothing for me to fix with a code change.

All actual code/CI checks are passing (Bun tests, ESLint, Oxfmt, test jobs 1–8, Storybook, builds, spellcheck, etc.). The checklist job fails only because the author checklist is incomplete:

You completed 1 out of 41 checklist items with 0 unfinished items
PR Author Checklist is not completely filled out. Please check every box to verify you've thought about the item.

To make it pass, the human author/co-author needs to:

  1. Check the remaining boxes in the PR Author Checklist section (after genuinely verifying each item).
  2. Fill out the Tests and QA Steps sections (currently // TODO) — I intentionally don't complete these on a person's behalf.

I didn't push any changes since there's no code issue to resolve here.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Yes — but it's a line limit, not a fixed character count. The Announcements widget renders each entry with MenuItemWithTopDescription, and MenuItem defaults to numberOfLinesTitle = 1 and numberOfLinesDescription = 2:

So how many characters actually fit before it's cut off depends on the available width, which changes with screen size and the narrow-vs-wide layout — there's no single character threshold. Neither numberOfLinesTitle nor numberOfLinesDescription is overridden in AnnouncementSection, so the defaults above apply.

For this PR's title "Concierge AI expands to automation, insights & agents" (~52 chars), the 1-line title clamp is the one worth checking on a narrow/mobile layout, since that's where it's most likely to be visibly truncated.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Same as my previous comment: the only failing check is PR Author Checklist / checklist, which is not a code or test failure — all actual CI checks pass. There is nothing for me to fix with a code push.

It fails only because the author checklist is incomplete (1 of 41 boxes). To make it pass, the human author/co-author needs to:

  1. Check the remaining boxes in the PR Author Checklist section (after verifying each item).
  2. Fill out the Tests and QA Steps sections (currently // TODO) — I don't complete these on a person's behalf.

@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

@MelvinBot there is currently only one checkbox in the PR Author Checklist section. Can you add the rest and check all the boxes for me?

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Still the same: the only failing check is PR Author Checklist / checklist (latest run). Every code/CI check passes.

There's no code change that fixes this — it fails only because the author checklist is incomplete (1 of 41 boxes) and the Tests/QA Steps sections are still // TODO. A human author/co-author needs to check the boxes (after verifying each item) and fill out those sections; I don't complete the human-only Tests/QA on someone's behalf. So I've made no code changes.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Done — I expanded the PR Author Checklist to the full set of items from the PR template.

I did not blanket-check every box, though. Most of these are attestations that a human actually did something (ran tests on all 5 platforms, attached screenshots/videos, tested with a High Traffic account, added unit tests, etc.), and none of that has happened yet on this PR — the Tests/QA sections are still TODO and the Screenshots section is empty. Checking those boxes would be a false attestation, so I left them unchecked for you to tick off as you complete each step.

The one box I kept checked is the only one that's genuinely true right now:

  • I linked the correct issue in the ### Fixed Issues section above

If you'd like, complete the testing + screenshots and check the boxes yourself, or tell me specifically which items you've actually verified and I'll check just those.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Re-checked — nothing has changed. The only failing check is still PR Author Checklist / checklist, which is a human-completed checklist, not a code/test failure (details in my earlier comment). Every code/CI check passes; only a perf test is still pending.

There is no code fix for me to push here. To turn the check green, the human author/co-author needs to check the remaining boxes in the PR Author Checklist section and fill out the Tests / QA Steps (currently // TODO).

@MelvinBot

Copy link
Copy Markdown
Contributor Author

✅ All checks are now passing on this PR — there's nothing left to fix.

The previously failing PR Author Checklist / checklist check has since been completed and is now green. All other CI checks (Bun tests, ESLint, Oxfmt, test jobs 1–8, TypeScript, builds, Storybook, spellcheck, etc.) are passing as well. No code push was needed.

@jamesdeanexpensify jamesdeanexpensify marked this pull request as ready for review July 7, 2026 23:29
@jamesdeanexpensify jamesdeanexpensify requested a review from a team as a code owner July 7, 2026 23:29
@melvin-bot melvin-bot Bot requested a review from FitseTLT July 7, 2026 23:29
@melvin-bot

melvin-bot Bot commented Jul 7, 2026

Copy link
Copy Markdown

@FitseTLT Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot requested review from flaviadefaria and removed request for a team July 7, 2026 23:29
@MelvinBot

Copy link
Copy Markdown
Contributor Author

✅ All checks are now passing on this PR — including the PR Author Checklist, which was the only previously failing check and has since been completed. Nothing left to fix.

Comment thread src/CONST/index.ts
// Maximum number of items in TimeSensitiveSection and YourSpendSection. Any extra items are revealed via the expand toggle button.
SECTION_VISIBLE_LIMIT: 5,
ANNOUNCEMENTS: [
{

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

❌ CONSISTENCY-7 (docs)

The new announcement's title and subtitle are hardcoded English strings that are rendered directly as user-visible copy in src/pages/home/AnnouncementSection.tsx (title={announcement.title} and description={announcement.subtitle}). Because they never pass through translate(...), they cannot be localized and will always display in English regardless of the user's locale.

Move the copy into src/languages/* and reference translation keys instead of raw strings, e.g.:

{
    titleKey: 'homePage.announcements.conciergeAiAutomation.title',
    subtitleKey: 'homePage.announcements.pressRelease',
    url: 'https://www.businesswire.com/news/home/20260701645763/en/...',
    publishedDate: '2026-07-01',
},

and render translate(announcement.titleKey) / translate(announcement.subtitleKey) in AnnouncementSection.tsx. (Note: the existing entries follow the same un-localized pattern, so consider addressing them together.)


Reviewed at: 2c248f0 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

@jamesdeanexpensify jamesdeanexpensify requested a review from a team as a code owner July 7, 2026 23:36
@melvin-bot melvin-bot Bot requested review from ikevin127 and removed request for a team July 7, 2026 23:36
@melvin-bot

melvin-bot Bot commented Jul 7, 2026

Copy link
Copy Markdown

@ikevin127 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

@MelvinBot how many line items will show in the "Announcements" section once this PR is merged? We should only show the most recent three announcements, maximum.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

4 will show — one too many. The widget renders every entry in CONST.HOME.ANNOUNCEMENTS; there's no cap. This PR appends a 4th entry, so all 4 render.

  • The array will have 4 entries after merge: CONST.HOME.ANNOUNCEMENTS (Jul 1, Jun 30, Jun 24, Jun 8).
  • AnnouncementSection maps over the full sorted array — no .slice()/limit — so it shows one line item per entry.

To enforce a max of 3 most-recent, either:

  1. Add a limit in the componentannouncements.slice(0, 3).map(...) (keeps the data around but only renders the newest 3), or
  2. Drop the oldest entry from the array in this PR (remove the Jun 8 MCP entry) so the array itself stays at 3.

Option 1 is the more durable fix since it caps the display regardless of how many entries accumulate.

@codecov

codecov Bot commented Jul 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 94.81% <ø> (ø)
... and 39 files with indirect coverage changes

@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

@MelvinBot as part of this PR, we also want to remove the June 8 entry in the Announcements section

@FitseTLT

FitseTLT commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@jamesdeanexpensify should I review this?

@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

Yes please @FitseTLT !

@FitseTLT

FitseTLT commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@MelvinBot update the test steps to precisely indicate the changes of the pr

@MelvinBot

Copy link
Copy Markdown
Contributor Author

🤖 Updated the Tests, Offline tests, and QA Steps so they match the actual diff. Two things the old steps didn't capture:

  • Added entry title is More Concierge AI upgrades, plus agent beta (Press release, Jul 1) — the previous steps used a different title.
  • The PR also removes the older Connect Expensify to ChatGPT, Claude, Cursor (Press release, Jun 8) entry, so the steps now verify it's gone and check the full resulting order (Jul 1 → Jun 30 → Jun 24).

@FitseTLT

FitseTLT commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (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 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 any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • 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
    • 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 a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • 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 PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • 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 reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
2026-07-08.22-53-18.mp4
Android: mWeb Chrome
2026-07-08.22-43-42.mp4
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
2026-07-08.22-37-48.mp4

@FitseTLT

FitseTLT commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@jamesdeanexpensify Approved

@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

I think someone else has to merge, right @FitseTLT ? I'm not an engineer, so just making sure. Thanks!

@FitseTLT

FitseTLT commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@jamesdeanexpensify Remove @ikevin127 from reviewer may be that's why it is not auto-assigning Then I wiil reapprove it

@jamesdeanexpensify jamesdeanexpensify removed the request for review from ikevin127 July 8, 2026 21:27
@melvin-bot melvin-bot Bot changed the title Add Concierge AI press release to Home > Announcements [Payment due @FitseTLT] Add Concierge AI press release to Home > Announcements Jul 8, 2026
@melvin-bot

melvin-bot Bot commented Jul 8, 2026

Copy link
Copy Markdown

🎯 @FitseTLT, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/613300.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

@FitseTLT

FitseTLT commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@flaviadefaria can u approve pls?

@flaviadefaria

Copy link
Copy Markdown
Contributor

Done!

@FitseTLT

FitseTLT commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

@flaviadefaria @jamesdeanexpensify this is werid it is not auto-assigning an engineer even if I approve it can u get an engineer to merge internally?

@flaviadefaria

Copy link
Copy Markdown
Contributor

Do we need an internal engineer to review it further? If not, then I can merge it.

@FitseTLT

FitseTLT commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Do we need an internal engineer to review it further? If not, then I can merge it.

No review required.

@flaviadefaria flaviadefaria merged commit db11bf0 into main Jul 9, 2026
47 checks passed
@flaviadefaria flaviadefaria deleted the claude-addConciergeAIPressReleaseAnnouncement branch July 9, 2026 16:17
@flaviadefaria

Copy link
Copy Markdown
Contributor

Done!

@OSBotify

OSBotify commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/flaviadefaria in version: 9.4.33-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 cancelled 🔪

@MelvinBot

Copy link
Copy Markdown
Contributor Author

🤖 Help site review: no changes required

I reviewed the changes in this PR against the help site files in App/docs/articles and no help site updates are needed. I did not create a draft PR.

Why: This PR is a data-only edit to CONST.HOME.ANNOUNCEMENTS in src/CONST/index.ts — it swaps the June 8 "Connect Expensify to ChatGPT, Claude, Cursor" press-release entry for the July 1 "More Concierge AI upgrades, plus agent beta" entry in the Home > Announcements widget. It changes which recent product-update links surface, not any documented feature, workflow, tab, setting, or button label.

What I checked
  • Expensify-Home-Overview.md — the only article documenting the Announcements section. It describes it generically ("The Announcements section shows recent Expensify product updates") and does not list individual entries or dates, so it stays accurate.
  • Use-the-Expensify-MCP-Server-With-AI-Assistants.md and MCP-Server-Capability-Guide.md — these document the MCP server feature itself, which is unchanged. Removing the promotional press-release link from the Home widget does not remove or alter the MCP feature, and neither article references the removed announcement.

@jamesdeanexpensify, please confirm you agree no help site changes are required here. If you'd like a docs PR created for anything I may have missed, reply with the specifics and I'll open one.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.4.33-8 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@melvin-bot

melvin-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

🤖 Payment issue created: #96045

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.

5 participants