Skip to content

chore(main): release orchestrator 0.1.0 - #3506

Closed
e2b-release-please[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--orchestrator
Closed

e2b-release-please[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--orchestrator

Conversation

@e2b-release-please

@e2b-release-please e2b-release-please Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.1.0 (2026-08-05)

Features

  • data-exporter: add export pipeline metrics (#1324) (9a6c71d)

Bug Fixes

  • orchestrator: abort the NBD release backoff on context cancellation (#3495) (f6378f5)
  • orch: smoketest never ran on belt — envd locator predates the restructure (#1386) (dec8a79)
  • oss: upload with gcloud storage instead of gsutil (#1302) (416a1b2)

This PR was generated with Release Please. See documentation.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM — automated release-please version bump for orchestrator 0.0.2 → 0.0.3, no code changes.

Extended reasoning...

Overview

This is an automated release-please PR that only touches .release-please-manifest.json (version bump) and packages/orchestrator/CHANGELOG.md (changelog entry for the already-merged and reviewed fix in #3495). No source code is changed.

Security risks

None. No logic, config, or infrastructure code is modified — just version metadata and a changelog entry.

Level of scrutiny

Minimal scrutiny is appropriate. This is a mechanical, bot-generated release PR following an established pattern (release-please), and the underlying fix it packages was already reviewed and merged separately in PR #3495.

Other factors

The diff is fully mechanical and matches the release-please convention used elsewhere in this repo's history (e.g. the prior 0.0.1→0.0.2 release PR). No outstanding review comments exist on this PR.

@e2b-release-please
e2b-release-please Bot force-pushed the release-please--branches--main--components--orchestrator branch from 7797293 to 065b1d7 Compare August 3, 2026 06:57
@jakubno
jakubno requested a review from ben-fornefeld as a code owner August 3, 2026 13:31
@jakubno
jakubno force-pushed the release-please--branches--main--components--orchestrator branch from 065b1d7 to 30c92b6 Compare August 3, 2026 13:33
@e2b-release-please e2b-release-please Bot changed the title chore(main): release orchestrator 0.0.3 chore(main): release orchestrator 0.1.0 Aug 3, 2026
@e2b-release-please
e2b-release-please Bot force-pushed the release-please--branches--main--components--orchestrator branch from 30c92b6 to 5176347 Compare August 3, 2026 13:33

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5176347a6d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

"packages/clickhouse": "0.1.0",
"packages/envd": "0.6.13",
"packages/orchestrator": "0.0.2",
"packages/orchestrator": "0.1.0",

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 Cut this release as a patch version

The manifest drives the release tag created by .github/workflows/release-please.yml:138-144, so merging this publishes orchestrator-v0.1.0. The previous orchestrator release in the repo is e92b3f6 (0.0.2), and git log e92b3f6..2acf2d5 -- packages/orchestrator shows only one fix(orchestrator) commit plus a ci docs change, with no feat or breaking orchestrator change to justify a minor bump. Cutting this as 0.1.0 locks the wrong version into the immutable publish flow; this release should stay patch-level, with the changelog limited to the post-0.0.2 fix.

Useful? React with 👍 / 👎.

@e2b-release-please
e2b-release-please Bot force-pushed the release-please--branches--main--components--orchestrator branch from 5176347 to 957f5e3 Compare August 5, 2026 12:24
@e2b-release-please
e2b-release-please Bot force-pushed the release-please--branches--main--components--orchestrator branch 2 times, most recently from 5d9ee11 to 7ab32c4 Compare August 5, 2026 12:24
@jakubno jakubno closed this Aug 6, 2026
@jakubno
jakubno deleted the release-please--branches--main--components--orchestrator branch August 14, 2026 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant