Skip to content

build(deps-dev): Bump certifi from 2026.6.17 to 2026.7.22 in /services/account_unification #20

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.

Sign up for GitHub

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

Merged
seonghobae merged 2 commits into from
Aug 3, 2026
Merged

build(deps-dev): Bump certifi from 2026.6.17 to 2026.7.22 in /services/account_unification #20

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6775b50
build(deps-dev): Bump certifi in /services/account_unification
dependabot[bot] Aug 3, 2026
a9c70d2
Merge branch 'main' into dependabot/pip/services/account_unification/…
opencode-agent[bot] Aug 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions services/account_unification/requirements-dev.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ attrs==26.1.0 \
--hash=sha256:c647aa4a12dfbad9333ca4e71fe62ddc36f4e63b2d260a37a8b83d2f043ac309 \
--hash=sha256:d03ceb89cb322a8fd706d4fb91940737b6642aa36998fe130a9bc96c985eff32
# via interrogate
certifi==2026.6.17 \
--hash=sha256:024c88eeec92ca068db80f02b8b07c9cef7b9fe261d1d535abfd5abd6f6af432 \
--hash=sha256:2227dcbaafe0d2f59279d1762ddddc37783ed4354594f194ffc31d20f41fc3db
certifi==2026.7.22 \
--hash=sha256:62f22742b58a1a33014a2b6b706588a8d7e2a88ae7bd1a6ebe8c992928483775 \
--hash=sha256:741e2c3b351ddf169a738da9f2c048608ff7f2c5cc02f1ebc6b118bb090d5d55
Comment on lines +21 to +23

@coderabbitai coderabbitai Bot Aug 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- tracked lockfiles ---'
git ls-files '*requirements-dev.txt' '*requirements.lock' '*uv.lock' | sort

printf '%s\n' '--- certifi entries ---'
for f in services/account_unification/requirements-dev.txt \
         services/account_unification/requirements.lock \
         services/account_unification/uv.lock; do
  if [ -f "$f" ]; then
    printf '\n[%s]\n' "$f"
    rg -n -C 3 'certifi|2026\.7\.22|2026\.6\.17|62f22742|741e2c3b' "$f" || true
  fi
done

printf '%s\n' '--- uv configuration and usage references ---'
rg -n -C 2 'uv\.lock|uv sync|--locked|requirements-dev\.txt|requirements\.lock' \
  services/account_unification .github Makefile pyproject.toml 2>/dev/null || true

Repository: ContextualWisdomLab/keyverse

Length of output: 8179

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- project configuration ---'
if [ -f services/account_unification/pyproject.toml ]; then
  cat -n services/account_unification/pyproject.toml
fi

printf '%s\n' '--- uv.lock metadata and certifi dependency contexts ---'
cat -n services/account_unification/uv.lock | sed -n '1,75p'
rg -n -C 5 'certifi|requires-dist|resolution-markers|content|revision|name = "account|name = "account-unification' \
  services/account_unification/uv.lock

printf '%s\n' '--- repository change summary ---'
git diff --stat -- services/account_unification/requirements-dev.txt \
  services/account_unification/requirements.lock \
  services/account_unification/uv.lock
git diff --numstat -- services/account_unification/requirements-dev.txt \
  services/account_unification/requirements.lock \
  services/account_unification/uv.lock

Repository: ContextualWisdomLab/keyverse

Length of output: 10048

🌐 Web query:

uv sync --locked behavior lockfile out of date project requirements

💡 Result:

When you use the --locked flag with uv sync, uv strictly requires that the project's lockfile (uv.lock) is both present and fully up-to-date with the current project requirements (e.g., pyproject.toml) [1][2][3]. If the lockfile is missing, or if the dependencies defined in your project configuration have diverged from the locked versions, uv will exit with an error rather than attempting to update the lockfile [1][3][4]. Key aspects of this behavior include: 1. Enforcement of Reproducibility: The --locked flag is primarily used in continuous integration (CI) or automated build environments to ensure that the installed environment exactly matches the committed lockfile [4]. It prevents the tool from silently resolving dependencies or updating the lockfile during the build process [2][4]. 2. Error Handling: If uv detects that the lockfile is stale (i.e., a change was made to pyproject.toml without subsequently running uv lock), it will explicitly output an error message instructing you to run uv lock to regenerate the lockfile [1][5][4]. 3. --locked vs. --frozen: - --locked: Asserts that the lockfile is up-to-date. If it is not, the command fails [2][3]. - --frozen: Skips checking the lockfile against project requirements entirely. It treats the existing uv.lock as the absolute source of truth and will not update it, but it will not error out if the lockfile is out of sync with pyproject.toml [2][3][6]. If you encounter an unexpected "lockfile needs to be updated" error while using --locked, it often indicates either true drift in dependencies or, occasionally, issues with workspace configuration or tool version mismatches [7][5][8]. In such cases, verifying that you are using the same version of uv locally and in your environment, and ensuring that all workspace dependencies are correctly accounted for, is recommended [7][5].

Citations:

uv.lock을 certifi==2026.7.22로 갱신하세요.

uv.lock은 certifi 2026.6.17과 이전 해시를 고정합니다. CI와 Dockerfile은 uv sync --locked를 사용하므로 이전 버전이 설치됩니다. 세 잠금 파일의 버전과 해시를 일치시키세요.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@services/account_unification/requirements-dev.txt` around lines 21 - 23,
certifi 의존성 항목을 기준으로 uv.lock의 버전을 2026.7.22로 갱신하고 새 버전에 해당하는 해시를 반영하세요. 세 잠금 파일의
certifi 버전과 해시가 모두 일치하도록 기존 2026.6.17 값과 이전 해시를 제거하세요.

# via
# httpcore
# httpx
Expand Down
Loading