[pull] main from e2b-dev:main #132
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Bumps the npm_and_yarn group with 1 update in the / directory: [next](https://github.com/vercel/next.js). Bumps the npm_and_yarn group with 1 update in the /apps/web directory: [next](https://github.com/vercel/next.js). Updates `next` from 14.2.21 to 14.2.25 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.21...v14.2.25) Updates `next` from 14.2.21 to 14.2.25 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.21...v14.2.25) --- updated-dependencies: - dependency-name: next dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: next dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
When iterating on templates, our team often wanted to sanity check when a template was modified. So we end up opening the network log and reading the `templates` object resp manually. If you've gotten this feedback from other users, here's a PR to show `updatedAt` as a column.
Bumps the npm_and_yarn group with 1 update in the / directory: [next](https://github.com/vercel/next.js). Bumps the npm_and_yarn group with 1 update in the /apps/web directory: [next](https://github.com/vercel/next.js). Updates `next` from 14.2.21 to 14.2.25 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v14.2.25</h2> <blockquote> <p>[!NOTE]<br /> This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary. This release contains a security patch for <a href="https://github.com/vercel/next.js/security/advisories/GHSA-f82v-jwr5-mffw">CVE-2025-29927</a>.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>Update middleware request header (<a href="https://redirect.github.com/vercel/next.js/issues/77202">#77202</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/ijjk"><code>@ijjk</code></a> for helping!</p> <h2>v14.2.24</h2> <blockquote> <p>[!NOTE]<br /> This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>fix: ensure lint worker errors aren't silenced (<a href="https://redirect.github.com/vercel/next.js/issues/75779">#75779</a>)</li> <li>add additional x-middleware-set-cookie filtering (<a href="https://redirect.github.com/vercel/next.js/issues/75561">#75561</a> & <a href="https://redirect.github.com/vercel/next.js/issues/73482">#73482</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/ztanner"><code>@ztanner</code></a> for helping!</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/d36a1f3c3547b0cb807f30c14aa6250a932349c8"><code>d36a1f3</code></a> v14.2.25</li> <li><a href="https://github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48"><code>5fd3ae8</code></a> [backport] Update middleware request header (<a href="https://redirect.github.com/vercel/next.js/issues/77202">#77202</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/756be15c4cfecb6fae1c69cae7cfaf336423b6cf"><code>756be15</code></a> v14.2.24</li> <li><a href="https://github.com/vercel/next.js/commit/ba6453d5efbb1dcb282c39d372b48d60de59fa2c"><code>ba6453d</code></a> fix corepack keys</li> <li><a href="https://github.com/vercel/next.js/commit/c482c2072f6eb3f7bd656bc05e100ed54dce3636"><code>c482c20</code></a> [backport v14] fix: ensure lint worker errors aren't silenced (<a href="https://redirect.github.com/vercel/next.js/issues/75766">#75766</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/75779">#75779</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/5791cb677808df1cea625057d6aff95fbf5cd3a0"><code>5791cb6</code></a> [Backport v14] add additional x-middleware-set-cookie filtering (<a href="https://redirect.github.com/vercel/next.js/issues/75561">#75561</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/75">#75</a>...</li> <li><a href="https://github.com/vercel/next.js/commit/8129a6188096c23c68d4151256acbe6d86d2eed3"><code>8129a61</code></a> test: fix eslint plugin test (<a href="https://redirect.github.com/vercel/next.js/issues/75687">#75687</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/f27ce02b6785a1c7c8f88daf1d2112b5a2e1f34a"><code>f27ce02</code></a> v14.2.23</li> <li><a href="https://github.com/vercel/next.js/commit/c4bf4acfbf727a2393c2b98bad1c5d7243c2a63e"><code>c4bf4ac</code></a> backport: force module format for virtual client-proxy (<a href="https://redirect.github.com/vercel/next.js/issues/74162">#74162</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/74590">#74590</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/d60bb1b5fb902dac79b11d9c78761022b88f6f03"><code>d60bb1b</code></a> Backport: Use provided waitUntil for pending revalidates (<a href="https://redirect.github.com/vercel/next.js/issues/74164">#74164</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/74573">#74573</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v14.2.21...v14.2.25">compare view</a></li> </ul> </details> <br /> Updates `next` from 14.2.21 to 14.2.25 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v14.2.25</h2> <blockquote> <p>[!NOTE]<br /> This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary. This release contains a security patch for <a href="https://github.com/vercel/next.js/security/advisories/GHSA-f82v-jwr5-mffw">CVE-2025-29927</a>.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>Update middleware request header (<a href="https://redirect.github.com/vercel/next.js/issues/77202">#77202</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/ijjk"><code>@ijjk</code></a> for helping!</p> <h2>v14.2.24</h2> <blockquote> <p>[!NOTE]<br /> This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>fix: ensure lint worker errors aren't silenced (<a href="https://redirect.github.com/vercel/next.js/issues/75779">#75779</a>)</li> <li>add additional x-middleware-set-cookie filtering (<a href="https://redirect.github.com/vercel/next.js/issues/75561">#75561</a> & <a href="https://redirect.github.com/vercel/next.js/issues/73482">#73482</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/ztanner"><code>@ztanner</code></a> for helping!</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/d36a1f3c3547b0cb807f30c14aa6250a932349c8"><code>d36a1f3</code></a> v14.2.25</li> <li><a href="https://github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48"><code>5fd3ae8</code></a> [backport] Update middleware request header (<a href="https://redirect.github.com/vercel/next.js/issues/77202">#77202</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/756be15c4cfecb6fae1c69cae7cfaf336423b6cf"><code>756be15</code></a> v14.2.24</li> <li><a href="https://github.com/vercel/next.js/commit/ba6453d5efbb1dcb282c39d372b48d60de59fa2c"><code>ba6453d</code></a> fix corepack keys</li> <li><a href="https://github.com/vercel/next.js/commit/c482c2072f6eb3f7bd656bc05e100ed54dce3636"><code>c482c20</code></a> [backport v14] fix: ensure lint worker errors aren't silenced (<a href="https://redirect.github.com/vercel/next.js/issues/75766">#75766</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/75779">#75779</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/5791cb677808df1cea625057d6aff95fbf5cd3a0"><code>5791cb6</code></a> [Backport v14] add additional x-middleware-set-cookie filtering (<a href="https://redirect.github.com/vercel/next.js/issues/75561">#75561</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/75">#75</a>...</li> <li><a href="https://github.com/vercel/next.js/commit/8129a6188096c23c68d4151256acbe6d86d2eed3"><code>8129a61</code></a> test: fix eslint plugin test (<a href="https://redirect.github.com/vercel/next.js/issues/75687">#75687</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/f27ce02b6785a1c7c8f88daf1d2112b5a2e1f34a"><code>f27ce02</code></a> v14.2.23</li> <li><a href="https://github.com/vercel/next.js/commit/c4bf4acfbf727a2393c2b98bad1c5d7243c2a63e"><code>c4bf4ac</code></a> backport: force module format for virtual client-proxy (<a href="https://redirect.github.com/vercel/next.js/issues/74162">#74162</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/74590">#74590</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/d60bb1b5fb902dac79b11d9c78761022b88f6f03"><code>d60bb1b</code></a> Backport: Use provided waitUntil for pending revalidates (<a href="https://redirect.github.com/vercel/next.js/issues/74164">#74164</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/74573">#74573</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v14.2.21...v14.2.25">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 You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/e2b-dev/E2B/network/alerts). </details>
Inspired by original change in code-interpreter release process e2b-dev/code-interpreter#72
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )