Repository navigation
Correct the Dependabot note about the dpctl floor - #3171
antonwolfy wants to merge 5 commits into
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The version-pin instructions need to preserve release-only build requirements in pyproject.toml and conda-recipe-cf/meta.yaml, with the same clarification in .github/dependabot.yml, to avoid requiring unavailable development versions.
1 open issue
What changed in this PR
This documentation-only PR corrects the guidance for handling Dependabot updates to dpnp’s dpctl development-version floor, following #3166 and the coordinated update in #3169.
Changes:
- Replaces the incorrect claim that Dependabot does not bump minimum versions or development prereleases.
- Documents that release-triggered
dpctlPRs should prompt a coordinated manual update rather than be merged directly. - Leaves dependency versions and Dependabot configuration behavior unchanged.
| File | Description |
|---|---|
.github/dependabot.yml |
Corrects the comment describing how to handle dpctl release updates. |
.github/AGENTS.md |
Adds contributor guidance for coordinated manual dpctl updates. |
Review effort: Balanced
|
Array API standard conformance tests for dpnp=0.22.0dev1=np2py314h8d9cdd5_20 ran successfully. |
|
View rendered docs @ https://intelpython.github.io/dpnp/pull/3171/index.html |
vlad-perevezentsev
left a comment
There was a problem hiding this comment.
LGTM
Thank you @antonwolfy

Dependabot opened #3166 to raise
dpctl>=0.23.0dev0inenvironments/dpctl_pkg.txtto>=0.23.0oncedpctl0.23.0 was released, although the note in.github/dependabot.ymlsays>=floors and dev pre-releases are not bumped. On master that floor tracks thedpctldev series together withpyproject.toml,environments/dpctl_pkg.ymland the conda recipes, so such a PR is not meant to be merged. It is the signal to bumpdpctlto the next dev series by hand in all those places, as #3169 does.This PR replaces the incorrect note with that rule and adds it to
.github/AGENTS.md.