TencentBlueKing / TencentBlueKing/bkpaas-python-sdk

blue-krill 3.1.0 锁了 django-environ 的版本

Open
#296 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
34
Forks
34
Avg merge
18m
Merged PRs (30d)
1

Description

The 3.14 lock now resolves. It also forced one related downgrade: blue-krill==3.1.0 requires django-environ<0.13.0, so django-environ moved from 0.13.0 to 0.12.0. I’m updating the dashboard AGENTS runtime note so the checked-in instructions don’t lie about the new Python range.


网关刚好用到 0.13.0

为啥要锁这个版本呢?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the checked-in dependency lock and the dashboard AGENTS runtime note mentioned in the issue. Compare the django-environ versions required by blue-krill 3.1.0 with the gateway's stated 0.13.0 requirement, then review the 3.14 resolution. Done means the dependency constraint and runtime instructions agree, or the reason for keeping the pin is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.