Skip to content

chore(main): release 0.2.0 #530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
e2b-generated-code-auto-fixer wants to merge 1 commit into from
Closed

chore(main): release 0.2.0 #530

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .release-please-manifest.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
".": "0.1.0"
".": "0.2.0"

@claude claude Bot Sep 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Bumping the manifest to 0.2.0 breaks tests/unit/release-config.test.ts, which hardcodes expect(manifest['.']).toBe('0.1.0') at line 28. That assertion passed on the base branch (manifest was 0.1.0) and now fails on main after every release-please bump, breaking CI/unit tests for maintainers on unrelated PRs. Fix: the test must not hardcode a version string that release-please is expected to change; assert a stable invariant instead (e.g. manifest['.'] === pkg.version and a semver-format check), so future automated bumps keep passing.

Extended reasoning...

tests/unit/release-config.test.ts:24-30 reads .release-please-manifest.json and package.json and asserts manifest['.'] === '0.1.0' literally, then asserts pkg.version === manifest['.']. Before this diff both files were 0.1.0, so the test passed. This diff (a release-please automated bump) changes .release-please-manifest.json to 0.2.0 and package.json's version to 0.2.0 too, but does not touch the test file (it is not among the 3 changed files). After merge, expect(manifest['.']).toBe('0.1.0') fails because manifest['.'] is now '0.2.0', even though pkg.version and manifest still agree with each other. Any CI run of the unit test suite on main (or any branch based on main) after this merge fails on this assertion until a human manually edits the test, defeating the purpose of an automated release-please bump PR.

Verification: normal. tests/unit/release-config.test.ts:28 asserts expect(manifest['.']).toBe('0.1.0'). On the base commit (f7b85de) .release-please-manifest.json had ".": "0.1.0", so this assertion passed. This diff changes the manifest to ".": "0.2.0" (HEAD manifest confirmed) but does not touch the test file (only 3 files change: .release-please-manifest.json, CHANGELOG.md,… | normal.…

}
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Changelog

## [0.2.0](https://github.com/e2b-dev/dashboard/compare/v0.1.0...v0.2.0) (2026-09-16)


### Features

* **container:** self-hostable container image with runtime configuration ([#528](https://github.com/e2b-dev/dashboard/issues/528)) ([f7b85de](https://github.com/e2b-dev/dashboard/commit/f7b85dee10b98c0e2196d631759174b2249a7e85))
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@e2b/dashboard",
"version": "0.1.0",
"version": "0.2.0",
"private": true,
"scripts": {
"<<<<<<< Next.js": "",
Expand Down
Loading