Skip to content

chore(release): promote reviewed develop to data - #3815

Merged
twoimo merged 71 commits into
datafrom
develop
Nov 12, 2026
Merged

twoimo merged 71 commits into
datafrom
develop

Conversation

@twoimo

@twoimo twoimo commented Nov 12, 2026

Copy link
Copy Markdown
Owner

Why

Promote the reviewed develop source through the existing protected develop → data → main path. PR #3814 reconciled the historical promotion ancestry while preserving the already-tested runtime/test/config bytes.

Exact inputs

  • Head develop: 31f3fd7e92b48079850b2482549bf6c35d14083a
  • Base data: 20fd13c9ff4026eff82f87a62983e258d91a4300
  • Candidate tree: f6853410d1b49deca57de9310281dfa470ba5bf3
  • The exact comparison is ahead with no data-only commits remaining and 113 changed files. No data-branch work is overwritten.

Included reviewed work

Verification and merge conditions

  • Read back the current protected main/data/develop refs and the actual default branch main.
  • Both data and main retain PR-required, strict up-to-date, conversation-resolution, no-bypass protection; force pushes and deletions remain disabled.
  • PR docs(ci): record rollout and reconcile protected promotion ancestry #3814 passed CI, Security, Release, Promotion Path, and CodeQL at its exact head. Its documentation-only web workflow ran scope/result jobs successfully; measurements are recorded in that PR.
  • This protected promotion must run the full applicable CI, Security, Release, Promotion Path, CodeQL and process-boundary checks. Verify the exact final head/base and completed results before a normal merge.
  • Read back the resulting data commit and tree after merge.

Operational boundary

This PR promotes source to data. Source Vercel settings exclude data builds, and the actual GitHub default remains main. No hosted database writes, producer activation, branch retirement, or Mac service change is performed here.

Actual production/main promotion remains dependent on verifying the intended Vercel project, current serving deployment, and a fresh eligible rollback target. The current connector cannot establish those identities; a GitHub deployment success record alone is insufficient.

dependabot Bot and others added 30 commits November 12, 2026 04:44
Bumps [@google/genai](https://github.com/googleapis/js-genai) from 2.32.0 to 3.0.0.
- [Release notes](https://github.com/googleapis/js-genai/releases)
- [Changelog](https://github.com/googleapis/js-genai/blob/main/CHANGELOG.md)
- [Commits](googleapis/js-genai@v2.32.0...v3.0.0)

---
updated-dependencies:
- dependency-name: "@google/genai"
  dependency-version: 3.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [dotenv](https://github.com/motdotla/dotenv) from 18.0.9 to 18.0.10.
- [Changelog](https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md)
- [Commits](motdotla/dotenv@v18.0.9...v18.0.10)

---
updated-dependencies:
- dependency-name: dotenv
  dependency-version: 18.0.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps the opentelemetry group in /backend/pipeline-control with 3 updates: [opentelemetry-api](https://github.com/open-telemetry/opentelemetry-python), [opentelemetry-sdk](https://github.com/open-telemetry/opentelemetry-python) and [opentelemetry-exporter-otlp-proto-http](https://github.com/open-telemetry/opentelemetry-python).


Updates `opentelemetry-api` from 1.45.1 to 1.45.2
- [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-python@v1.45.1...v1.45.2)

Updates `opentelemetry-sdk` from 1.45.1 to 1.45.2
- [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-python@v1.45.1...v1.45.2)

Updates `opentelemetry-exporter-otlp-proto-http` from 1.45.1 to 1.45.2
- [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-python@v1.45.1...v1.45.2)

---
updated-dependencies:
- dependency-name: opentelemetry-api
  dependency-version: 1.45.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: opentelemetry
- dependency-name: opentelemetry-sdk
  dependency-version: 1.45.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: opentelemetry
- dependency-name: opentelemetry-exporter-otlp-proto-http
  dependency-version: 1.45.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: opentelemetry
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [supabase](https://github.com/supabase/supabase-py) from 2.33.0 to 2.34.1.
- [Release notes](https://github.com/supabase/supabase-py/releases)
- [Changelog](https://github.com/supabase/supabase-py/blob/v2.34.1/CHANGELOG.md)
- [Commits](supabase/supabase-py@v2.33.0...v2.34.1)

---
updated-dependencies:
- dependency-name: supabase
  dependency-version: 2.34.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [kafka-python](https://github.com/dpkp/kafka-python) from 3.0.11 to 3.0.13.
- [Release notes](https://github.com/dpkp/kafka-python/releases)
- [Changelog](https://github.com/dpkp/kafka-python/blob/master/docs/changelog.rst)
- [Commits](dpkp/kafka-python@3.0.11...3.0.13)

---
updated-dependencies:
- dependency-name: kafka-python
  dependency-version: 3.0.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [langchain-openai](https://github.com/langchain-ai/langchain) from 1.7.3 to 1.7.4.
- [Release notes](https://github.com/langchain-ai/langchain/releases)
- [Commits](langchain-ai/langchain@langchain-openai==1.7.3...langchain-openai==1.7.4)

---
updated-dependencies:
- dependency-name: langchain-openai
  dependency-version: 1.7.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [Azure/setup-helm](https://github.com/azure/setup-helm) from 5.0.1 to 5.1.0.
- [Release notes](https://github.com/azure/setup-helm/releases)
- [Changelog](https://github.com/Azure/setup-helm/blob/main/CHANGELOG.md)
- [Commits](Azure/setup-helm@9bc31f4...2f5e7bc)

---
updated-dependencies:
- dependency-name: Azure/setup-helm
  dependency-version: 5.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…seline

local-stack.py start now restores the committed baseline once the application
database is ready. A database that already matches is left alone, so a later
start does not wipe local rows. LOCAL_STACK_REPLAY_STACK=1 skips the restore,
so the nightly replay lane still applies the historical chain.

Verified: ensure_present skips, reuses, and provisions; the core start calls the
hook after the database is ready; the replay selector never queries the database
for a baseline.
feat(supabase): provision the application stack from the committed baseline
PG17 start was recreating auth, storage and realtime from a privilege-less
dump, so those services never became ready. Leave the image-owned schemas
in place, restore project objects after the services migrate, and record
the hosted object gap.
fix(supabase): restore project objects without dropping platform schemas
…t-crawling/scripts/develop/langchain-openai-1.7.4

chore(deps): bump langchain-openai from 1.7.3 to 1.7.4 in /backend/restaurant-crawling/scripts
Regenerate the existing reconciliation manifest for the Kafka client and Helm action updates already merged into develop. Preserve source provenance, dispositions, tests, gates, and the immutable Supabase migration.
perf(db): remove redundant Supabase indexes with catalog guards
…control/develop/opentelemetry-fb2c5e4a73

chore(deps): bump the opentelemetry group in /backend/pipeline-control with 3 updates
…develop/dotenv-18.0.10

chore(deps): bump dotenv from 18.0.9 to 18.0.10 in /backend
…develop/google/genai-3.0.0

chore(deps): bump @google/genai from 2.32.0 to 3.0.0 in /backend
perf(ci): scope PR checks and require complete results
perf(pipeline): run local services on demand with reliable delivery
…0261113

perf(pipeline): decouple daily compute from optional data publication
chore(release): retire bypassing sync helper and prepare staged promotion
docs(ci): record rollout and reconcile protected promotion ancestry
@vercel

vercel Bot commented Nov 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
tzudong Ignored Ignored Nov 12, 2026 5:14pm UTC

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
tzudong-ci-governance 31f3fd7 Nov 12 2026, 05:16 PM

@twoimo
twoimo merged commit 8af98ee into data Nov 12, 2026
58 checks passed
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.

1 participant