Skip to content

chore(release): promote main → release (22 commits)#4936

Merged
M3gA-Mind merged 22 commits into
releasefrom
main
Jul 15, 2026
Merged

chore(release): promote main → release (22 commits)#4936
M3gA-Mind merged 22 commits into
releasefrom
main

Conversation

@M3gA-Mind

Copy link
Copy Markdown
Collaborator

Promote the current main into release22 commits ahead, no divergence (clean fast-forwardable merge, release carries nothing not already in main).

Cutting staging/prod builds from release after this picks up the accumulated fixes/features below.

Notable changes since the last release cut

Notes

  • Release and main are both at app version 0.61.5; this brings the post-0.61.5 fix/feature work onto release.
  • No merge conflicts (release is strictly behind main).
  • Standard promotion is also available via the promote-main-to-release.yml workflow dispatch; opening this as a PR for review visibility per request.

graycyrus and others added 22 commits July 15, 2026 12:41
…are sandbox, unified draft handles, reference gates (#4881)
… AA (#4897)

Co-authored-by: Steven Enamakel <enamakel@tinyhumans.ai>
Co-authored-by: Steven Enamakel <enamakel@tinyhumans.ai>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-advanced-security

Copy link
Copy Markdown
Contributor

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cb5d33b8-c812-4684-96b6-1a72a0813816

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@M3gA-Mind M3gA-Mind merged commit abffbe6 into release Jul 15, 2026
48 of 49 checks passed

@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: 4be17632f0

ℹ️ 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".

Comment on lines +551 to +552
setDraftGraph(proposedGraph);
setPreview(null);

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 Preserve the preview until Accept actually saves

If handleSave fails here (core/network error or validation race), the copilot panel intentionally keeps the proposal card visible for retry, but these lines have already overwritten draftGraph and cleared the preview base. In that failure state, clicking Reject only calls setPreview(null) and no longer restores the pre-proposal graph/title, so the user can reject the still-visible proposal while the canvas remains changed and later save changes they thought they discarded.

Useful? React with 👍 / 👎.

// `canvasVersion` bump above) so the ref's imperative handle is stale;
// call `handleSave` directly with the known-good proposed graph.
try {
await handleSave(proposedGraph, overrideName, proposal.requireApproval);

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 Keep outbound approval forced on accepted updates

When accepting a proposal onto an existing flow, this forwards proposal.requireApproval directly to flows_update; if the proposal JSON explicitly has require_approval: false and the graph contains outbound tool_call/http_request/code nodes, the update path honors that flag instead of applying the create-time side-effect floor, so Accept can silently turn off the human approval gate for a live workflow. This is limited to existing-flow Accepts because new draft creation goes through flows_create, which forces approval for outbound graphs.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants