chore(pgvector-embedded): rebuild prebuilt artifacts (v0.8.1)#980
chore(pgvector-embedded): rebuild prebuilt artifacts (v0.8.1)#980github-actions[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (4)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
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. |
…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.
Regenerated by the build-pgvector-embedded workflow (pgvector v0.8.1, PG 18).