[Bug]: Actual fails to sync when run under Cloudflare Zero Trust due to the expired auth token and no CORS #1879

New Issue

Closed

opened 2026-02-28 19:57:04 -06:00 by GiteaMirror · 7 comments

GiteaMirror commented 2026-02-28 19:57:04 -06:00

Owner

Copy Link

Originally created by @gtrubach on GitHub (Feb 20, 2025).

Verified issue does not already exist?

• I have searched and found no existing issue

What happened?

Hi,

First of all thanks for this great project!

I'm running Actual behind Cloudflare with ZeroTrust. CF issues an CF_Authorization token after login which expires after 1 day. When expired, Actual fails to call /sync endpoint as CF rejects the request due to the expired token.

Access to fetch at 'https://<cf-account-name>.cloudflareaccess.com/cdn-cgi/access/login/<fqdn>?kid=<redacted>&redirect_url=%2Fsync%2Fsync&meta=<redacted>' (redirected from 'https://<fqdn>/sync/sync') from origin 'https://<fqdn>' 
has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. 
If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

There was a similar change lately https://github.com/actualbudget/actual/pull/3286, where some similar issues were fixed but unfortunately it does not work with CF ZeroTrust. But calling this code from PR works!

window.navigator.serviceWorker
      .getRegistration('/')
      .then(registration => {
        if (registration == null) return;
        return registration.unregister();
      })
      .then(() => {
        window.location.reload();
      });

This leads me to the thought that something is wrong with the if condition in this line https://github.com/actualbudget/actual/blob/master/packages/loot-core/src/platform/server/fetch/index.web.ts#L13. Also similar reports can be found in the mentioned PR https://github.com/actualbudget/actual/pull/3286#issuecomment-2646377751.

It would be great if this is fixed as it makes the setup a bit unusable due to the need to clean all cookies manually daily.

How can we reproduce the issue?

1. Setup Cloudflare zero trust application using any auth method
2. Put Actual behind it
3. Access Actual and login
4. Delete CF_Authorization cookie (or wait 1 day to expire)
5. Observe that server goes offline and sync calls fail.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @gtrubach on GitHub (Feb 20, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Hi, First of all thanks for this great project! I'm running Actual behind Cloudflare with ZeroTrust. CF issues an CF_Authorization token after login which expires after 1 day. When expired, Actual fails to call /sync endpoint as CF rejects the request due to the expired token. ``` Access to fetch at 'https://<cf-account-name>.cloudflareaccess.com/cdn-cgi/access/login/<fqdn>?kid=<redacted>&redirect_url=%2Fsync%2Fsync&meta=<redacted>' (redirected from 'https://<fqdn>/sync/sync') from origin 'https://<fqdn>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. ``` There was a similar change lately https://github.com/actualbudget/actual/pull/3286, where some similar issues were fixed but unfortunately it does not work with CF ZeroTrust. But calling this code from PR works! ``` window.navigator.serviceWorker .getRegistration('/') .then(registration => { if (registration == null) return; return registration.unregister(); }) .then(() => { window.location.reload(); }); ``` This leads me to the thought that something is wrong with the if condition in this line https://github.com/actualbudget/actual/blob/master/packages/loot-core/src/platform/server/fetch/index.web.ts#L13. Also similar reports can be found in the mentioned PR https://github.com/actualbudget/actual/pull/3286#issuecomment-2646377751. It would be great if this is fixed as it makes the setup a bit unusable due to the need to clean all cookies manually daily. ### How can we reproduce the issue? 1. Setup Cloudflare zero trust application using any auth method 2. Put Actual behind it 3. Access Actual and login 4. Delete CF_Authorization cookie (or wait 1 day to expire) 5. Observe that server goes offline and sync calls fail. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11

GiteaMirror added the bug label 2026-02-28 19:57:04 -06:00

GiteaMirror closed this issue 2026-02-28 19:57:05 -06:00

GiteaMirror commented 2026-02-28 19:57:06 -06:00

Author

Owner

Copy Link

@gtrubach commented on GitHub (Feb 20, 2025):

Also it seems it corrupted my pwa
I tried to switch servers back and forth, but now it says that the server is not running under provided URL. The only option is to delete all cookies which I cannot do as Edge on IPhone can only delete cookies for all web sites...

@gtrubach commented on GitHub (Feb 20, 2025): Also it seems it corrupted my pwa I tried to switch servers back and forth, but now it says that the server is not running under provided URL. The only option is to delete all cookies which I cannot do as Edge on IPhone can only delete cookies for all web sites...

GiteaMirror commented 2026-02-28 19:57:06 -06:00

Author

Owner

Copy Link

@mathisgauthey commented on GitHub (Feb 28, 2025):

Got the same issue on my end. Response body is not available to scripts (Reason: CORS Missing Allow Origin)

My setup is defined here and involves Cloudflare tunnel with access restriction and Nginx Proxy Manager.

@mathisgauthey commented on GitHub (Feb 28, 2025): Got the same issue on my end. `Response body is not available to scripts (Reason: CORS Missing Allow Origin)` My setup is defined [here](https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/4379) and involves Cloudflare tunnel with access restriction and Nginx Proxy Manager.

GiteaMirror commented 2026-02-28 19:57:06 -06:00

Author

Owner

Copy Link

@KenGrinder commented on GitHub (Mar 5, 2025):

How to Fix CORS Issues with Cloudflare Access (Advanced Settings)

Below are the settings I’m using in Cloudflare. I asked ChatGPT to write a guide based on my settings to make it easier for anyone else that may have the same issue. I have my session duration set to 15 minutes and it's been working fine for the past ~24 hours.

1. Open Your Application in Cloudflare Zero Trust

1. Log into your Cloudflare Zero Trust dashboard.
2. In the left-hand menu, navigate to Access → Applications.
3. Select the Access-protected application you need to configure.

2. Go to Advanced Settings → CORS

1. In the application view, click the Advanced settings tab near the top.
2. Under Advanced settings, select Cross-Origin Resource Sharing (CORS) settings.

3. Configure the CORS Settings

Below are the recommended settings for most cases:

• Bypass options requests to origin: Off
  This ensures Cloudflare injects CORS headers for OPTIONS (preflight) requests.

• Access-Control-Allow-Credentials: On
  Required if your app uses cookies or authorization headers.

• Access-Control-Max-Age (seconds): 86400
  Caches the preflight response for 24 hours.

• Access-Control-Allow-Origin:
  Add your specific domain here, for example https://actual.XXXXXXXXX.com.
  Avoid using “Allow all origins” if possible for better security.

• Access-Control-Allow-Methods: All methods
  Ensures the browser sees allowed methods like GET, POST, PUT, OPTIONS, etc.

• Access-Control-Allow-Headers: All http headers
  Alternatively, list only the headers you need (e.g. Content-Type, Authorization).

@KenGrinder commented on GitHub (Mar 5, 2025): # How to Fix CORS Issues with Cloudflare Access (Advanced Settings) Below are the settings I’m using in Cloudflare. I asked ChatGPT to write a guide based on my settings to make it easier for anyone else that may have the same issue. I have my session duration set to 15 minutes and it's been working fine for the past ~24 hours.  ## 1. Open Your Application in Cloudflare Zero Trust 1. **Log into** your [Cloudflare Zero Trust dashboard](https://dash.teams.cloudflare.com/). 2. In the left-hand menu, navigate to **Access → Applications**. 3. Select the **Access-protected application** you need to configure. ## 2. Go to *Advanced Settings* → *CORS* 1. In the application view, click the **Advanced settings** tab near the top. 2. Under **Advanced settings**, select **Cross-Origin Resource Sharing (CORS) settings**. ## 3. Configure the CORS Settings Below are the recommended settings for most cases: - **Bypass options requests to origin**: **Off** *This ensures Cloudflare injects CORS headers for OPTIONS (preflight) requests.* - **Access-Control-Allow-Credentials**: **On** *Required if your app uses cookies or authorization headers.* - **Access-Control-Max-Age (seconds)**: `86400` *Caches the preflight response for 24 hours.* - **Access-Control-Allow-Origin**: Add your specific domain here, for example `https://actual.XXXXXXXXX.com`. *Avoid using “Allow all origins” if possible for better security.* - **Access-Control-Allow-Methods**: **All methods** *Ensures the browser sees allowed methods like GET, POST, PUT, OPTIONS, etc.* - **Access-Control-Allow-Headers**: **All http headers** *Alternatively, list only the headers you need (e.g. `Content-Type, Authorization`).*

GiteaMirror commented 2026-02-28 19:57:07 -06:00

Author

Owner

Copy Link

@mathisgauthey commented on GitHub (Mar 6, 2025):

How to Fix CORS Issues with Cloudflare Access (Advanced Settings)

Below are the settings I’m using in Cloudflare. I asked ChatGPT to write a guide based on my settings to make it easier for anyone else that may have the same issue. I have my session duration set to 15 minutes and it's been working fine for the past ~24 hours.

1. Open Your Application in Cloudflare Zero Trust

1. **Log into** your [Cloudflare Zero Trust dashboard](https://dash.teams.cloudflare.com/).

2. In the left-hand menu, navigate to **Access → Applications**.

3. Select the **Access-protected application** you need to configure.

2. Go to Advanced Settings → CORS

1. In the application view, click the **Advanced settings** tab near the top.

2. Under **Advanced settings**, select **Cross-Origin Resource Sharing (CORS) settings**.

3. Configure the CORS Settings

Below are the recommended settings for most cases:

* **Bypass options requests to origin**: **Off**
  _This ensures Cloudflare injects CORS headers for OPTIONS (preflight) requests._

* **Access-Control-Allow-Credentials**: **On**
  _Required if your app uses cookies or authorization headers._

* **Access-Control-Max-Age (seconds)**: `86400`
  _Caches the preflight response for 24 hours._

* **Access-Control-Allow-Origin**:
  Add your specific domain here, for example `https://actual.XXXXXXXXX.com`.
  _Avoid using “Allow all origins” if possible for better security._

* **Access-Control-Allow-Methods**: **All methods**
  _Ensures the browser sees allowed methods like GET, POST, PUT, OPTIONS, etc._

* **Access-Control-Allow-Headers**: **All http headers**
  _Alternatively, list only the headers you need (e.g. `Content-Type, Authorization`)._

That is the thing I have been trying for the last two days without yet facing any issues, I can only vouch for that workaround.

It doesn't work on my end. Wether I set it up using an application with domain.tld and/or *.domain.tld, or creating a specific application on cloudflare for actual budget, I still get the same issues. Response body is not available to scripts (Reason: CORS Missing Allow Origin)

@mathisgauthey commented on GitHub (Mar 6, 2025): > # How to Fix CORS Issues with Cloudflare Access (Advanced Settings) > > Below are the settings I’m using in Cloudflare. I asked ChatGPT to write a guide based on my settings to make it easier for anyone else that may have the same issue. I have my session duration set to 15 minutes and it's been working fine for the past ~24 hours. > >  > ## 1. Open Your Application in Cloudflare Zero Trust > > 1. **Log into** your [Cloudflare Zero Trust dashboard](https://dash.teams.cloudflare.com/). > > 2. In the left-hand menu, navigate to **Access → Applications**. > > 3. Select the **Access-protected application** you need to configure. > > > ## 2. Go to _Advanced Settings_ → _CORS_ > > 1. In the application view, click the **Advanced settings** tab near the top. > > 2. Under **Advanced settings**, select **Cross-Origin Resource Sharing (CORS) settings**. > > > ## 3. Configure the CORS Settings > > Below are the recommended settings for most cases: > > * **Bypass options requests to origin**: **Off** > _This ensures Cloudflare injects CORS headers for OPTIONS (preflight) requests._ > > * **Access-Control-Allow-Credentials**: **On** > _Required if your app uses cookies or authorization headers._ > > * **Access-Control-Max-Age (seconds)**: `86400` > _Caches the preflight response for 24 hours._ > > * **Access-Control-Allow-Origin**: > Add your specific domain here, for example `https://actual.XXXXXXXXX.com`. > _Avoid using “Allow all origins” if possible for better security._ > > * **Access-Control-Allow-Methods**: **All methods** > _Ensures the browser sees allowed methods like GET, POST, PUT, OPTIONS, etc._ > > * **Access-Control-Allow-Headers**: **All http headers** > _Alternatively, list only the headers you need (e.g. `Content-Type, Authorization`)._ ~That is the thing I have been trying for the last two days without yet facing any issues, I can only vouch for that workaround.~ It doesn't work on my end. Wether I set it up using an application with `domain.tld` and/or `*.domain.tld`, or creating a specific application on cloudflare for actual budget, I still get the same issues. `Response body is not available to scripts (Reason: CORS Missing Allow Origin)`

GiteaMirror commented 2026-02-28 19:57:07 -06:00

Author

Owner

Copy Link

@KenGrinder commented on GitHub (Mar 9, 2025):

Ah, I can confirm shortly after my instance stopped working.

Full disclosure, I barely know TypeScript and this was mostly created using AI - So this code may be awful/redundant/or incorrect, This still requires the access control allow credentials and allow origin in CF-. I've only been able to test for a few hours in a Docker after deleting the CF_Auth tokens with success, will need some additional testing to confirm.

The issue is the worker for the app stays in cache and upon auth expiration it's not able to prompt for the access page while the service is registered in cache. (You can verify this but manually unregistering the service worker via inspect element) -

For this code change, Upon auth expiration, it unregisters the worker, and prompts to re-auth through Cloudflare access.
I definitely welcome any feedback from someone who actually knows what they are talking about.

Here is my proposed changed:

Updated Fetch Wrapper to Catch Authentication Redirects

File updated:
packages/loot-core/src/platform/server/fetch/index.web.ts

• Enhancement: Modified the fetch wrapper to use redirect: 'manual' for requests and handle both redirect indicators and opaque redirect responses.

Replaced:

import * as connection from '../connection';

export const fetch = async (
  input: RequestInfo | URL,
  options?: RequestInit,
): Promise<Response> => {
  const response = await globalThis.fetch(input, options);

  // Detect if the API query has been redirected to a different origin. This may indicate that the
  // request has been intercepted by an authentication proxy
  const originalUrl = new URL(input instanceof Request ? input.url : input);
  const responseUrl = new URL(response.url);
  if (response.redirected && responseUrl.host !== originalUrl.host) {
    connection.send('api-fetch-redirected');
    throw new Error(`API request redirected to ${responseUrl.host}`);
  }

  return response;
};

With:

import * as connection from '../connection';

export const fetch = async (
  input: RequestInfo | URL,
  options?: RequestInit
): Promise<Response> => {
  // Ensure manual redirect mode to catch login redirects
  const opts: RequestInit = { ...(options || {}), redirect: 'manual' };
  const response = await globalThis.fetch(input, opts);

  // Original request URL and final response URL
  const originalUrl = new URL(input instanceof Request ? input.url : String(input));
  const responseUrl = new URL(response.url);

  // If redirect occurred to a different origin or an opaque redirect was returned, trigger re-auth flow
  const differentOrigin = responseUrl.host !== originalUrl.host;
  if ((response.redirected && differentOrigin) || response.type === 'opaqueredirect') {
    connection.send('api-fetch-redirected');  // notify the app to reload/authenticate
    throw new Error(`API request redirected to auth login (${responseUrl.host})`);
  }

  return response;
};

---

Handle Authentication Redirect by Unregistering Service Worker

File updated:
packages/desktop-client/src/global-events.ts

• Enhancement: Update the global event handler to unregister the service worker before reloading when an auth redirect occurs.

Replaced:

const unlistenApiFetchRedirected = listen('api-fetch-redirected', () => {
  window.Actual.reload();
});

With:

let authRefreshInProgress = false;

const unlistenApiFetchRedirected = listen('api-fetch-redirected', async () => {
  if (authRefreshInProgress) return;
  authRefreshInProgress = true;
  console.warn('Detected auth redirect – unregistering service worker and reloading.');

  if ('serviceWorker' in navigator && navigator.serviceWorker.getRegistration) {
    try {
      const registration = await navigator.serviceWorker.getRegistration('/');
      if (registration) {
        await registration.unregister();
        console.log('Service worker unregistered.');
      }
    } catch (err) {
      console.error('Error unregistering service worker:', err);
    }
  }
  
  // Use a short delay to ensure unregistration completes before reloading
  setTimeout(() => {
    window.location.reload();
  }, 100);
});

---

Brief Explanation

• Issue: Previously, browser-handled redirects prevented proper detection of authentication issues, leading to silent CORS errors.
• Fix: Forcing redirect: 'manual' in fetch requests allows explicit detection of authentication redirects, prompting service worker removal and page reload to ensure the latest authentication state.

---

Forked Repository

I've forked Actual Budget with these enhancements for testing:

https://github.com/KenGrinder/actual_CF

I'd appreciate any testing or reviews to confirm no adverse effects are introduced by these changes.

@KenGrinder commented on GitHub (Mar 9, 2025): Ah, I can confirm shortly after my instance stopped working. Full disclosure, I barely know TypeScript and this was mostly created using AI - So this code may be awful/redundant/or incorrect, This still requires the access control allow credentials and allow origin in CF-. I've only been able to test for a few hours in a Docker after deleting the CF_Auth tokens with success, will need some additional testing to confirm. The issue is the worker for the app stays in cache and upon auth expiration it's not able to prompt for the access page while the service is registered in cache. (You can verify this but manually unregistering the service worker via inspect element) - For this code change, Upon auth expiration, it unregisters the worker, and prompts to re-auth through Cloudflare access. I definitely welcome any feedback from someone who actually knows what they are talking about. Here is my proposed changed: ### Updated Fetch Wrapper to Catch Authentication Redirects **File updated:**\ `packages/loot-core/src/platform/server/fetch/index.web.ts` - **Enhancement:** Modified the fetch wrapper to use `redirect: 'manual'` for requests and handle both redirect indicators and opaque redirect responses. #### Replaced: ```typescript import * as connection from '../connection'; export const fetch = async ( input: RequestInfo | URL, options?: RequestInit, ): Promise<Response> => { const response = await globalThis.fetch(input, options); // Detect if the API query has been redirected to a different origin. This may indicate that the // request has been intercepted by an authentication proxy const originalUrl = new URL(input instanceof Request ? input.url : input); const responseUrl = new URL(response.url); if (response.redirected && responseUrl.host !== originalUrl.host) { connection.send('api-fetch-redirected'); throw new Error(`API request redirected to ${responseUrl.host}`); } return response; }; ``` #### With: ```typescript import * as connection from '../connection'; export const fetch = async ( input: RequestInfo | URL, options?: RequestInit ): Promise<Response> => { // Ensure manual redirect mode to catch login redirects const opts: RequestInit = { ...(options || {}), redirect: 'manual' }; const response = await globalThis.fetch(input, opts); // Original request URL and final response URL const originalUrl = new URL(input instanceof Request ? input.url : String(input)); const responseUrl = new URL(response.url); // If redirect occurred to a different origin or an opaque redirect was returned, trigger re-auth flow const differentOrigin = responseUrl.host !== originalUrl.host; if ((response.redirected && differentOrigin) || response.type === 'opaqueredirect') { connection.send('api-fetch-redirected'); // notify the app to reload/authenticate throw new Error(`API request redirected to auth login (${responseUrl.host})`); } return response; }; ``` --- ### Handle Authentication Redirect by Unregistering Service Worker **File updated:**\ `packages/desktop-client/src/global-events.ts` - **Enhancement:** Update the global event handler to unregister the service worker before reloading when an auth redirect occurs. #### Replaced: ```typescript const unlistenApiFetchRedirected = listen('api-fetch-redirected', () => { window.Actual.reload(); }); ``` #### With: ```typescript let authRefreshInProgress = false; const unlistenApiFetchRedirected = listen('api-fetch-redirected', async () => { if (authRefreshInProgress) return; authRefreshInProgress = true; console.warn('Detected auth redirect – unregistering service worker and reloading.'); if ('serviceWorker' in navigator && navigator.serviceWorker.getRegistration) { try { const registration = await navigator.serviceWorker.getRegistration('/'); if (registration) { await registration.unregister(); console.log('Service worker unregistered.'); } } catch (err) { console.error('Error unregistering service worker:', err); } } // Use a short delay to ensure unregistration completes before reloading setTimeout(() => { window.location.reload(); }, 100); }); ``` --- ### Brief Explanation - **Issue:** Previously, browser-handled redirects prevented proper detection of authentication issues, leading to silent CORS errors. - **Fix:** Forcing `redirect: 'manual'` in fetch requests allows explicit detection of authentication redirects, prompting service worker removal and page reload to ensure the latest authentication state. --- ### Forked Repository I've forked Actual Budget with these enhancements for testing: [https://github.com/KenGrinder/actual\_CF](https://github.com/KenGrinder/actual_CF) I'd appreciate any testing or reviews to confirm no adverse effects are introduced by these changes.

GiteaMirror commented 2026-02-28 19:57:08 -06:00

Author

Owner

Copy Link

@Nerdtality commented on GitHub (Mar 11, 2025):

Can we get some kind of flag to set this to redirect correctly for CF ZTN?

@Nerdtality commented on GitHub (Mar 11, 2025): Can we get some kind of flag to set this to redirect correctly for CF ZTN?

GiteaMirror commented 2026-02-28 19:57:08 -06:00

Author

Owner

Copy Link

@Nerdtality commented on GitHub (Mar 11, 2025):

This seems to work as a temporary solution for CF ZTN Authentication

@Nerdtality commented on GitHub (Mar 11, 2025): This seems to work as a temporary solution for CF ZTN Authentication 

GiteaMirror referenced this issue 2026-02-28 20:50:08 -06:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #4002

GiteaMirror referenced this issue 2026-04-10 20:50:40 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #11057

GiteaMirror referenced this issue 2026-04-14 20:41:57 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #18365

GiteaMirror referenced this issue 2026-04-16 16:53:19 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #22612

GiteaMirror referenced this issue 2026-04-18 06:24:15 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #29927

GiteaMirror referenced this issue 2026-04-20 21:23:49 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #34197

GiteaMirror referenced this issue 2026-04-23 11:31:09 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #38433

GiteaMirror referenced this issue 2026-04-26 07:56:41 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #45822

GiteaMirror referenced this issue 2026-04-30 21:52:07 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #53306

GiteaMirror referenced this issue 2026-05-06 21:55:50 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #57656

GiteaMirror referenced this issue 2026-05-11 19:03:02 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #61988

GiteaMirror referenced this issue 2026-05-14 00:38:21 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #66369

GiteaMirror referenced this issue 2026-05-16 15:12:26 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #73987

GiteaMirror referenced this issue 2026-05-19 05:56:20 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #81683

GiteaMirror referenced this issue 2026-05-22 06:30:20 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #86186

GiteaMirror referenced this issue 2026-05-26 06:45:12 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #93900

GiteaMirror referenced this issue 2026-05-29 23:30:14 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #101698

GiteaMirror referenced this issue 2026-06-02 11:12:49 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #106268

GiteaMirror referenced this issue 2026-06-05 14:44:19 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #110819

GiteaMirror referenced this issue 2026-06-11 14:51:30 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #118719

GiteaMirror referenced this issue 2026-06-14 01:03:59 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #123431

GiteaMirror referenced this issue 2026-06-15 18:41:54 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #128109

GiteaMirror referenced this issue 2026-06-17 15:06:50 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #132797

GiteaMirror referenced this issue 2026-06-19 02:48:51 -05:00

[PR #1879] [MERGED] Maintenance: BudgetSummaries, MonthPicker, SidebarCategory components to tsx. #137499

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

claude/verify-migration-guardrails-i82c8m

cross-version-sync-stage2

api-browser-custom-data-dir

dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a

tabedzki/feat/replacing-month-picker-with-day-picker

delay-initial-sync-until-loaded

jfdoming/mobile-app-build

cross-version-sync-compat

jfdoming/api-tokens-part-1

jfdoming/api-tokens-part-2

jfdoming/api-tokens-part-3

jfdoming/mobile-app-updates

claude/budget-version-migration-compat-151jlr

claude/worker-error-serialization-9iqtl7

claude/react-table-library-research-afx83z

claude/issue-8401-regression-test-9nw9l3

jfdoming/mobile-app-foundation-part-1

jfdoming/mobile-app-scaffold

release

ai-fix-cleanup-def-8290

claude/relaxed-shannon-jusywa

claude/fervent-keller-s6f2fq

claude/determined-feynman-st1y9z

claude/wizardly-einstein-vi2wce

claude/sweet-albattani-7nseio

feat/bank-sync-per-budget-file

claude/affectionate-cannon-y0kc82

claude/dependabot-findings-m9pgmb

claude/mac-app-ios-publish-zjs1lz

claude/vigilant-tesla-aiiyos

depot-migrate-secrets-1781296330308

claude/quirky-cerf-v5qck7

claude/animation-removal-alternative-2etfh1

claude/netlify-preview-comments-consolidate-9XPYa

osc/7391-error-boundaries-reports

claude/pensive-dijkstra-7DYui

claude/server-app-version-mismatch-HTCGv

claude/pr-8027-review-feedback-mELuO

claude/zealous-wozniak-e5pO0

claude/intelligent-heisenberg-BSHJq

claude/translation-download-refactor-jFRsO

claude/mobile-performance-ideas-G9PAO

claude/github-issue-7988-5A5ly

blacksmith-migration-ff70d2d

claude/great-mayer-KRvOk

claude/react-native-ios-compilation-fcJh5

claude/serene-goldberg-58xv0

claude/kind-euler-LVG3K

release-automation/edge-nightly

7710-bundle-migrations

claude/fix-docker-build-error-WMfed

claude/llm-compatible-release-notes-t20Nr

7710-tests-tdd

cursor/transaction-table-rewrite-f077

claude/plan-ci-secure-context-OtEe1

claude/fix-issue-7667-DPXi3

cursor/resolve-pr-7449-ee11

claude/fix-typescript-build-error-JPtZ5

copilot/add-repository-configs-to-packages

worktree-compressed-drifting-ritchie

claude/api-consumer-verification-kfz1K

pr-7454

claude/fix-issue-7410-LLLQ4

revert-7281-generate-icons

react-query-useSchedules

copilot/sub-pr-6140

package-upgrades

v26.7.0

v26.6.0

v26.5.2

v26.5.1

v26.5.0

v26.4.0

v26.3.0

v26.2.1

v26.2.0

v26.1.0

v25.12.0

v25.11.0

v25.10.0

v25.9.0

v25.8.0

v25.7.1

v25.7.0

v25.6.1

v25.6.0

v25.5.0

v25.4.0

v25.3.1

v25.3.0

v25.2.1

v25.2.0

v25.1.0

v24.12.0

v24.11.0

v24.10.1

v24.10.0

v24.9.0

v24.8.0

v24.7.0

v24.6.0

v24.5.0

v24.4.0

v24.3.0

v24.2.0

v24.1.0

v23.12.0

v23.11.0

v23.10.0

v23.9.0

v23.8.1

v23.8.0

v23.7.2

v23.7.1

v23.7.0

v23.6.0

v23.5.0

v23.4.2

v23.4.1

v23.4.0

v23.3.2

v23.3.0

v23.2.9

v23.2.5

v23.1.12

v22.12.9

Labels

Clear labels

AI generated

API

bank sync

budgeting

bug

can’t replicate

dependencies

docker

documentation

electron

experimental feature

feature

feedback

goal templates

good first issue

help wanted

importers

maintenance

needs info

needs testing

needs triage

needs votes

openid

payees

pull-request

Mirrored from GitHub Pull Request

regression

reports

responsive

rules

schedules

server

✨ merged

split transactions

tech debt

tech-support

theme

transaction import

transaction reconciliation

transactions

translations

upstream

user interface

✅ approved

wontfix

No Label bug

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/actual#1879