Skip to content

[NO QA] feat: Add tsgo for faster dev type checking #83228

Merged
roryabraham merged 12 commits into
Expensify:mainfrom
software-mansion-labs:dariusz-biela/feat/tsgo-for-dev
Feb 26, 2026
Merged

[NO QA] feat: Add tsgo for faster dev type checking #83228
roryabraham merged 12 commits into
Expensify:mainfrom
software-mansion-labs:dariusz-biela/feat/tsgo-for-dev

Conversation

@dariusz-biela

@dariusz-biela dariusz-biela commented Feb 23, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Add @typescript/native-preview (tsgo) as a dev dependency with npm run typecheck-tsgo command for faster type checking during development. Includes a dedicated tsconfig.tsgo.json and fixes for existing type errors detected by tsgo.

Benchmark (Expensify App):

tsc tsgo Change
Full check 116.3s 15.7s -86%
Incremental (no changes) 9.2s 1.6s -83%
Memory usage 6,428MB 5,463MB -15%

Bugs fixed (detected by tsgo, silently accepted by tsc):

[src/ONYXKEYS.ts] Remove duplicate VERIFY_3DS_SUBSCRIPTION key in OnyxValuesMapping
src/ONYXKEYS.ts:1321:5 - error TS2300: Duplicate identifier '[ONYXKEYS.VERIFY_3DS_SUBSCRIPTION]'.

1321     [ONYXKEYS.VERIFY_3DS_SUBSCRIPTION]: string;
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/ONYXKEYS.ts:1338:5 - error TS2300: Duplicate identifier '[ONYXKEYS.VERIFY_3DS_SUBSCRIPTION]'.

1338     [ONYXKEYS.VERIFY_3DS_SUBSCRIPTION]: string;
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[src/libs/API/types.ts] Remove duplicate command keys in API/types.ts
src/libs/API/types.ts:704:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.UPDATE_WORKSPACE_DESCRIPTION]'.
src/libs/API/types.ts:790:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.UPDATE_WORKSPACE_DESCRIPTION]'.
src/libs/API/types.ts:825:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.SET_POLICY_RULES_ENABLED]'.
src/libs/API/types.ts:826:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.SET_POLICY_CODING_RULE]'.
src/libs/API/types.ts:864:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.SET_POLICY_RULES_ENABLED]'.
src/libs/API/types.ts:865:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.SET_POLICY_CODING_RULE]'.
src/libs/API/types.ts:943:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.SAVE_CORPAY_ONBOARDING_BENEFICIAL_OWNER]'.
src/libs/API/types.ts:950:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.SAVE_CORPAY_ONBOARDING_BENEFICIAL_OWNER]'.
src/libs/API/types.ts:1084:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.UPDATE_XERO_AUTO_SYNC]'.
src/libs/API/types.ts:1085:5 - error TS2300: Duplicate identifier '[WRITE_COMMANDS.UPDATE_XERO_AUTO_SYNC]'.
src/libs/API/types.ts:1304:5 - error TS2300: Duplicate identifier '[READ_COMMANDS.GET_SAML_SETTINGS]'.
src/libs/API/types.ts:1307:5 - error TS2300: Duplicate identifier '[READ_COMMANDS.GET_SAML_SETTINGS]'.
[src/libs/EmojiUtils.tsx] Add null check for regexResult.indices[0] in EmojiUtils
src/libs/EmojiUtils.tsx:694:37 - error TS2532: Object is possibly 'undefined'.

694             const matchIndexStart = regexResult.indices[0][0];
                                        ~~~~~~~~~~~~~~~~~~~~~~

src/libs/EmojiUtils.tsx:695:35 - error TS2532: Object is possibly 'undefined'.

695             const matchIndexEnd = regexResult.indices[0][1];
                                      ~~~~~~~~~~~~~~~~~~~~~~
[src/libs/Navigation/types.ts] Remove duplicate EXPENSIFY_CARD screen params in Navigation/types.ts
src/libs/Navigation/types.ts:2552:5 - error TS2300: Duplicate identifier '[SCREENS.WORKSPACE.EXPENSIFY_CARD]'.

2552     [SCREENS.WORKSPACE.EXPENSIFY_CARD]: {
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/libs/Navigation/types.ts:2688:5 - error TS2300: Duplicate identifier '[SCREENS.WORKSPACE.EXPENSIFY_CARD]'.

2688     [SCREENS.WORKSPACE.EXPENSIFY_CARD]: {
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[src/libs/actions/IOU/index.ts] Remove unnecessary @ts-expect-error directives and fix statusNum assignment in IOU/index.ts
src/libs/actions/IOU/index.ts:11171:17 - error TS2578: Unused '@ts-expect-error' directive.

11171                 // @ts-expect-error - will be solved in https://github.com/Expensify/App/issues/73830
                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/libs/actions/IOU/index.ts:11175:17 - error TS2578: Unused '@ts-expect-error' directive.

11175                 // @ts-expect-error - will be solved in https://github.com/Expensify/App/issues/73830
                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/libs/actions/IOU/index.ts:11179:21 - error TS2578: Unused '@ts-expect-error' directive.

11179                     // @ts-expect-error - will be solved in https://github.com/Expensify/App/issues/73830
                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[src/libs/actions/Policy/Policy.ts] Restructure conditional OnyxUpdate spread to avoid undefined in Policy.ts
src/libs/actions/Policy/Policy.ts:481:9 - error TS2322: Type '{ onyxMethod: "set"; key: "bankAccountList"; value: BankAccountList; } | undefined' is not assignable to type 'OnyxUpdate<...>'.
  Type 'undefined' is not assignable to type 'OnyxUpdate<...>'.

481         ...(filteredBankAccountList !== bankAccountList
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
482             ? [
    ~~~~~~~~~~~~~~~
...
488               ]
    ~~~~~~~~~~~~~~~
489             : []),
    ~~~~~~~~~~~~~~~~~
[src/types/onyx/ReimbursementAccount.ts] Remove duplicate CORPAY field definitions in ReimbursementAccount.ts
src/types/onyx/ReimbursementAccount.ts:83:5 - error TS2300: Duplicate identifier '[INPUT_IDS.ADDITIONAL_DATA.CORPAY.OWNS_MORE_THAN_25_PERCENT]'.
src/types/onyx/ReimbursementAccount.ts:85:5 - error TS2300: Duplicate identifier '[INPUT_IDS.ADDITIONAL_DATA.CORPAY.ANY_INDIVIDUAL_OWN_25_PERCENT_OR_MORE]'.
src/types/onyx/ReimbursementAccount.ts:87:5 - error TS2300: Duplicate identifier '[INPUT_IDS.ADDITIONAL_DATA.CORPAY.BENEFICIAL_OWNERS]'.
src/types/onyx/ReimbursementAccount.ts:117:5 - error TS2300: Duplicate identifier '[INPUT_IDS.ADDITIONAL_DATA.CORPAY.OWNS_MORE_THAN_25_PERCENT]'.
src/types/onyx/ReimbursementAccount.ts:119:5 - error TS2300: Duplicate identifier '[INPUT_IDS.ADDITIONAL_DATA.CORPAY.ANY_INDIVIDUAL_OWN_25_PERCENT_OR_MORE]'.
src/types/onyx/ReimbursementAccount.ts:121:5 - error TS2300: Duplicate identifier '[INPUT_IDS.ADDITIONAL_DATA.CORPAY.BENEFICIAL_OWNERS]'.
[src/pages/signin/SignInPageLayout/BackgroundImage/index.tsx] Type lazy SVG import catch handlers in BackgroundImage/index.tsx
src/pages/signin/SignInPageLayout/BackgroundImage/index.tsx:10:5 - error TS2322: Type 'Promise<{ default: () => null; } | typeof import("*.svg")>' is not assignable to type 'Promise<{ default: () => null; }>'.
  Type '{ default: () => null; } | typeof import("*.svg")' is not assignable to type '{ default: () => null; }'.
    Type 'typeof import("*.svg")' is not assignable to type '{ default: () => null; }'.
      Types of property 'default' are incompatible.
        Type 'FC<SvgProps>' is not assignable to type '() => null'.

src/pages/signin/SignInPageLayout/BackgroundImage/index.tsx:15:5 - error TS2322: (same as above for desktop variant)

src/pages/signin/SignInPageLayout/BackgroundImage/index.tsx:58:38 - error TS2322: Type '{ width: number; }' is not assignable to type 'IntrinsicAttributes'.
  Property 'width' does not exist on type 'IntrinsicAttributes'.
[src/components/MoneyRequestReportView/MoneyRequestReportActionsList.tsx] Import ListRenderItemInfo from main @react-native/virtualized-lists export
src/components/MoneyRequestReportView/MoneyRequestReportActionsList.tsx:2:39 - error TS2307: Cannot find module '@react-native/virtualized-lists/Lists/VirtualizedList' or its corresponding type declarations.

2 import type {ListRenderItemInfo} from '@react-native/virtualized-lists/Lists/VirtualizedList';
                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/pages/inbox/report/ReportActionsList.tsx:1:39 - error TS2307: Cannot find module '@react-native/virtualized-lists/Lists/VirtualizedList' or its corresponding type declarations.

1 import type {ListRenderItemInfo} from '@react-native/virtualized-lists/Lists/VirtualizedList';
                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Fixed Issues

$ #83349

Tests

N/A — dev tooling only, no runtime changes.

Offline tests

N/A

QA Steps

N/A — no user-facing changes. [No QA]

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 shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • 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.ts 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 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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.

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

# Conflicts:
#	package.json
#	src/libs/API/types.ts
@dariusz-biela dariusz-biela changed the title feat: Add tsgo for faster dev type checking [NO QA] ]feat: Add tsgo for faster dev type checking Feb 25, 2026
@dariusz-biela dariusz-biela marked this pull request as ready for review February 25, 2026 11:22
@dariusz-biela dariusz-biela requested review from a team as code owners February 25, 2026 11:22
@melvin-bot melvin-bot Bot requested review from DylanDylann and trjExpensify and removed request for a team February 25, 2026 11:22
@melvin-bot

melvin-bot Bot commented Feb 25, 2026

Copy link
Copy Markdown

@DylanDylann 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 removed the request for review from a team February 25, 2026 11:22
@DylanDylann

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
    • MacOS: Desktop
  • 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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • 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 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)
  • 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.ts or at the top of the file that uses the constant) are defined as such
  • 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

@melvin-bot melvin-bot Bot requested a review from roryabraham February 26, 2026 06:24
@DylanDylann

Copy link
Copy Markdown
Contributor

@dariusz-biela It's so fast now

@trjExpensify

Copy link
Copy Markdown
Contributor

PR doesn’t need product input as a dev tooling PR. Unassigning and unsubscribing myself.

@trjExpensify trjExpensify removed their request for review February 26, 2026 12:33
@roryabraham roryabraham merged commit 7f40453 into Expensify:main Feb 26, 2026
38 checks passed
@codecov

codecov Bot commented Feb 26, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/ONYXKEYS.ts 100.00% <ø> (ø)
...equestReportView/MoneyRequestReportActionsList.tsx 57.23% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
src/libs/EmojiUtils.tsx 69.65% <100.00%> (ø)
src/libs/actions/IOU/index.ts 71.34% <ø> (ø)
src/libs/actions/Policy/Policy.ts 36.84% <100.00%> (+0.10%) ⬆️
src/pages/inbox/report/ReportActionsList.tsx 80.48% <ø> (ø)
.../signin/SignInPageLayout/BackgroundImage/index.tsx 0.00% <0.00%> (ø)
... and 7 files with indirect coverage changes

@OSBotify

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.

@github-actions

Copy link
Copy Markdown
Contributor

🚧 @roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

@dariusz-biela dariusz-biela changed the title [NO QA] ]feat: Add tsgo for faster dev type checking [NO QA] feat: Add tsgo for faster dev type checking Feb 26, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.3.27-0 🚀

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

@OSBotify

OSBotify commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.27-8 🚀

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

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