Skip to content

Deploy: staging → main - #186

Open
rapiercraft-forgedock[bot] wants to merge 102 commits into
mainfrom
staging
Open

Deploy: staging → main#186
rapiercraft-forgedock[bot] wants to merge 102 commits into
mainfrom
staging

Conversation

@rapiercraft-forgedock

Copy link
Copy Markdown

Summary

Promote the current staging branch to main.

This release includes the accumulated ForgeDock Next runtime, orchestration, promotion, observability, TUI, GitHub/SQLite adapter, verification, documentation, and workflow updates from staging.

Review notes

  • GitHub comparison: 43 commits ahead of main, 13 commits behind.
  • This PR is based on the remote staging branch.
  • Local verification was not run before opening; use the required CI/build checks for validation.

ItsMrDubey and others added 30 commits August 5, 2026 10:28
Publish the complete detached staging worktree snapshot, including bounded provider retry safeguards and existing staged changes.
…-4654-9b09-45cddc1a98c2

[E2E fresh disposable] Add one lifecycle proof document
…-43b7-bcdc-b921e0d5d08e

fix: Vendor-only Pi/runtime changes are omitted from publish trigger and changed-path guard (staging review — PR #137)
function send(response: ServerResponse, status: number, payload: Record<string, unknown>): void {
if (response.writableEnded) return;
response.writeHead(status, { "content-type": "application/json" });
response.end(JSON.stringify(payload));
rapiercraft-forgedock Bot and others added 2 commits August 17, 2026 04:50
…-4c71-8da3-19dea51986e7

fix: Verification content sealing permits symlinks escaping the workspace (review finding — PR #186)
…-41a6-995b-9ace9f9f01ab

fix: npm-only recovery suppresses a needed GitHub Packages retry (review finding — PR #186)
…-41c9-8605-6d3ca125fe21

fix: Sandbox write validation is vulnerable to a symlink TOCTOU race (review finding — PR #186)
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.

2 participants