Dependency Dashboard

Aberta
#10 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
15/100
Tipo de issue
Refatoração
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
docker, github-actions, rust
Domínio
build-system, devops

Direção de pesquisa

This is an automated Renovate dashboard, not a scoped change request. Review the listed dependency updates in Cargo.toml, .github/workflows/ci.yml, .github/workflows/publish.yml, and Dockerfile; the tokio security update already has a pull request at ../pull/9. There is no defined completion criterion for a newcomer to pick up here.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository Problems

Renovate tried to run on this repository, but found these problems.

  • ⚠️ WARN: Some release(s) did not have a releaseTimestamp, but as we're running with minimumReleaseAgeBehaviour=timestamp-optional, proceeding. See debug logs for more information
  • ⚠️ WARN: Some upgrade(s) did not have a releaseTimestamp, but as we're running with minimumReleaseAgeBehaviour=timestamp-optional, proceeding. See debug logs for more information

Awaiting Schedule

The following updates are awaiting their schedule. To get an update now, click on a checkbox below.

  • chore(deps): lock file maintenance
  • fix(deps): update rust crate fastembed to v7
  • fix(deps): update rust crate hf-hub to v1
  • 🔐 Create all awaiting schedule PRs at once 🔐

Open

The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.

Vulnerabilities

Renovate has not found any CVEs on osv.dev.

Detected Dependencies

cargo (1)
Cargo.toml (14)
  • axum 0.8.7
  • fastembed 5.15.0 → [Updates: 7.0.0]
  • futures 0.3.32
  • hf-hub 0.5.0 → [Updates: 1.0.0]
  • ort =2.0.0-rc.13 → [Updates: =2.0.0-rc.15]
  • serde 1.0.219
  • serde_json 1.0.145
  • sysinfo 0.39.2 → [Updates: 0.40.0]
  • tokenizers 0.22.2 → [Updates: 0.23.0]
  • tokio 1.52.3
  • tracing 0.1.44
  • tracing-subscriber 0.3.20
  • ureq 3.3.0
  • tikv-jemallocator 0.6 → [Updates: 0.7]
dockerfile (1)
Dockerfile (3)
  • docker/dockerfile 1.7@sha256:a57df69d0ea827fb7266491f2813635de6f17269be881f696fbfdf2d83dda33e → [Updates: 1.28]
  • rust 1.95-slim-trixie@sha256:e14e87345b4d5964ddcc3491d27ee046a0f23820f340c3c1e24da6880141f7c0 → [Updates: 1.100-slim-trixie]
  • debian trixie-slim@sha256:a72b4433de1cf7d6bae0c4cee74d0547f58601a643b3375f070c51600d63b6b2
github-actions (3)
.github/workflows/ci.yml (6)
  • actions/checkout v6.0.2@de0fac2e4500dabe0009e67214ff5f5447ce83dd → [Updates: v6.1.0, v7.0.1]
  • dtolnay/rust-toolchain stable@39008827e6b4319a349e9a42dfc90579dd25f1ca
  • Swatinem/rust-cache v2.9.1@c19371144df3bb44fab255c43d04cbc2ab54d1c4 → [Updates: v2.9.3]
  • actions/checkout v6.0.2@de0fac2e4500dabe0009e67214ff5f5447ce83dd → [Updates: v6.1.0, v7.0.1]
  • docker/setup-buildx-action v4.1.0@d7f5e7f509e45cec5c76c4d5afdd7de93d0b3df5 → [Updates: v4.4.1]
  • docker/build-push-action v7.2.0@f9f3042f7e2789586610d6e8b85c8f03e5195baf → [Updates: v7.4.0]
.github/workflows/memory-bench.yml (5)
  • actions/checkout v6.0.2@de0fac2e4500dabe0009e67214ff5f5447ce83dd → [Updates: v6.1.0, v7.0.1]
  • actions/checkout v6.0.2@de0fac2e4500dabe0009e67214ff5f5447ce83dd → [Updates: v6.1.0, v7.0.1]
  • dtolnay/rust-toolchain stable@39008827e6b4319a349e9a42dfc90579dd25f1ca
  • Swatinem/rust-cache v2.9.1@c19371144df3bb44fab255c43d04cbc2ab54d1c4 → [Updates: v2.9.3]
  • actions/cache v6.1.0@55cc8345863c7cc4c66a329aec7e433d2d1c52a9
.github/workflows/publish.yml (6)
  • actions/checkout v6.0.2@de0fac2e4500dabe0009e67214ff5f5447ce83dd → [Updates: v6.1.0, v7.0.1]
  • docker/setup-qemu-action v4.0.0@ce360397dd3f832beb865e1373c09c0e9f86d70a → [Updates: v4.4.0]
  • docker/setup-buildx-action v4.1.0@d7f5e7f509e45cec5c76c4d5afdd7de93d0b3df5 → [Updates: v4.4.1]
  • docker/login-action v4.2.0@650006c6eb7dba73a995cc03b0b2d7f5ca915bee → [Updates: v4.8.0]
  • docker/metadata-action v6.1.0@80c7e94dd9b9319bd5eb7a0e0fe9291e23a2a2e9 → [Updates: v6.2.0]
  • docker/build-push-action v7.2.0@f9f3042f7e2789586610d6e8b85c8f03e5195baf → [Updates: v7.4.0]
Linguagem predominante
Rust
Estrelas
0
Forks
3
Merge médio
10h 33min
PRs com merge (30d)
4

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de appwrite/embedding

Todas as issues de appwrite/embedding

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.