Skip to content

chore(pgvector-embedded): rebuild prebuilt artifacts (v0.8.1)#981

Closed
github-actions[bot] wants to merge 2 commits into
mainfrom
chore/pgvector-embedded-v0.8.1-26184696799
Closed

chore(pgvector-embedded): rebuild prebuilt artifacts (v0.8.1)#981
github-actions[bot] wants to merge 2 commits into
mainfrom
chore/pgvector-embedded-v0.8.1-26184696799

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 20, 2026

Regenerated by the build-pgvector-embedded workflow (pgvector v0.8.1, PG 18).

Summary by CodeRabbit

Release v9.0.0

  • Breaking Changes

    • Local test database engine switched from PGlite to embedded PostgreSQL; existing test data directories will not be migrated automatically.
  • New Features

    • Enhanced CLI, server, authentication, gateway, and local testing capabilities.
  • Bug Fixes

    • Multiple fixes across CLI, server, authentication, gateway, and testing components.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: df4beb2f-d1ee-411c-8314-06aa0d035f95

📥 Commits

Reviewing files that changed from the base of the PR and between ac2ddbd and 8770978.

⛔ Files ignored due to path filters (4)
  • packages/pgvector-embedded/prebuilt/darwin-arm64/vector.dylib is excluded by !**/*.dylib
  • packages/pgvector-embedded/prebuilt/darwin-x64/vector.dylib is excluded by !**/*.dylib
  • packages/pgvector-embedded/prebuilt/linux-arm64/vector.so is excluded by !**/*.so
  • packages/pgvector-embedded/prebuilt/linux-x64/vector.so is excluded by !**/*.so
📒 Files selected for processing (14)
  • .release-please-manifest.json
  • CHANGELOG.md
  • charts/lobu/Chart.yaml
  • package.json
  • packages/agent-worker/package.json
  • packages/cli/package.json
  • packages/connector-sdk/package.json
  • packages/connector-worker/package.json
  • packages/connectors/package.json
  • packages/core/package.json
  • packages/embeddings/package.json
  • packages/openclaw-plugin/package.json
  • packages/pgvector-embedded/package.json
  • packages/promptfoo-provider/package.json

📝 Walkthrough

Walkthrough

This PR performs a monorepo-wide version bump from 8.0.0 to 9.0.0, updating the release manifest, root workspace, Helm chart, and all package manifests. The changelog entry documents a breaking change: the local lobu run/test database engine switched from PGlite to an embedded PostgreSQL instance without migration of existing data.

Changes

Version 9.0.0 Release

Layer / File(s) Summary
Changelog entry for 9.0.0 release
CHANGELOG.md
New release section documents the breaking change that the local database engine switched from PGlite to embedded PostgreSQL (no automatic migration of existing ~/.lobu data), along with enumerated features and bug fixes across CLI, server, auth, gateway, and related areas.
Version number updates across manifests and packages
.release-please-manifest.json, package.json, charts/lobu/Chart.yaml, packages/agent-worker/package.json, packages/cli/package.json, packages/connector-sdk/package.json, packages/connector-worker/package.json, packages/connectors/package.json, packages/core/package.json, packages/embeddings/package.json, packages/openclaw-plugin/package.json, packages/pgvector-embedded/package.json, packages/promptfoo-provider/package.json
Version field is incremented from 8.0.0 to 9.0.0 across the release-please manifest, root workspace, Helm chart metadata (version and appVersion), and all monorepo package manifests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

  • lobu-ai/lobu#863: Prior release version bump updating the same release-management files for a different release number.
  • lobu-ai/lobu#897: Related release-please version bump modifying release/config/versioned files across the same manifest and package structure.
  • lobu-ai/lobu#724: Earlier Release Please version bump updating the same release/version metadata fields across manifest, package.json, and chart files.

Suggested labels

autorelease: tagged

Poem

🐰 From eight to nine, we leap ahead,
PGlite fades, PostgreSQL's bed,
Versions unified, manifests bright,
A release complete, everything right!

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title describes rebuilding pgvector-embedded prebuilt artifacts, but the changeset predominantly contains version bumps to 9.0.0 across all packages and changelog updates, not pgvector-embedded rebuild artifacts. Update the title to accurately reflect the main change: something like 'chore: release version 9.0.0' or 'chore(release): bump version to 9.0.0 with changelog updates'.
Description check ⚠️ Warning The description is minimal and does not follow the provided template structure, which requires Summary, Test plan, and Notes sections with specific validation checkboxes. Add a proper Summary section explaining the 9.0.0 release and breaking changes, complete the Test plan checklist, and include any relevant notes or linked issues.
✅ Passed checks (3 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/pgvector-embedded-v0.8.1-26184696799

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

@buremba
Copy link
Copy Markdown
Member

buremba commented May 20, 2026

Closing as duplicate. The build-pgvector-embedded workflow opened 6 PRs for the same v0.8.1 rebuild; the build is non-deterministic so these only churn binary artifacts with no functional change. Several also carry already-merged work (#973, #978) or the release-please 9.0.0 commit (#939). main's existing prebuilt artifacts are kept.

@buremba buremba closed this May 20, 2026
@buremba buremba deleted the chore/pgvector-embedded-v0.8.1-26184696799 branch May 20, 2026 19:39
buremba added a commit that referenced this pull request May 25, 2026
…1051)

The push trigger used a bare paths filter, which GitHub ignores for
freshly-created refs (it can't diff them). So every release-please tag
(lobu-vX.Y.Z) ran the rebuild and, because the binaries aren't
byte-reproducible, opened a no-op 'rebuild artifacts' PR each release
(#972, #974, #975, #977, #979, #980, #981, #996, #1002, #1005, #1025,
#1029).

Scope the push trigger to branches: [main] so tag refs no longer match,
and drop the workflow file from paths (only build.sh changes the
artifacts). workflow_dispatch still covers deliberate pgvector/PG bumps.
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