Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency tensorchord/pgvecto.rs to v0.2.1 #16

Merged
merged 1 commit into from
Mar 5, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 4, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
tensorchord/pgvecto.rs patch v0.2.0 -> v0.2.1

Release Notes

tensorchord/pgvecto.rs (tensorchord/pgvecto.rs)

v0.2.1

Compare Source

Improvements

  • NULL Support: NULL can now be safely inserted into vector columns without error. They will be skipped during pgvecto.rs index creation, but exist in the table. A query on a vector column will never return a result containing a NULL.
  • Signal Handler Fix: Now we use SIGQUIT instead of SIGHUP to trigger a peaceful exit, since SIGHUP is defined as configure reload by Postgres.
  • Upgrade Script Refine: Due to some symbol renaming, the upgrade path from v0.1.10 to v0.2.0 is broken. Users can now upgrade directly to v0.2.1 if they are currently using v0.1.10.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@bo0tzz
Copy link
Member

bo0tzz commented Mar 4, 2024

@gaocegege @cutecutecat this build is failing with

#12 [linux/amd64 2/4] ADD https://github.com/tensorchord/pgvecto.rs/releases/download/v0.2.1/vectors-pg14_0.2.1_amd64.deb ./pgvectors.deb
#12 ERROR: invalid response status 404

This is because the artifacts on the pgvecto.rs release are named with 0.2.1-1 - did something go wrong there, or should this build be adapted to support that scheme?

@bo0tzz bo0tzz merged commit 7352582 into main Mar 5, 2024
6 checks passed
@renovate renovate bot deleted the renovate/tensorchord-pgvecto.rs-0.x branch March 5, 2024 10:03
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