[Snyk] Upgrade @t3-oss/env-nextjs from 0.3.1 to 0.13.8 by tpsaint · Pull Request #4 · tpsaint/AutoGPT

tpsaint · 2025-09-09T17:45:16Z

Snyk has created this PR to upgrade @t3-oss/env-nextjs from 0.3.1 to 0.13.8.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 43 versions ahead of your current version.
The recommended version was released 3 months ago.

Release notes

Package name: @t3-oss/env-nextjs

0.13.8 - 2025-06-09
Patch Changes
- #353 31202b8 Thanks @ mmikhan! - feat: add Vite preset (https://vite.dev/guide/env-and-mode)
- #362 21d6d95 Thanks @ mmikhan! - feat: add WXT preset (https://wxt.dev/guide/essentials/config/environment-variables.html#built-in-environment-variables)
- Updated dependencies [31202b8, 21d6d95]:
  - @ t3-oss/env-core@0.13.8
0.13.7 - 2025-06-09
Patch Changes
- #357 216bc2d Thanks @ juliusmarminge! - feat: add arktype presets
- #354 221bdb5 Thanks @ mmikhan! - feat: add supabase vercel preset (https://vercel.com/marketplace/supabase)
- Updated dependencies [216bc2d, 221bdb5]:
  - @ t3-oss/env-core@0.13.7
0.13.6 - 2025-05-27
Patch Changes
- Updated dependencies [aa245ed]:
  - @ t3-oss/env-core@0.13.6
0.13.5 - 2025-05-27
Patch Changes
- Updated dependencies [73e90f5]:
  - @ t3-oss/env-core@0.13.5
0.13.4 - 2025-04-30
0.13.4-canary.2c99b41 - 2025-04-30
0.13.3 - 2025-04-30
0.13.2 - 2025-04-30
0.13.1 - 2025-04-30
0.13.1-canary.f66e736 - 2025-04-30
0.13.1-canary.c99c35e - 2025-04-30
0.13.1-canary.a5b80a2 - 2025-04-30
0.13.1-canary.95978c4 - 2025-04-30
0.13.0 - 2025-04-23
0.12.0 - 2025-01-25
0.12.0-canary.2 - 2025-01-25
0.12.0-canary.1 - 2025-01-25
0.11.1 - 2024-08-25
0.11.0 - 2024-07-22
0.10.1 - 2024-04-23
0.10.0 - 2024-04-22
0.9.3-canary.b0cc17a - 2024-04-22
0.9.2 - 2024-02-08
0.9.2-canary.a2c1806 - 2024-02-08
0.9.1 - 2024-02-08
0.9.0 - 2024-02-08
0.8.0 - 2024-01-24
0.7.3 - 2024-01-12
0.7.3-manual.2 - 2024-01-12
0.7.3-manual.1 - 2024-01-12
0.7.3-manual.0 - 2024-01-12
0.7.2 - 2024-01-12
0.7.1 - 2023-10-16
0.7.0 - 2023-10-05
0.6.2-canary.72384d2 - 2023-10-05
0.6.1 - 2023-08-17
0.6.0 - 2023-06-25
0.5.1 - 2023-06-25
0.5.0 - 2023-06-25
0.4.2-canary.6984043 - 2023-06-25
0.4.1 - 2023-06-16
0.4.1-canary.40f9204 - 2023-05-30
0.4.0 - 2023-05-29
0.3.1 - 2023-05-06

from @t3-oss/env-nextjs GitHub release notes

Important

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

📜 Customise PR templates

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

…ution (Significant-Gravitas#10328) ## Summary This PR enhances the node execution stats tracking system to properly handle nested graph executions and additional cost/step metrics: - **Add extra_cost and extra_steps fields** to `NodeExecutionStats` model for tracking additional metrics from sub-graphs - **Update AgentExecutorBlock** to merge nested execution stats from sub-graphs into the parent execution - **Fix stats update mechanism** in `execute_node` to use in-place updates instead of `model_copy` for better performance - **Add proper tracking** of extra costs and steps in graph execution stats aggregation ## Changes Made - Modified `backend/backend/data/model.py` to add `extra_cost` and `extra_steps` fields - Updated `backend/backend/blocks/agent.py` to merge stats from nested graph executions - Fixed `backend/backend/executor/manager.py` to properly update execution stats and aggregate extra metrics ## Test Plan - [x] Verify that nested graph executions properly propagate their stats to parent graphs - [x] Test that extra costs and steps are correctly tracked and aggregated - [x] Ensure debug logging provides useful information for monitoring - [x] Run existing tests to ensure no regressions - [x] Test with multi-level nested agent graphs 🤖 Generated with [Claude Code](https://claude.ai/code) --------- Co-authored-by: Claude <noreply@anthropic.com>

This PR simply removes the MIT Icon from the main README.md

…nificant-Gravitas#10360) ### Motivation 💡 The previous Discord badge in the README used `dcbadge.vercel.app`, which often fails to render correctly and displays an invalid or broken badge. ### Changes 🛠️ - Replaced the broken badge with a `shields.io` Discord badge that is visually consistent with the Twitter badge - Ensures clearer visual guidance and a more professional appearance ### Notes ✏️ This PR only updates the `README.md` no frontend, backend, or configuration files are touched. This change improves the aesthetics and onboarding experience for new contributors. Screenshot of the issue: <img width="405" height="47" alt="Screenshot 2025-07-12 175316" src="https://github.com/user-attachments/assets/41f7355c-f795-4163-855f-3d01f2478dd7" /> --------- Co-authored-by: Ubbe <hi@ubbe.dev> Co-authored-by: Bently <Github@bentlybro.com> Co-authored-by: Bently <tomnoon9@gmail.com>

…s#10357) Currently, my agents count is showing the initial agent count loads on the library and then adding more agents after pagination. ### Changes 🏗️ - I’ve used `total_items` inside the pagination response and shown the correct result. ### Demo https://github.com/user-attachments/assets/b9a2cf18-c9fc-42f8-b0d4-3f8a7ad3cbc5 ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Manually test everything, and it works fine.

…vitas#10354) ## Changes 🏗️ Disable the Cloudflare check: <img width="600" height="861" alt="Screenshot 2025-07-11 at 18 51 46" src="https://github.com/user-attachments/assets/792ecca0-967e-4cef-a562-789125452d2f" /> On Vercel previews, so we can use previews for testing Front-end only changes. Vercel previews have dynamically generated URLs: ``` https://{branch}-{commit}-significant-gravitas.vercel.app/login ``` So if Cloudflare does not support URL wildcards we will neeed to do this 🙇🏽 ( _as an experiment_ ) ## Checklist 📋 ### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] You can login on the preview ### For configuration changes: None

…10342) ## Changes 🏗️ - Put `Continue with Google` button below the other button on the forms ( _to confirm with design_ ) - Ensure some vertical spacing so the forms don't end touching the header on small screens - Apply style adjustments asked by design on navbar links ## Checklist 📋 ### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Check the above ### For configuration changes: None

…utogpt_platform/frontend (Significant-Gravitas#10385) [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=chromatic&package-manager=npm_and_yarn&previous-version=11.25.2&new-version=13.1.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…/autogpt_platform/frontend with 4 updates (Significant-Gravitas#10382) Bumps the development-dependencies group in /autogpt_platform/frontend with 4 updates: [@playwright/test](https://github.com/microsoft/playwright), [@tanstack/react-query-devtools](https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools), [msw](https://github.com/mswjs/msw) and [prettier-plugin-tailwindcss](https://github.com/tailwindlabs/prettier-plugin-tailwindcss). Updates `@playwright/test` from 1.53.2 to 1.54.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/playwright/releases"><code>@playwright/test</code>'s releases</a>.</em></p> <blockquote> <h2>v1.54.1</h2> <h3>Highlights</h3> <p><a href="https://redirect.github.com/microsoft/playwright/issues/36650">microsoft/playwright#36650</a> - [Regression]: 1.54.0 breaks downloading browsers when an HTTP(S) proxy is used</p> <h2>Browser Versions</h2> <ul> <li>Chromium 139.0.7258.5</li> <li>Mozilla Firefox 140.0.2</li> <li>WebKit 26.0</li> </ul> <p>This version was also tested against the following stable channels:</p> <ul> <li>Google Chrome 140</li> <li>Microsoft Edge 140</li> </ul> <h2>v1.54.0</h2> <h2>Highlights</h2> <ul> <li> <p>New cookie property <code>partitionKey</code> in <a href="https://playwright.dev/docs/api/class-browsercontext#browser-context-cookies">browserContext.cookies()</a> and <a href="https://playwright.dev/docs/api/class-browsercontext#browser-context-add-cookies">browserContext.addCookies()</a>. This property allows to save and restore partitioned cookies. See <a href="https://developer.mozilla.org/en-US/docs/Web/Privacy/Guides/Privacy_sandbox/Partitioned_cookies">CHIPS MDN article</a> for more information. Note that browsers have different support and defaults for cookie partitioning.</p> </li> <li> <p>New option <code>noSnippets</code> to disable code snippets in the html report.</p> <pre lang="js"><code>import { defineConfig } from '@playwright/test'; <p>export default defineConfig({ reporter: [['html', { noSnippets: true }]] }); </code></pre></p> </li> <li> <p>New property <code>location</code> in test annotations, for example in <a href="https://playwright.dev/docs/api/class-testresult#test-result-annotations">testResult.annotations</a> and <a href="https://playwright.dev/docs/api/class-testinfo#test-info-annotations">testInfo.annotations</a>. It shows where the annotation like <code>test.skip</code> or <code>test.fixme</code> was added.</p> </li> </ul> <h2>Command Line</h2> <ul> <li> <p>New option <code>--user-data-dir</code> in multiple commands. You can specify the same user data dir to reuse browsing state, like authentication, between sessions.</p> <pre lang="bash"><code>npx playwright codegen --user-data-dir=./user-data </code></pre> </li> <li> <p>Option <code>-gv</code> has been removed from the <code>npx playwright test</code> command. Use <code>--grep-invert</code> instead.</p> </li> <li> <p><code>npx playwright open</code> does not open the test recorder anymore. Use <code>npx playwright codegen</code> instead.</p> </li> </ul> <h2>Miscellaneous</h2> <ul> <li>Support for Node.js 16 has been removed.</li> <li>Support for Node.js 18 has been deprecated, and will be removed in the future.</li> </ul> <h2>Browser Versions</h2> <ul> <li>Chromium 139.0.7258.5</li> <li>Mozilla Firefox 140.0.2</li> <li>WebKit 26.0</li> </ul> <p>This version was also tested against the following stable channels:</p>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/playwright/commit/97b6b881b733f752f1980cc8a92e80087504c9e9"><code>97b6b88</code></a> chore: mark 1.54.1 (<a href="https://redirect.github.com/microsoft/playwright/issues/36655">#36655</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/0071756019d678460ef832582e15ba37466cfd62"><code>0071756</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/36654">#36654</a>): Revert "fix: get rid of url.parse in network code" (<a href="https://redirect.github.com/microsoft/playwright/issues/36654">#36654</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/3da07a7049284e0c89ae65c95b955abad95e9f57"><code>3da07a7</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/36625">#36625</a>): chore: render overlay on top of modal dom content</li> <li><a href="https://github.com/microsoft/playwright/commit/b01d0d1e5f79acdca402106f37f17c7ed88434ae"><code>b01d0d1</code></a> chore: mark v1.54.0 (<a href="https://redirect.github.com/microsoft/playwright/issues/36626">#36626</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/12834b026ecc956fa337444a834f8062a59889d0"><code>12834b0</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/36624">#36624</a>): chore: update v1.54 release notes</li> <li><a href="https://github.com/microsoft/playwright/commit/82ce7360fd0fdb3d995261bb1812e677c5ddfc1f"><code>82ce736</code></a> test: remove stale fixme/skips in capabilities spec (<a href="https://redirect.github.com/microsoft/playwright/issues/36617">#36617</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/fab30432b1518cf2e9ff89a0422644df4e19ad1b"><code>fab3043</code></a> chore: v1.54 release notes (<a href="https://redirect.github.com/microsoft/playwright/issues/36620">#36620</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/ba32a2446742e1f571d1431523c3bb81a0a5898b"><code>ba32a24</code></a> chore: push action in context to the recorder app (<a href="https://redirect.github.com/microsoft/playwright/issues/36611">#36611</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/090e5aa754196869aadb9486c40f55601d4cd7fd"><code>090e5aa</code></a> chore: update WebKit version to 26.0 (<a href="https://redirect.github.com/microsoft/playwright/issues/36619">#36619</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/2edbe2562f3166a7960ae8a238aec8d1f90a6eff"><code>2edbe25</code></a> chore: update browser_patches to 9638cca873674fdb6c97a524be0d3ae4874f805a (<a href="https://redirect.github.com/microsoft/playwright/issues/3">#3</a>...</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/playwright/compare/v1.53.2...v1.54.1">compare view</a></li> </ul> </details> <br /> Updates `@tanstack/react-query-devtools` from 5.81.5 to 5.83.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/TanStack/query/releases"><code>@tanstack/react-query-devtools</code>'s releases</a>.</em></p> <blockquote> <h2>v5.83.0</h2> <p>Version 5.83.0 - 7/11/25, 5:00 PM</p> <h2>Changes</h2> <h3>Feat</h3> <ul> <li>core: QueryObserver returns isEnabled flag (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9408">#9408</a>) (23c8908) by Dominik Dorfmeister</li> </ul> <h3>Test</h3> <ul> <li>solid-query/suspense: remove "vi.waitFor", and add "advanceTimersByTimeAsync", "expect" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9407">#9407</a>) (0569891) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>svelte-query/createMutation: switch to fake timers, replace "waitFor" with "vi.waitFor", and add "expect" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9382">#9382</a>) (d6930fd) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>svelte-query/createQueries: switch to fake timers, and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9383">#9383</a>) (ab7fd72) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>svelte-query/createQuery: switch to fake timers, replace "waitFor" with "vi.waitFor", and add "expect" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9384">#9384</a>) (2212fff) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>svelte-query/useIsFetching: switch to fake timers, add "expect", "vi.waitFor", and replace "findByText" with "getByText" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9386">#9386</a>) (06cb8eb) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useIsMutating: remove "vi.waitFor", and add "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9404">#9404</a>) (9ecfbf7) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useMutationState: remove "vi.waitFor", and add "advanceTimersByTimeAsync", "expect" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9405">#9405</a>) (89f9483) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useQueries: remove "vi.waitFor", and add "advanceTimersByTimeAsync", "expect" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9406">#9406</a>) (daad8e3) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>svelte-query/createInfiniteQuery: switch to fake timers, and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9381">#9381</a>) (b32904c) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useIsFetching: remove "vi.waitFor", and add "advanceTimersByTimeAsync", "expect" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9403">#9403</a>) (e2bcbe8) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/transition: remove "vi.waitFor", and add "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9402">#9402</a>) (eb1cab7) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/QueryClientProvider: remove "vi.waitFor", and add "advanceTimersByTimeAsync", "expect" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9401">#9401</a>) (93978d3) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>svelte-query/useMutationState: switch to fake timers, and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9388">#9388</a>) (32467aa) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>svelte-query/useIsMutating: switch to fake timers, add "expect", "vi.waitFor", and replace "findByText" with "getByText" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9387">#9387</a>) (c597f76) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useIsFetching: switch to fake timers, replace "waitFor" with "vi.waitFor" and "findByText" with "getByText" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9377">#9377</a>) (bce4d7e) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>svelte-query/QueryClientProvider: switch to fake timers, replace "waitFor" with "vi.waitFor", and add "expect" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9385">#9385</a>) (c0fd94e) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useQueries: switch to fake timers and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9380">#9380</a>) (f7c83c2) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/suspense: switch to fake timers and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9375">#9375</a>) (d1c8cff) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useMutationState: switch to fake timers and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9379">#9379</a>) (94f2150) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useIsMutating: switch to fake timers and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9378">#9378</a>) (509064a) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/transition: switch to fake timers and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9376">#9376</a>) (27d82a7) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/useInfiniteQuery: switch to fake timers, and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9391">#9391</a>) (a0aeac0) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>solid-query/QueryClientProvider: switch to fake timers and replace "waitFor" with "vi.waitFor" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9374">#9374</a>) (c66af8a) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>vue-query/vueQueryPlugin: switch to fake timers and replace "sleep" with "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9372">#9372</a>) (8c79719) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>vue-query/useIsMutating: switch to fake timers and replace "sleep" with "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9373">#9373</a>) (47f7e86) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>vue-query/useIsFetching: switch to fake timers and replace "sleep" with "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9370">#9370</a>) (367a96e) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>vue-query/useQueries: switch to fake timers and replace "sleep" with "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9369">#9369</a>) (fc0b23e) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>vue-query/queryClient: switch to fake timers and replace "sleep" with "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9371">#9371</a>) (79893c8) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>vue-query/useInfiniteQuery: switch to fake timers and replace "sleep" with "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9368">#9368</a>) (fc2a95c) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>react-query/usePrefetchQuery: remove "vi.waitFor" and add "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9355">#9355</a>) (c9daf2c) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>react-query/useQueries: remove "waitFor" and add "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9367">#9367</a>) (fd7c655) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>react-query/useInfiniteQuery: remove "vi.waitFor" and add "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9366">#9366</a>) (f6085d0) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>react-query/useMutation: remove "vi.waitFor", add "advanceTimersByTimeAsync" and replace "findByText" with "getByText" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9352">#9352</a>) (c680879) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>react-query/mutationOptions: switch to fake timers, remove "vi.waitFor", and add "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9397">#9397</a>) (5765378) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>react-query/suspense: remove "vi.waitFor" and add "advanceTimersByTime" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9350">#9350</a>) (f580f08) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>react-query/useQuery: remove "vi.waitFor", add "advanceTimersByTimeAsync" and replace "findByText" with "getByText" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9363">#9363</a>) (eaf768b) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> <li>react-query/useSuspenseQueries: remove "waitFor" and add "advanceTimersByTimeAsync" (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9356">#9356</a>) (a0a0812) by <a href="https://github.com/sukvvon"><code>@sukvvon</code></a></li> </ul> <h2>Packages</h2>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/TanStack/query/commit/390424bcdd547d238148e72926f75c181e342976"><code>390424b</code></a> release: v5.83.0</li> <li><a href="https://github.com/TanStack/query/commit/4287e68336e6602aea2e4c60511f983d15eb7c98"><code>4287e68</code></a> release: v5.82.0</li> <li><a href="https://github.com/TanStack/query/commit/4425423588713311d5d949fc29ccfa647e927c98"><code>4425423</code></a> chore(*): migrate tsup configuration files to TypeScript format (<a href="https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools/issues/9330">#9330</a>)</li> <li>See full diff in <a href="https://github.com/TanStack/query/commits/v5.83.0/packages/react-query-devtools">compare view</a></li> </ul> </details> <br /> Updates `msw` from 2.10.3 to 2.10.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mswjs/msw/releases">msw's releases</a>.</em></p> <blockquote> <h2>v2.10.4 (2025-07-12)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>HttpHandler:</strong> use correct query parameters docs link (<a href="https://redirect.github.com/mswjs/msw/issues/2547">#2547</a>) (6cdce81de5576e5049899a729ab3a1424550c003) <a href="https://github.com/kettanaito"><code>@kettanaito</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mswjs/msw/commit/e4101030fe2efc10f7d2b5f95612bdb5c717902a"><code>e410103</code></a> chore(release): v2.10.4</li> <li><a href="https://github.com/mswjs/msw/commit/6cdce81de5576e5049899a729ab3a1424550c003"><code>6cdce81</code></a> fix(HttpHandler): use correct query parameters docs link (<a href="https://redirect.github.com/mswjs/msw/issues/2547">#2547</a>)</li> <li>See full diff in <a href="https://github.com/mswjs/msw/compare/v2.10.3...v2.10.4">compare view</a></li> </ul> </details> <br /> Updates `prettier-plugin-tailwindcss` from 0.6.13 to 0.6.14 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/releases">prettier-plugin-tailwindcss's releases</a>.</em></p> <blockquote> <h2>v0.6.14</h2> <ul> <li>Add support for OXC + Hermes Prettier plugins (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/376">#376</a>, <a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/380">#380</a>)</li> <li>Sort template literals in Angular expressions (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/377">#377</a>)</li> <li>Don't repeatedly add backslashes to escape sequences when formatting (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/381">#381</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/blob/main/CHANGELOG.md">prettier-plugin-tailwindcss's changelog</a>.</em></p> <blockquote> <h2>[0.6.14] - 2025-07-09</h2> <ul> <li>Add support for OXC + Hermes Prettier plugins (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/376">#376</a>, <a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/380">#380</a>)</li> <li>Sort template literals in Angular expressions (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/377">#377</a>)</li> <li>Don't repeatedly add backslashes to escape sequences when formatting (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/381">#381</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/commit/e4072ec25a26bba9e8beb858caebe8e641a85e54"><code>e4072ec</code></a> 0.6.14</li> <li><a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/commit/63d1f5c70543017354883b7821f0f41ba64ec18e"><code>63d1f5c</code></a> Don't repeatedly add backslashes to escape sequences when formatting (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/381">#381</a>)</li> <li><a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/commit/a265c5b795283bac043ea8a1163de749090b60bc"><code>a265c5b</code></a> Fix parsing TypeScript with OXC (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/380">#380</a>)</li> <li><a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/commit/8e4efba29aaadeb8dcf7c461afdba92857cfee53"><code>8e4efba</code></a> Test against Prettier v3.6 (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/375">#375</a>)</li> <li><a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/commit/afa39a56cc2fc6da37f4865338c5fb976c81232b"><code>afa39a5</code></a> Create FUNDING.yml</li> <li><a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/commit/9b87e4a50e53744ba02351775feb98cc3211aeac"><code>9b87e4a</code></a> Sort template literals in Angular expressions (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/377">#377</a>)</li> <li><a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/commit/3f06943f1e9e547733f9623f9915875060b0967f"><code>3f06943</code></a> Add support for OXC + Hermes plugins (<a href="https://redirect.github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/376">#376</a>)</li> <li>See full diff in <a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss/compare/v0.6.13...v0.6.14">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…icant-Gravitas#10347) Updates to the readme + docs to add info about the newly added auto setup script. Changes to ``new_blocks.md`` and ``installer.md`` are to make netlify CI happy and pass --------- Co-authored-by: Reinier van der Leer <pwuts@agpt.co>

) (Significant-Gravitas#10071)  The `GmailReadBlock._get_email_body()` method was only inspecting the top-level payload and a single `text/plain` part, causing it to return the fallback string "This email does not contain a text body." for most Gmail messages. This occurred because Gmail messages are typically wrapped in `multipart/alternative` or other multipart containers, which the original implementation couldn't handle. This critical issue made the Gmail integration unusable for reading email body content, as virtually every real Gmail message uses multipart MIME structures.  ### Changes #### Core Implementation: - **Replaced simple `_get_email_body()` with recursive multipart parser** that can walk through nested MIME structures - **Added `_walk_for_body()` method** for recursive traversal of email parts with depth limiting (max 10 levels) - **Implemented safe base64 decoding** with automatic padding correction in `_decode_base64()` - **Added attachment body support** via `_download_attachment_body()` for emails where body content is stored as attachments #### Email Format Support: - **HTML to text conversion** using `html2text` library for HTML-only emails - **Multipart/alternative handling** with preference for `text/plain` over `text/html` - **Nested multipart structure support** (e.g., `multipart/mixed` containing `multipart/alternative`) - **Single-part email support** (maintains backward compatibility) #### Dependencies & Testing: - **Added `html2text = "^2024.2.26"`** to `pyproject.toml` for HTML conversion - **Created comprehensive unit tests** in `test/blocks/test_gmail.py` covering all email types and edge cases - **Added error handling and graceful fallbacks** for malformed data and missing dependencies #### Security & Performance: - **Recursion depth limiting** prevents infinite loops on malformed email structures - **Exception handling** ensures graceful degradation when API calls fail - **Efficient tree traversal** with early returns for better performance ### Checklist #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: <details> <summary>Test Plan</summary> - **Single-part text/plain emails** - Verified correct extraction of plain text content - **Multipart/alternative emails** - Tested preference for plain text over HTML when both available - **HTML-only emails** - Confirmed HTML to text conversion works correctly - **Nested multipart structures** - Tested deeply nested `multipart/mixed` containing `multipart/alternative` - **Attachment-based body content** - Verified downloading and decoding of body stored as attachments - **Base64 padding edge cases** - Tested malformed base64 data with missing padding - **Recursion depth limits** - Confirmed protection against infinite recursion - **Error handling scenarios** - Tested graceful fallbacks for API failures and missing dependencies - **Backward compatibility** - Ensured existing functionality remains unchanged for edge cases - **Integration testing** - Ran standalone verification script with 100% test pass rate </details> #### For configuration changes: - [x] `.env.example` is updated or already compatible with my changes - [x] `docker-compose.yml` is updated or already compatible with my changes - [x] I have included a list of my configuration changes in the PR description (under **Changes**) <details> <summary>Configuration Changes</summary> - Added `html2text` dependency to `pyproject.toml` - no environment or infrastructure changes required - No changes to ports, services, secrets, or databases - Fully backward compatible with existing Gmail API configuration </details> --------- Co-authored-by: Toran Bruce Richards <toran.richards@gmail.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

…#10392) ## Changes 🏗️ <img width="800" height="265" alt="Screenshot 2025-07-16 at 13 10 57" src="https://github.com/user-attachments/assets/01164bde-0523-4284-bf74-d1a735b77d5c" /> When redoing the navigation bar, I moved the profile query to be executed on the server using the new [react-query](https://tanstack.com/query/latest) generated hooks. The README [states the new hooks can be called on the server](https://github.com/Significant-Gravitas/AutoGPT/blob/master/autogpt_platform/frontend/README.md#server-side-prefetching), but when looking deeply into the implementation of [`custom-mutator.ts`](https://github.com/Significant-Gravitas/AutoGPT/blob/master/autogpt_platform/frontend/src/app/api/mutators/custom-mutator.ts), it turns out they can not ( yet ) as `custom-mutator` calls the proxy API ( _which can't be called from a RSC_ 😅 ). ### Solution For now, I changed the call to be made through the old `BackendAPI`, which can be called client and server side ✅ ( _I did that as part of the server 🍪 migration_ ) and added an E2E test to catch this ever disappears again. Next, I will open a separate PR refactoring `custom-mutator` so that it can be called on the server. ## Checklist 📋 ### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Run the app - [x] Login - [x] You see your account name and email when opening the account menu

…d FileReadBlock (Significant-Gravitas#10393) This PR adds Excel file support to CSV processing and enhances text file reading capabilities. ### Changes 🏗️ **ReadSpreadsheetBlock (formerly ReadCsvBlock):** - Renamed `ReadCsvBlock` to `ReadSpreadsheetBlock` for better clarity - Added Excel file support (.xlsx, .xls) with automatic conversion to CSV using pandas - Enhanced parameter `file_in` to `file_input` for consistency - Excel files are automatically detected by extension and converted to CSV format - Maintains all existing CSV processing functionality (delimiters, headers, etc.) - Graceful error handling when pandas library is not available **FileReadBlock:** - Enhanced text file reading with advanced chunking capabilities - Added parameters: `skip_size`, `skip_rows`, `row_limit`, `size_limit`, `delimiter` - Supports both character-based and row-based processing - Chunked output for large files based on size limits - Proper file handling with UTF-8 and latin-1 encoding fallbacks - Uses `store_media_file` for secure file processing (URLs, data URIs, local paths) - Fixed test input to use data URI instead of non-existent file **General Improvements:** - Consistent parameter naming across blocks (`file_input`) - Enhanced error handling and validation - Comprehensive test coverage - All existing functionality preserved ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Both ReadSpreadsheetBlock and FileReadBlock instantiate correctly - [x] ReadSpreadsheetBlock processes CSV data with existing functionality - [x] FileReadBlock reads text files with data URI input - [x] All block tests pass (457 passed, 83 skipped) - [x] No linting errors in modified files - [x] Excel support gracefully handles missing pandas dependency #### For configuration changes: - [ ] `.env.example` is updated or already compatible with my changes - [ ] `docker-compose.yml` is updated or already compatible with my changes - [ ] I have included a list of my configuration changes in the PR description (under **Changes**) *Note: No configuration changes required for this PR.*

…e API configurations (Significant-Gravitas#10394) This update enhances the performance and user experience by allowing data to be prefetched, reducing loading times on the frontend. ### Changes - Introduced `usePrefetch` in Orval configuration to support prefetching. - Added prefetch queries for user profiles, admin listings history, notification preferences, and execution schedules. - Updated OpenAPI specifications to include descriptions for provider names and adjusted required fields in request models. - Enhanced the Navbar component to utilize the new prefetch functionality for user profile data. - Improved type definitions for various models to ensure better integration with the API. ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] I’ve checked everything manually, and everything is working fine.

…atform/backend (Significant-Gravitas#10378) [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pinecone&package-manager=pip&previous-version=5.4.2&new-version=7.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

…n /autogpt_platform/frontend (Significant-Gravitas#10379) [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@types/node&package-manager=npm_and_yarn&previous-version=22.15.30&new-version=24.0.13)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…tform/autogpt_libs in the development-dependencies group (Significant-Gravitas#10376) Bumps the development-dependencies group in /autogpt_platform/autogpt_libs with 1 update: [ruff](https://github.com/astral-sh/ruff). Updates `ruff` from 0.12.2 to 0.12.3 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/ruff/releases">ruff's releases</a>.</em></p> <blockquote> <h2>0.12.3</h2> <h2>Release Notes</h2> <h3>Preview features</h3> <ul> <li>[<code>flake8-bugbear</code>] Support non-context-manager calls in <code>B017</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/19063">#19063</a>)</li> <li>[<code>flake8-use-pathlib</code>] Add autofixes for <code>PTH100</code>, <code>PTH106</code>, <code>PTH107</code>, <code>PTH108</code>, <code>PTH110</code>, <code>PTH111</code>, <code>PTH112</code>, <code>PTH113</code>, <code>PTH114</code>, <code>PTH115</code>, <code>PTH117</code>, <code>PTH119</code>, <code>PTH120</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/19213">#19213</a>)</li> <li>[<code>flake8-use-pathlib</code>] Add autofixes for <code>PTH203</code>, <code>PTH204</code>, <code>PTH205</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/18922">#18922</a>)</li> </ul> <h3>Bug fixes</h3> <ul> <li>[<code>flake8-return</code>] Fix false-positive for variables used inside nested functions in <code>RET504</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/18433">#18433</a>)</li> <li>Treat form feed as valid whitespace before a line continuation (<a href="https://redirect.github.com/astral-sh/ruff/pull/19220">#19220</a>)</li> <li>[<code>flake8-type-checking</code>] Fix syntax error introduced by fix (<code>TC008</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19150">#19150</a>)</li> <li>[<code>pyupgrade</code>] Keyword arguments in <code>super</code> should suppress the <code>UP008</code> fix (<a href="https://redirect.github.com/astral-sh/ruff/pull/19131">#19131</a>)</li> </ul> <h3>Documentation</h3> <ul> <li>[<code>flake8-pyi</code>] Make example error out-of-the-box (<code>PYI007</code>, <code>PYI008</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19103">#19103</a>)</li> <li>[<code>flake8-simplify</code>] Make example error out-of-the-box (<code>SIM116</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19111">#19111</a>)</li> <li>[<code>flake8-type-checking</code>] Make example error out-of-the-box (<code>TC001</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19151">#19151</a>)</li> <li>[<code>flake8-use-pathlib</code>] Make example error out-of-the-box (<code>PTH210</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19189">#19189</a>)</li> <li>[<code>pycodestyle</code>] Make example error out-of-the-box (<code>E272</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19191">#19191</a>)</li> <li>[<code>pycodestyle</code>] Make example not raise unnecessary <code>SyntaxError</code> (<code>E114</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19190">#19190</a>)</li> <li>[<code>pydoclint</code>] Make example error out-of-the-box (<code>DOC501</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19218">#19218</a>)</li> <li>[<code>pylint</code>, <code>pyupgrade</code>] Fix syntax errors in examples (<code>PLW1501</code>, <code>UP028</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19127">#19127</a>)</li> <li>[<code>pylint</code>] Update <code>missing-maxsplit-arg</code> docs and error to suggest proper usage (<code>PLC0207</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/18949">#18949</a>)</li> <li>[<code>flake8-bandit</code>] Make example error out-of-the-box (<code>S412</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19241">#19241</a>)</li> </ul> <h2>Contributors</h2> <ul> <li><a href="https://github.com/AlexWaygood"><code>@AlexWaygood</code></a></li> <li><a href="https://github.com/BurntSushi"><code>@BurntSushi</code></a></li> <li><a href="https://github.com/Gankra"><code>@Gankra</code></a></li> <li><a href="https://github.com/InSyncWithFoo"><code>@InSyncWithFoo</code></a></li> <li><a href="https://github.com/LaBatata101"><code>@LaBatata101</code></a></li> <li><a href="https://github.com/MatthewMckee4"><code>@MatthewMckee4</code></a></li> <li><a href="https://github.com/MeGaGiGaGon"><code>@MeGaGiGaGon</code></a></li> <li><a href="https://github.com/MichaReiser"><code>@MichaReiser</code></a></li> <li><a href="https://github.com/NamelessGO"><code>@NamelessGO</code></a></li> <li><a href="https://github.com/UnboundVariable"><code>@UnboundVariable</code></a></li> <li><a href="https://github.com/abhijeetbodas2001"><code>@abhijeetbodas2001</code></a></li> <li><a href="https://github.com/carljm"><code>@carljm</code></a></li> <li><a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a></li> <li><a href="https://github.com/chirizxc"><code>@chirizxc</code></a></li> <li><a href="https://github.com/danparizher"><code>@danparizher</code></a></li> <li><a href="https://github.com/dhruvmanila"><code>@dhruvmanila</code></a></li> <li><a href="https://github.com/fdosani"><code>@fdosani</code></a></li> <li><a href="https://github.com/github-actions"><code>@github-actions</code></a></li> <li><a href="https://github.com/ibraheemdev"><code>@ibraheemdev</code></a></li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md">ruff's changelog</a>.</em></p> <blockquote> <h2>0.12.3</h2> <h3>Preview features</h3> <ul> <li>[<code>flake8-bugbear</code>] Support non-context-manager calls in <code>B017</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/19063">#19063</a>)</li> <li>[<code>flake8-use-pathlib</code>] Add autofixes for <code>PTH100</code>, <code>PTH106</code>, <code>PTH107</code>, <code>PTH108</code>, <code>PTH110</code>, <code>PTH111</code>, <code>PTH112</code>, <code>PTH113</code>, <code>PTH114</code>, <code>PTH115</code>, <code>PTH117</code>, <code>PTH119</code>, <code>PTH120</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/19213">#19213</a>)</li> <li>[<code>flake8-use-pathlib</code>] Add autofixes for <code>PTH203</code>, <code>PTH204</code>, <code>PTH205</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/18922">#18922</a>)</li> </ul> <h3>Bug fixes</h3> <ul> <li>[<code>flake8-return</code>] Fix false-positive for variables used inside nested functions in <code>RET504</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/18433">#18433</a>)</li> <li>Treat form feed as valid whitespace before a line continuation (<a href="https://redirect.github.com/astral-sh/ruff/pull/19220">#19220</a>)</li> <li>[<code>flake8-type-checking</code>] Fix syntax error introduced by fix (<code>TC008</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19150">#19150</a>)</li> <li>[<code>pyupgrade</code>] Keyword arguments in <code>super</code> should suppress the <code>UP008</code> fix (<a href="https://redirect.github.com/astral-sh/ruff/pull/19131">#19131</a>)</li> </ul> <h3>Documentation</h3> <ul> <li>[<code>flake8-pyi</code>] Make example error out-of-the-box (<code>PYI007</code>, <code>PYI008</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19103">#19103</a>)</li> <li>[<code>flake8-simplify</code>] Make example error out-of-the-box (<code>SIM116</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19111">#19111</a>)</li> <li>[<code>flake8-type-checking</code>] Make example error out-of-the-box (<code>TC001</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19151">#19151</a>)</li> <li>[<code>flake8-use-pathlib</code>] Make example error out-of-the-box (<code>PTH210</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19189">#19189</a>)</li> <li>[<code>pycodestyle</code>] Make example error out-of-the-box (<code>E272</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19191">#19191</a>)</li> <li>[<code>pycodestyle</code>] Make example not raise unnecessary <code>SyntaxError</code> (<code>E114</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19190">#19190</a>)</li> <li>[<code>pydoclint</code>] Make example error out-of-the-box (<code>DOC501</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19218">#19218</a>)</li> <li>[<code>pylint</code>, <code>pyupgrade</code>] Fix syntax errors in examples (<code>PLW1501</code>, <code>UP028</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19127">#19127</a>)</li> <li>[<code>pylint</code>] Update <code>missing-maxsplit-arg</code> docs and error to suggest proper usage (<code>PLC0207</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/18949">#18949</a>)</li> <li>[<code>flake8-bandit</code>] Make example error out-of-the-box (<code>S412</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/19241">#19241</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/ruff/commit/5bc81f26c8a820835067280153a279658477ccf2"><code>5bc81f2</code></a> Bump 0.12.3 (<a href="https://redirect.github.com/astral-sh/ruff/issues/19279">#19279</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/6908e2682f14792898cb8f9e4d920021da022307"><code>6908e26</code></a> Filter <code>ruff_linter::VERSION</code> out of SARIF output tests (<a href="https://redirect.github.com/astral-sh/ruff/issues/19280">#19280</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/25c429556421ddd6f715f5aaf906610e0c564606"><code>25c4295</code></a> [ty] Avoid stale diagnostics for open files diagnostic mode (<a href="https://redirect.github.com/astral-sh/ruff/issues/19273">#19273</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/426fa4bb12d8c47185800ba14dd5b4e721fd2c29"><code>426fa4b</code></a> [ty] Add signature help provider to playground (<a href="https://redirect.github.com/astral-sh/ruff/issues/19276">#19276</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/b0b65c24ff01dc9095f17b3768cf2b9a336a5a8c"><code>b0b65c2</code></a> [ty] Initial implementation of signature help provider (<a href="https://redirect.github.com/astral-sh/ruff/issues/19194">#19194</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/08bc6d25899501d690c37a87d6da51951280dfc5"><code>08bc6d2</code></a> Add simple integration tests for all output formats (<a href="https://redirect.github.com/astral-sh/ruff/issues/19265">#19265</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/f2ae12bab33d80d52caa3047775371fca83f6e96"><code>f2ae12b</code></a> [<code>flake8-return</code>] Fix false-positive for variables used inside nested functio...</li> <li><a href="https://github.com/astral-sh/ruff/commit/965f415212f4f9f3ef855b647d53e892e6913828"><code>965f415</code></a> [ty] Add a <code>--quiet</code> mode (<a href="https://redirect.github.com/astral-sh/ruff/issues/19233">#19233</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/83b5bbf004bf2e47dd4ca5c049930894856547f1"><code>83b5bbf</code></a> Treat form feed as valid whitespace before a line continuation (<a href="https://redirect.github.com/astral-sh/ruff/issues/19220">#19220</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/87f6f08ef53edc2cbe8632d612f6d4fd016fe2ff"><code>87f6f08</code></a> [ty] Make <code>check_file</code> a salsa query (<a href="https://redirect.github.com/astral-sh/ruff/issues/19255">#19255</a>)</li> <li>Additional commits viewable in <a href="https://github.com/astral-sh/ruff/compare/0.12.2...0.12.3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ruff&package-manager=pip&previous-version=0.12.2&new-version=0.12.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…autogpt_platform/backend with 2 updates (Significant-Gravitas#10373) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

…latform/frontend (Significant-Gravitas#10377) [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=dotenv&package-manager=npm_and_yarn&previous-version=16.5.0&new-version=17.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…t_platform/autogpt_libs (Significant-Gravitas#10175) Bumps [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) from 0.26.0 to 1.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-asyncio/releases">pytest-asyncio's releases</a>.</em></p> <blockquote> <h2>pytest-asyncio 1.0.0</h2> <h1><a href="https://github.com/pytest-dev/pytest-asyncio/tree/1.0.0">1.0.0</a> - 2025-05-26</h1> <h2>Removed</h2> <ul> <li>The deprecated <em>event_loop</em> fixture. (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/1106">#1106</a>)</li> </ul> <h2>Added</h2> <ul> <li>Prelimiary support for Python 3.14 (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/1025">#1025</a>)</li> </ul> <h2>Changed</h2> <ul> <li>Scoped event loops (e.g. module-scoped loops) are created once rather than per scope (e.g. per module). This reduces the number of fixtures and speeds up collection time, especially for large test suites. (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/1107">#1107</a>)</li> <li>The <em>loop_scope</em> argument to <code>pytest.mark.asyncio</code> no longer forces that a pytest Collector exists at the level of the specified scope. For example, a test function marked with <code>pytest.mark.asyncio(loop_scope="class")</code> no longer requires a class surrounding the test. This is consistent with the behavior of the <em>scope</em> argument to <code>pytest_asyncio.fixture</code>. (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/1112">#1112</a>)</li> </ul> <h2>Fixed</h2> <ul> <li>An error caused when using pytest's [--setup-plan]{.title-ref} option. (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/630">#630</a>)</li> <li>Unsuppressed import errors with pytest option <code>--doctest-ignore-import-errors</code> (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/797">#797</a>)</li> <li>A "fixture not found" error in connection with package-scoped loops (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/1052">#1052</a>)</li> </ul> <h2>Notes for Downstream Packagers</h2> <ul> <li>Removed a test that had an ordering dependency on other tests. (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/1114">#1114</a>)</li> </ul> <h2>pytest-asyncio 1.0.0a1</h2> <h1><a href="https://github.com/pytest-dev/pytest-asyncio/tree/1.0.0a1">1.0.0a1</a> - 2025-05-09</h1> <h2>Removed</h2> <ul> <li>The deprecated <em>event_loop</em> fixture. (<a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/1106">#1106</a>)</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/5ef97bd60a3b9363c837e07cf47f19d5240cdd82"><code>5ef97bd</code></a> chore: Prepare release of v1.0.0.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/f212e24ec5fd6d9b01936199c84e1676b6c7fcee"><code>f212e24</code></a> docs: Mention fix of <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/797">#797</a>.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/32c1d10e87d8ce31ca61a29c7d9bebfe5a413966"><code>32c1d10</code></a> test: Removed obsolete test for async_gen_fixtures.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/627ce9265ea06b8139cd3a60c34920912ff9351c"><code>627ce92</code></a> [pre-commit.ci] pre-commit autoupdate</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/a55ff36f2cd0e8ec4373e2adb729a4f431443b8d"><code>a55ff36</code></a> Build(deps): Bump pluggy from 1.5.0 to 1.6.0 in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/633389f3027ad4939d67099d51bef4d37dbf3ac0"><code>633389f</code></a> Build(deps): Bump hypothesis in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/0c99466a6c859cffc6474178e4cbd3575c0d3db8"><code>0c99466</code></a> docs: Fixed an error that reported a missing event_loop fixture when using pa...</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/0688d17581eb7396e5acfc14e8090d854f4e10aa"><code>0688d17</code></a> ci: Replace Github template expansion with env variable expansion.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/2adcf52664e3e3b804505ed5ee09da83cc173fb8"><code>2adcf52</code></a> ci: Quote Github variable expansion.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/dd0fac96cdf060c07dc8630185535e26c818c08c"><code>dd0fac9</code></a> ci: Fixed a bug that prevented release notes from being extracted from a Git ...</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-asyncio/compare/v0.26.0...v1.0.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest-asyncio&package-manager=pip&previous-version=0.26.0&new-version=1.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> > **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

…_platform/backend (Significant-Gravitas#10386) [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=faker&package-manager=pip&previous-version=33.3.1&new-version=37.4.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

…platform/backend (Significant-Gravitas#10384) [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=websockets&package-manager=pip&previous-version=14.2&new-version=15.0.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

…t-Gravitas#10388) ## Changes 🏗️ ### User creation tests Now, all tests use the users created via the platform signup in `global-setup.ts`. Their login details are on a `.auth/user-pool.json` file. I have the delete the logic that created tests users via Supabase directly. ### Build tests speed I have refactored the builder tests, so that, instead of adding 100s of blocks under a given test user session, a new test user logins and adds block for each letter: ``` Test user 1 - logins and adds blocks starting with "a" Test user 2 - logins and adds blocks starting with "b" ``` Given that we know the builder becomes slow once we have 30 or more blocks, in this way a test user never adds more than 10 blocks on a given test ( _without losing coverage_ ), so we don't need time-outs or artificially waiting due to the UI being slow. ### Readability test changes Refactor existing tests, using short-hand utilities, to be: - easier to write - clearer to read - easier to debug ```ts // Selectors getId("id") // --> page.getByTestId("id") getText("foo") // --> page.getByText("id") getButton("Run") // --> page.getByRole("button", {name: "Run"} ... // Assetions const btn = getButton("Save") isVisible(btn) // --> expect(btn).toBeVisible() ``` These utilities live under `selectors.ts` and `assertions.ts`. Their usage is optional but encouraged. ## Checklist 📋 ### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Refactored tests code looks good - [x] E2E tests are 🟢 on the CI ### For configuration changes: No config changes

## Changes 🏗️ <img width="1843" height="321" alt="Screenshot 2025-07-17 at 15 48 01" src="https://github.com/user-attachments/assets/63f528f7-1dc3-4587-a5af-d02b2c858191" /> In this recent PR Significant-Gravitas#10394 the navigation bar disappeared when logged out. A change was introduced where the navigation bar does not show up if we don't have profile data ( _which we won't have when logged out_ ). This solves it + adds tests covering the navigation bar in the logged out state. ## Checklist 📋 ### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Run this locally - [x] See the navbar appearing - [x] E2E tests pass on the CI ### For configuration changes: None

…ng (Significant-Gravitas#10368) ### Changes - Introduced a new script to generate test data for end-to-end (E2E) tests using API functions, ensuring compatibility with future model changes. - The script creates test users, agent blocks, graphs, profiles, library agents, presets, API keys, and store submissions. - Utilizes external services for image and video URLs, and includes error handling for data creation processes. - Provides a summary of created data upon completion, enhancing the testing framework for the AutoGPT platform. ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Test scripts are working perfectly and not breaking anything. Data is also correctly visible in the database.

…& Improve ReadSpreadsheetBlock performance (Significant-Gravitas#10395) ### Changes 🏗️ This PR introduces several key improvements to message handling, block functionality, and execution reliability: - **Renamed CSV block to Spreadsheet block** with enhanced CSV/Excel processing capabilities - **Added message size limiting and truncation** for Redis communication to prevent connection issues - **Optimized FileReadBlock** to yield content chunks instead of duplicated outputs for better performance - **Improved execution termination handling** with better timeout management and event publishing - **Enhanced continuous retry decorator** with async function support - **Implemented payload truncation** to prevent Redis connection issues from oversized messages ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Verified backend starts without errors - [x] Confirmed message truncation works for large payloads - [x] Tested spreadsheet block functionality with CSV and Excel files - [x] Validated execution termination improvements - [x] Checked FileReadBlock chunk processing #### For configuration changes: - [x] `.env.example` is updated or already compatible with my changes - [x] `docker-compose.yml` is updated or already compatible with my changes - [x] I have included a list of my configuration changes in the PR description (under **Changes**) 🤖 Generated with [Claude Code](https://claude.ai/code) --------- Co-authored-by: Claude <noreply@anthropic.com>

…in /autogpt_platform/backend (Significant-Gravitas#10375) [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=youtube-transcript-api&package-manager=pip&previous-version=0.6.3&new-version=1.1.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

This PR adds two new Gmail integration blocks—**Gmail Get Thread** and **Gmail Reply**—to the platform, enhancing threaded email workflows. Key changes include: - **GmailGetThreadBlock**: - New block that retrieves an entire Gmail thread by `threadId`, with an option to include or exclude messages from Spam and Trash. - Supports use cases like fetching all messages in a conversation to check for responses. - **GmailReplyBlock**: - New block that sends a reply within an existing Gmail thread, maintaining the thread context. - Accepts detailed input fields including recipients, CC, BCC, subject, body, and attachments. - Ensures replies are properly associated with their parent message and thread. - **Enhancements to existing Gmail blocks**: - The `Email` model and related outputs now include a `threadId` field. - Updated test data and mock data to support threaded operations. - Expanded OAuth scopes for actions requiring thread metadata. - **Documentation updates**: - Added documentation for the new Gmail blocks in both the general block listing and the detailed Gmail block docs. - Clarified that the `Email` output now includes the `threadId`. These updates enable more advanced and context-aware Gmail automations, such as fetching full conversations and replying inline, supporting richer communication workflows with Gmail. ## Checklist 📋 ### For code changes - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Try all the gmail blocks - [x] Send an email reply based on a thread from the get thread block --------- Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

…ificant-Gravitas#10718) ### Changes 🏗️ This PR implements email notifications for agent creators when their agent submissions are approved or rejected by an admin in the marketplace. Specifically, the changes include: - Added `AGENT_APPROVED` and `AGENT_REJECTED` notification types to `schema.prisma`. - Created `AgentApprovalData` and `AgentRejectionData` Pydantic models for notification data. - Configured the notification system to use immediate queues and new Jinja2 templates for these types. - Designed two new email templates: `agent_approved.html.jinja2` and `agent_rejected.html.jinja2`, with dynamic content for agent details, reviewer feedback, and relevant action links. - Modified the `review_store_submission` function to: - Include `User` and `Reviewer` data in the database query. - Construct and queue the appropriate email notification based on the approval/rejection status. - Ensure email sending failures do not block the agent review process. ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Approve an agent via the admin dashboard. - [x] Verify the agent creator receives an "Agent Approved" email with correct details and a link to the store. - [x] Reject an agent via the admin dashboard (providing a reason). - [x] Verify the agent creator receives an "Agent Rejected" email with correct details, the rejection reason, and a link to resubmit. - [x] Verify that if email sending fails (e.g., misconfigured SMTP), the agent approval/rejection process still completes successfully without error. <img width="664" height="975" alt="image" src="https://github.com/user-attachments/assets/d397f2dc-56eb-45ab-877e-b17f1fc234d1" /> <img width="664" height="975" alt="image" src="https://github.com/user-attachments/assets/25597752-f68c-46fe-8888-6c32f5dada01" /> --- Linear Issue: [SECRT-1168](https://linear.app/autogpt/issue/SECRT-1168) <a href="https://cursor.com/background-agent?bcId=bc-7394906c-0341-4bd0-8842-6d9d6f83c56c"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/open-in-cursor-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="https://cursor.com/open-in-cursor-light.svg"> <img alt="Open in Cursor" src="https://cursor.com/open-in-cursor.svg"> </picture> </a> <a href="https://cursor.com/agents?id=bc-7394906c-0341-4bd0-8842-6d9d6f83c56c"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/open-in-web-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="https://cursor.com/open-in-web-light.svg"> <img alt="Open in Web" src="https://cursor.com/open-in-web.svg"> </picture> </a> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>

…itas#10707) Co-authored-by: Swifty <craigswift13@gmail.com> resolve issue Significant-Gravitas#10692 where scheduled time and actual run

…ions (Significant-Gravitas#10656) Co-authored-by: SwiftyOS <craigswift13@gmail.com> Co-authored-by: Claude <claude@users.noreply.github.com> Co-authored-by: majdyz <zamil@agpt.co>

this fixes and makes the moderation message properly show the moderation ID ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan:  - [x] try trigger moderation and have it shows the moderation id in the error message

…gnificant-Gravitas#10533) Handle invalid or empty response from MusicGen model Fixes: Significant-Gravitas#9145 > ⚠️ Note: This PR does not directly fix issue Significant-Gravitas#9145 (failed run marked as success), but improves the validation of the URL to reduce the chances of invalid states entering the system. This is a related improvement, but not the root cause fix. ### Description During execution of the meta/musicgen model via Replicate API, the application failed with an error indicating the model returned an empty or invalid response. Although some API calls succeeded, this error showed the logic was not checking the structure and content of the result properly before processing it. PROBLEM: CONTEXT: API: Replicate MODEL: meta/musicgen:671ac645 STATUS: Failed after 3 attempts ERROR_MESSAGE: "Unexpected error: Model returned empty or invalid response" CAUSE: - The original logic did not validate result structure. - It assumed any non-null output was valid, including strings like "No output received". - This led to invalid/malformed results being passed to the frontend. ### Changes 🏗️ - Added `AIMusicGeneratorBlock` to support music generation using Meta’s MusicGen models via Replicate API. - Supports configurable inputs like prompt, model version, duration, temperature, top_k/p, and normalization. - Uses robust retry logic for reliability. - Output returns audio URL; errors return user-friendly message. BEFORE_CODE: | ``` if result and result != "No output received": yield "result", result return ``` AFTER_CODE: | ``` if result and isinstance(result, str) and result.startswith("http"): yield "result", result return ``` ### Checklist 📋 #### For code changes: - [x] Clearly listed changes in the PR description - [x] Added test plan and mock outputs - [x] Tested with various prompts and confirmed working output ### Test Plan - [x] Ran locally with valid Replicate API key - [x] Generated audio with different prompts - [x] Simulated failure to verify retry and error message --------- Co-authored-by: Abhimanyu Yadav <122007096+Abhi1992002@users.noreply.github.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

…eeded for their contexts (Significant-Gravitas#10717) The database manager had both sync and async clients that contained overlapping methods, including some that weren't actually used in their respective contexts. This violated the principle that each client should only expose the methods it needs. ## Problem The `DatabaseManagerClient` (sync) included `get_user_execution_summary_data`, but this method was only ever used in async contexts like the notifications system. This created unnecessary coupling and violated the design goal of having focused, context-specific clients. ## Solution After comprehensive analysis of actual method usage across the codebase: - **Removed** `get_user_execution_summary_data` from `DatabaseManagerClient` since it's only used in async contexts (notifications) - **Verified** all remaining methods on both clients are actively used in their respective contexts: - Sync client (11 methods): Used in monitoring and main execution thread - Async client (26 methods): Used in node execution, blocks, and notifications - **Maintained** the base `DatabaseManager` class with the union of all methods needed by either client ## Impact Each client now contains exactly the methods it needs for its specific usage patterns: - `DatabaseManagerClient` handles synchronous operations like monitoring and credit management - `DatabaseManagerAsyncClient` handles asynchronous operations like node execution, persistence, and notifications The change is minimal and surgical - only removing one unused method while preserving all actually-used functionality. Fixes Significant-Gravitas#10658.  --- ✨ Let Copilot coding agent [set things up for you](https://github.com/Significant-Gravitas/AutoGPT/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Swifty <craigswift13@gmail.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: ntindle <8845353+ntindle@users.noreply.github.com> Co-authored-by: Abhimanyu Yadav <122007096+Abhi1992002@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Reinier van der Leer <pwuts@agpt.co> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Nicholas Tindle <nicktindle@outlook.com> Co-authored-by: Bently <Github@bentlybro.com>

…ficant-Gravitas#10716) - Resolves Significant-Gravitas#10713 ### Changes 🏗️ - Remove early exit in API proxy that suppresses auth errors - Remove unused `proxy-action.ts` ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Publish Agent dialog works when logged out - [x] Publish Agent dialog works when logged in --------- Co-authored-by: Nicholas Tindle <nicholas.tindle@agpt.co>

Backend for the Blocks Menu Redesign. ### Changes 🏗️ - Add optional `agent_name` to the `AgentExecutorBlock` - displayed as the block name in the Builder - Include `output_schema` in the `LibraryAgent` model - Make `v2.store.db.py:get_store_agents` accept multiple creators filter - Add `api/builder` router with endpoints (and accompanying logic in `v2/builder/db` and models in `v2/builder/models`) - `/suggestions`: elements for the suggestions tab - `/categories`: categories with a number of blocks per each - `/blocks`: blocks based on category, type or provider - `/providers`: integration providers with their block counts - `/serach`: search blocks (including integrations), marketplace agents and user library agents - `/counts`: element counts for each category in the Blocks Menu. ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Modified function `get_store_agents` works in existing code paths - [x] Agent executor block works - [x] New endpoints work - [x] Existing Builder menu is unaffected --------- Co-authored-by: Abhimanyu Yadav <abhimanyu1992002@gmail.com> Co-authored-by: Abhimanyu Yadav <122007096+Abhi1992002@users.noreply.github.com>

…ges (Significant-Gravitas#10746) ### Changes 🏗️ This PR fixes an infinite loop issue in the execution manager where malformed or unparseable messages would be continuously requeued, causing high CPU usage and preventing the system from processing legitimate messages. **Key changes:** - Modified `_ack_message()` function to accept explicit `requeue` parameter - Set `requeue=False` for malformed/unparseable messages that cannot be fixed by retrying - Set `requeue=False` for duplicate execution attempts (graph already running) - Kept `requeue=True` for legitimate failures that may succeed on retry (e.g., temporary resource constraints, network issues) **Technical details:** The previous implementation always set `requeue=True` when rejecting messages with `basic_nack()`. This caused problematic messages to be immediately re-delivered to the consumer, creating an infinite loop for: 1. Messages with invalid JSON that cannot be parsed 2. Messages for executions that are already running (duplicates) These scenarios will never succeed regardless of how many times they're retried, so they should be rejected without requeueing to prevent resource exhaustion. ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Verified malformed messages are rejected without requeue - [x] Confirmed duplicate execution messages are rejected without requeue - [x] Ensured legitimate failures (shutdown, pool full) still requeue properly - [x] Tested that normal message processing continues to work correctly

…t-Gravitas#10750) - Fixes Significant-Gravitas#10749 ### Changes 🏗️ - Fix implementation of `useAgentRunsInfinite.upsertAgentRun(..)` ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] New runs appear in runs list

…ficant-Gravitas#10731) - resolves - Significant-Gravitas#10618 When we have a dropdown with a large description, the actions button is moved out of the dialog box. To fix this, I’ve added a temporary solution, but in the future, we need to change the entire layout. ### Checklist 📋 - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Everything works perfectly locally.

…ignificant-Gravitas#10737) ### Changes 🏗️ - Updated the creator page to utilize React Query for data fetching, improving performance and reliability. - Removed legacy API calls and integrated prefetching for creator details and agents. - Introduced a new MainCreatorPage component for better separation of concerns. - Added a hydration boundary for managing server state. ### Checklist 📋 ### Checklist 📋 - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] All marketplace E2E tests are working. - [x] I’ve tested all the links and checked if everything renders perfectly on the marketplace page.

…tas#10751) Added basic stagehand integration: <img width="667" height="609" alt="Screenshot 2025-08-27 at 09 20 18" src="https://github.com/user-attachments/assets/11ab2941-0913-4346-a1d4-45980711e0f9" /> [stagehand_v35.json](https://github.com/user-attachments/files/22002924/stagehand_v35.json) ### Changes 🏗️ - Act Block - Extract Block - Observe Block ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] I have added a sample agent - [x] I have created an agent that uses these blocks and ensured it runs

Adds support for Ideogram V3 model while maintaining backward compatibility with existing models (V1, V1_TURBO, V2, V2_TURBO). Updates default model to V3 and implements smart API routing to handle Ideogram's new V3 endpoint requirements. Changes Made - Added V3 model support: Added V_3 to IdeogramModelName enum and set as default - Dual API endpoint handling: - V3 models route to new /v1/ideogram-v3/generate endpoint with updated payload format - Legacy models (V1, V2, Turbo variants) continue using /generate endpoint - Model-specific feature filtering: - V1 models: Basic parameters only (no style_type or color_palette support) - V2/V2_TURBO: Full legacy feature support including style_type and color_palette - V3: New endpoint with aspect ratio mapping and updated parameter structure - Aspect ratio compatibility: Added mapping between internal enum values and V3's expected format (ASPECT_1_1 → 1x1) - Updated pricing: V3 model costs 18 credits (vs 16 for other models) - Updated default usage: Store image generation now uses V3 by default Technical Details Ideogram updated their API with a separate V3 endpoint that has different requirements: - Different URL path (/v1/ideogram-v3/generate) - Different aspect ratio format (e.g., 1x1 instead of ASPECT_1_1) - Model-specific feature support (V1 models don't support style_type, etc.) The implementation intelligently routes requests to the appropriate endpoint based on the selected model while maintaining a single unified interface. I tested all the models and they are working here <img width="1804" height="887" alt="image" src="https://github.com/user-attachments/assets/9f2e44ca-50a4-487f-987c-3230dd72fb5e" /> ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan:  - [x] Test the Ideogram model block and watch as they all work!

…10753)

Snyk has created this PR to upgrade @t3-oss/env-nextjs from 0.3.1 to 0.13.8. See this package in npm: @t3-oss/env-nextjs See this project in Snyk: https://app.snyk.io/org/tpsaint1966/project/52068c5f-4860-4e0f-9bd7-059ca3f532a3?utm_source=github&utm_medium=referral&page=upgrade-pr

snyk-io · 2025-09-09T17:45:30Z

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

github-actions · 2025-09-09T17:46:45Z

This PR targets the master branch but does not come from dev or a hotfix/* branch.

Automatically setting the base branch to dev.

openhands-ai · 2025-09-09T17:48:54Z

Looks like there are a few issues preventing this PR from being merged!

GitHub Actions are failing:
- Repo - PR Status Checker
- Classic - Agent smoke tests
- Classic - Python checks
- Classic - AGBenchmark CI

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #4 at branch `snyk-upgrade-6437a40cd37baf87404bfbddf97158f8`

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}

github-actions · 2025-09-21T22:10:50Z

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

majdyz and others added 30 commits July 14, 2025 09:01

fix(readme): Removes MIT icon from readme (Significant-Gravitas#10366)

3ca0d04

This PR simply removes the MIT Icon from the main README.md

Merge branch 'master' into dev

a07b0c7

ntindle and others added 17 commits August 25, 2025 14:24

feat(backend): Add user timezone support to backend (Significant-Grav…

2bb8e91

…itas#10707) Co-authored-by: Swifty <craigswift13@gmail.com> resolve issue Significant-Gravitas#10692 where scheduled time and actual run

feat(backend): implement low balance and insufficient funds notificat…

890bb3b

…ions (Significant-Gravitas#10656) Co-authored-by: SwiftyOS <craigswift13@gmail.com> Co-authored-by: Claude <claude@users.noreply.github.com> Co-authored-by: majdyz <zamil@agpt.co>

Merge master into dev to tidy up merge history (Significant-Gravitas#…

b713093

…10753)

Merge remote-tracking branch 'origin/dev'

82618ae

github-actions bot changed the base branch from master to dev September 9, 2025 17:46

github-actions bot added size/xl documentation Improvements or additions to documentation Classic Benchmark platform/frontend platform/backend platform/blocks labels Sep 9, 2025

tpsaint changed the base branch from dev to aarushikansal/remove-title-input-blocks September 9, 2025 20:45

github-actions bot added the conflicts label Sep 21, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Snyk] Upgrade @t3-oss/env-nextjs from 0.3.1 to 0.13.8#4

[Snyk] Upgrade @t3-oss/env-nextjs from 0.3.1 to 0.13.8#4
tpsaint wants to merge 967 commits intoaarushikansal/remove-title-input-blocksfrom
snyk-upgrade-6437a40cd37baf87404bfbddf97158f8

tpsaint commented Sep 9, 2025

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Uh oh!

snyk-io bot commented Sep 9, 2025

Uh oh!

github-actions bot commented Sep 9, 2025

Uh oh!

openhands-ai bot commented Sep 9, 2025

Uh oh!

github-actions bot commented Sep 21, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

19 participants

Conversation

tpsaint commented Sep 9, 2025

Snyk has created this PR to upgrade @t3-oss/env-nextjs from 0.3.1 to 0.13.8.

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Uh oh!

snyk-io bot commented Sep 9, 2025

🎉 Snyk checks have passed. No issues have been found so far.

Uh oh!

github-actions bot commented Sep 9, 2025

Uh oh!

openhands-ai bot commented Sep 9, 2025

Uh oh!

github-actions bot commented Sep 21, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

19 participants