9732573b6a
add: new_user hubspot contact creation
2025-04-03 11:40:51 +02:00
f9198474fa
Add development shell to manage dependencies ( #657 )
2025-04-02 14:56:10 -07:00
32664ea0fe
[skip ci] Release new versions
2025-04-01 20:36:48 +00:00
2db98557ba
Show SDK ref dir only when it exists ( #655 )
...
# Description
To avoid errors like https://github.com/e2b-dev/E2B/actions/runs/14200197836/job/39785152642
where we publish without any sdk ref changes.
2025-04-01 22:34:00 +02:00
2535fc22c7
make show sdk ref dir when exsits
2025-04-01 10:17:46 -07:00
d65de1bbe8
Update Ubuntu base image to 22.04 ( #653 )
...
# Description
There is a scheduled Ubuntu 20.04 brownout. Ubuntu 20.04 LTS runner will
be removed on 2025-04-15. For more details, see
https://github.com/actions/runner-images/issues/11101
2025-04-01 08:50:51 -07:00
c3ecd7c684
Remove backslashes from the docker build command (Windows) ( #652 )
...
- Fixing #650 , on Windows commands cannot separate arguments by
backslash (\).
2025-04-01 16:32:56 +01:00
130773ea7f
Refactor: Convert legacy application to docs-only mode ( #599 )
...
This PR transforms our legacy Next.js application to serve only
documentation content by:
- Removing dashboard components and pages
- Stripping authentication requirements
- Maintaining documentation routes and content
- Preparing for proxy integration with new dashboard
### Technical changes
- Removed auth-required wrappers from documentation pages
- Eliminated dashboard-specific components and routes
- Removed unused dependencies related to dashboard functionality
- Updated application configs & sitemap.xml to support being proxied by
new dashboard app
### Testing
- Verified all documentation pages render correctly without auth
- Confirmed navigation works as expected
- Tested proxy integration with new dashboard application
### Next steps
1. Once merged, the new dashboard will proxy to this application for
documentation content
2. In the future, we'll migrate documentation to the new system
completely
2025-04-01 16:34:29 +02:00
213bcdd351
remove: all sitemap paths for legacy docs
2025-04-01 16:20:18 +02:00
0d2c6d31b3
chore: refresh lockfile
2025-04-01 13:47:15 +02:00
07a510ba4e
revert: accidental pnpm-lock.yaml deletion
2025-04-01 13:44:27 +02:00
62e28caa82
remove: overdone merged sitemap refactor parts
2025-04-01 13:44:27 +02:00
ddfee82401
remove redirects from vercel.json
2025-04-01 13:44:27 +02:00
34625e6e6b
update sitemap.xml
2025-04-01 13:44:27 +02:00
279dcc77c9
remove posthog /ingest rewrites
2025-04-01 13:44:27 +02:00
f5f5a0b6ad
remove all auth / dashboard related parts & update sitemap to not include dashboard
2025-04-01 13:43:49 +02:00
8e1bd9a94c
Update package versions ( #648 )
...
## Description
Update the python beta SDK version to latest
2025-03-31 07:06:21 -07:00
73b27fad47
Update Python beta SDK version ( #647 )
...
# Description
Update the python beta SDK version to latest
2025-03-31 14:25:41 +02:00
cfa58614ae
Update python beta SDK version
2025-03-31 14:17:17 +02:00
e7321d5b12
[skip ci] Release new versions
2025-03-28 20:38:03 +00:00
e8fab568da
build-arg's not working for e2b template build command ( #644 )
...
At the moment if you pass in build args it breaks since the commands
aren't compatible with the docker build command:
Sample error at the moment when passing the --build-arg to e2b which
proxies the command on incorrectly:
```
(base) ➜ web git:(lb) ✗ npm run build-template template-name version
> new-nextjs-app@0.1.0 build-template
> ts-node scripts/build-template.ts template-name template-version sha
ERROR: "docker buildx build" requires exactly 1 argument.
See 'docker buildx build --help'.
Usage: docker buildx build [OPTIONS] PATH | URL | -
Start a build
/bin/sh: line 4: --build-arg=TEMPLATE_VERSION=0.0.1: command not found
Error: Command failed: docker build . \
-f e2b.Dockerfile \
--pull --platform linux/amd64 \
-t docker.e2b.dev/e2b/custom-envs/17e92ok9u0gimh3oy1qg:be0bdf11-4cf2-4ee0-a932-1ecb6ae50298 --build-arg="TEMPLATE_NAME=lead-magnet" \
--build-arg="TEMPLATE_VERSION=0.0.1"
at genericNodeError (node:internal/errors:983:15)
at wrappedFn (node:internal/errors:537:14)
at checkExecSyncError (node:child_process:889:11)
at Object.execSync (node:child_process:961:15)
at e.<anonymous> (/opt/homebrew/lib/node_modules/@e2b/cli/src/commands/template/build.ts:363:23) {
status: 127,
signal: null,
output: [ null, null, null ],
pid: 67925,
stdout: null,
stderr: null
}
Failed to build template: Error: Command failed: e2b template build -d "../../sandbox/templates/e2b.Dockerfile" -n template-name sha1 --build-arg TEMPLATE_NAME=template-name --build-arg TEMPLATE_VERSION=0.0.1 -p "../sandbox/templates/"
ERROR: "docker buildx build" requires exactly 1 argument.
See 'docker buildx build --help'.
Usage: docker buildx build [OPTIONS] PATH | URL | -
```
---------
Co-authored-by: Mish <10400064+mishushakov@users.noreply.github.com >
2025-03-28 21:34:50 +01:00
ebfade86d5
Fixes "sandbox id" naming consistency (uppercase) ( #643 )
2025-03-28 11:04:01 +01:00
7638231277
fix "sandbox id" naming consistency (uppercase)
2025-03-28 11:02:16 +01:00
9f7957d0fb
Script for per-package check if release is needed ( #641 )
...
Inspired by original change in code-interpreter release process
https://github.com/e2b-dev/code-interpreter/pull/72
2025-03-27 07:13:11 -07:00
d032d5a80b
Bump the npm_and_yarn group across 2 directories with 1 update ( #627 )
...
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>
2025-03-27 13:34:19 +01:00
d799ae9210
Merge branch 'main' into dependabot/npm_and_yarn/npm_and_yarn-954d90908d
2025-03-27 13:20:38 +01:00
bda91a9767
Add table column to show template updatedAt field ( #622 )
...
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.
2025-03-27 11:55:23 +01:00
63dd3afe29
Merge branch 'main' into add-updated-at-to-templates-list
2025-03-27 10:40:57 +01:00
5ca2b9cc42
[skip ci] Release new versions
2025-03-26 18:15:28 +00:00
c865121307
Allow python SDKs to write any instance of IOBase files ( #640 )
...
- [x] update `write` method in sync & async python SDKs to allow
`io.BufferedReader` files
- [x] update tests
2025-03-26 19:11:35 +01:00
5a208ebb6b
add changeset
2025-03-26 10:49:10 -07:00
bd4398f30d
address PR comments
2025-03-25 15:53:42 -07:00
6dd18e2832
allow writing files that are of type io.BufferedReader and update tests
2025-03-25 14:39:58 -07:00
184f33c269
[skip ci] Release new versions
2025-03-25 15:23:47 +00:00
39a880a9ac
Cli changeset for version release ( #639 )
...
Related to changes in https://github.com/e2b-dev/E2B/pull/636
2025-03-25 16:21:33 +01:00
7d4f7b0e0b
getInfo: added tests, updated documentation with example return ( #638 )
...
Unborked version of #637
2025-03-25 09:40:11 +01:00
197d966ad0
Update cli to latest sdk version ( #636 )
2025-03-24 17:25:51 +01:00
c0efd6f322
added additional test coverage for getInfo, updated doc
2025-03-24 16:59:37 +01:00
5701eead65
Bump the npm_and_yarn group across 2 directories with 1 update
...
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](https://github.com/vercel/next.js/compare/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](https://github.com/vercel/next.js/compare/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 >
2025-03-24 15:11:31 +00:00
1e9502fe0c
chore(apps/web): update package.json ( #633 )
...
1. move `@types/node` to `devDependencies`
2. move `@types/react-highlight-words` to `devDependencies`
3. remove unused package `swr`
4. remove unused package `unique-names-generator`
5. remove unused package `uuid`
2025-03-24 07:58:59 -07:00
8f47d4d6a3
doc: fix typo of file apps/web/README.md ( #630 )
2025-03-24 07:17:59 -07:00
8fdb429998
[skip ci] Release new versions
2025-03-24 13:33:20 +00:00
d4f4352aa3
Add getInfo/get_info methods to the SDKs ( #625 )
...
- Rebased version of #517
2025-03-24 14:26:18 +01:00
5d8b719b21
[skip ci] Release new versions
2025-03-24 11:45:11 +00:00
85c4505b9f
Change default domain in sdks from e2b.dev to e2b.app ( #635 )
2025-03-24 12:40:22 +01:00
c4129d879d
Fix Webflow proxying with www-prefixed hostname and proper request handling ( #634 )
...
This PR resolves the Cloudflare IP blocking issue by:
1. Adding www prefix to landing page hostname
2. Properly handling request headers with new Headers object
3. Adding redirect handling to follow redirects
4. Refactoring middleware response handling for proper URL rewriting
These changes prevent Cloudflare from identifying our requests as
suspicious automated traffic while maintaining the functionality of our
proxy middleware.
2025-03-23 12:32:44 +01:00
5ee371498a
fix: clean up middleware rewrite fetch + use next native rewrite response + prefix landing page hostname with www
...
Simplify fetch
Remove headers
Add rest of headers
Explicitly define fetch options
Remove header manipulation
Test all custom config
Remove out cache header
Remove no cache in header
Remove cache
Tweak fetch options
Remove credentials
Remove referrer
Return to basic setup
Add redirect handling
Stop caching
Remove redirect
Remove no cache
Return old settings
Proxy everything
Modify hostname
Change domain
Change hostname back
Remove caching
Change rewrite mechanism
Add more headers
Remove the rewrite
Follow redirect
Try www
Add log
Try just rewrite
Only pass get requests
Fix error
Change headers passing
Print headers
Test pure rewrite
Remove unused code
Add html replace for ai agents list
Remove logs
2025-03-23 12:20:31 +01:00
deb47a2f48
Merge branch 'main' into add-updated-at-to-templates-list
2025-03-22 10:31:06 -07:00
4453b26477
Updated preview logo in readme ( #628 )
2025-03-22 11:45:26 +01:00
f076a61448
updated preview logo
2025-03-22 11:21:55 +01:00
Ben Fornefeld