Skip to content

chore(main): release orchestrator 0.0.1 #3470

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

Merged
charlie-e2b merged 2 commits into from
Jul 30, 2026
+142 −1
Merged

chore(main): release orchestrator 0.0.1 #3470

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
45ece62
chore(main): release orchestrator 0.0.1
e2b-release-please[bot] Jul 30, 2026
25d72ac
Merge branch 'main' into release-please--branches--main--components--…
charlie-e2b Jul 30, 2026
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
3 changes: 2 additions & 1 deletion .release-please-manifest.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,9 @@
"packages/docker-reverse-proxy": "0.0.1",
"packages/client-proxy": "0.0.1",
"packages/clickhouse": "0.0.1",
"packages/envd": "0.0.1",

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 30, 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.

P2 Badge Remove duplicate envd manifest version

The new packages/envd entry leaves this release manifest with two different envd versions (0.0.1 here and 0.6.13 below). The release workflow treats .release-please-manifest.json as the source of package versions before tagging, so the envd release state is now parser-dependent or can be rejected by tooling that checks for duplicate JSON keys, which can break or mis-version the next envd release. Please remove this added envd line and keep the existing 0.6.13 entry.

Useful? React with 👍 / 👎.

"packages/orchestrator": "0.0.1",
"packages/envd": "0.6.13",
"packages/orchestrator": "0.0.0",
"packages/api": "0.0.1",
"packages/dashboard-api": "0.0.0",
"packages/nomad-nodepool-apm": "0.0.1"
Expand Down
Loading