Skip to content

Updated poetry.lock#26

Merged
spiani merged 1 commit into
mainfrom
update_lock
Apr 16, 2026
Merged

Updated poetry.lock#26
spiani merged 1 commit into
mainfrom
update_lock

Conversation

@spiani

@spiani spiani commented Apr 16, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@spiani spiani self-assigned this Apr 16, 2026
Copilot AI review requested due to automatic review settings April 16, 2026 17:23
@spiani spiani merged commit 9896721 into main Apr 16, 2026
3 checks passed
@spiani spiani deleted the update_lock branch April 16, 2026 17:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates Python dependency resolution and development tooling versions by modifying pyproject.toml constraints and regenerating poetry.lock.

Changes:

  • Relax/adjust version constraints for xarray, dask, numba, and deptry in pyproject.toml.
  • Bump dev tooling versions (notably pre-commit and deptry).
  • Regenerate poetry.lock, updating many transitive packages and introducing new locked packages (e.g., gsw, tomli).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 4 comments.

File Description
pyproject.toml Updates dependency constraints and dev tooling version requirements.
poetry.lock Regenerated lockfile capturing updated direct/transitive dependency versions and hashes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread pyproject.toml
dask = ">=2026.1.2"
ogs-riverger = {git = "https://github.com/inogs/ogs_riverger.git"}
numba = "^0.64.0"
numba = ">=0.64.0"

Copilot AI Apr 16, 2026

Copy link

Choose a reason for hiding this comment

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

dask/numba were changed from caret constraints to >=... with no upper bound. That widens the allowed range significantly compared to the rest of this file (e.g., numpy = "^2.1.3") and can make installs non-reproducible or pull in incompatible future releases. Prefer a bounded range (caret or explicit upper bound) that matches what you’ve validated in the lockfile.

Suggested change
numba = ">=0.64.0"
numba = "^0.64.0"

Copilot uses AI. Check for mistakes.
Comment thread pyproject.toml
pre-commit = "^3.8.0"
deptry = "^0.21.2"
pre-commit = "^4.5.0"
deptry = ">0.21.2"

Copilot AI Apr 16, 2026

Copy link

Choose a reason for hiding this comment

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

deptry = ">0.21.2" both excludes 0.21.2 and leaves the upper bound unbounded; the lockfile resolves to 0.25.1, so this constraint could be tightened to the intended compatible range (e.g., caret from 0.25.1 or an explicit <1.0 upper bound) to avoid unexpected breaking updates.

Suggested change
deptry = ">0.21.2"
deptry = "^0.25.1"

Copilot uses AI. Check for mistakes.
Comment thread pyproject.toml
Comment on lines 13 to 16
bitsea = { git = "https://github.com/inogs/bit.sea.git", branch = "master" }
xarray = "^2026.1.0"
xarray = ">2026.1.0"
pandas = { version = "^2.3.0", extras = ["openpyxl"]}
openpyxl= "^3.1.5"

Copilot AI Apr 16, 2026

Copy link

Choose a reason for hiding this comment

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

The PR title indicates only an updated lockfile, but this change also modifies dependency constraints in pyproject.toml. Either update the PR title/description to reflect the spec changes, or move these spec edits into a separate PR to keep dependency bumps traceable.

Copilot uses AI. Check for mistakes.
Comment thread pyproject.toml
scipy = "^1.15.2"
bitsea = { git = "https://github.com/inogs/bit.sea.git", branch = "master" }
xarray = "^2026.1.0"
xarray = ">2026.1.0"

Copilot AI Apr 16, 2026

Copy link

Choose a reason for hiding this comment

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

xarray is specified as >2026.1.0, which (a) excludes 2026.1.0 and (b) has no upper bound, so future major/CalVer releases can be resolved unexpectedly. Consider using a bounded constraint consistent with the other deps (e.g., caret from the intended baseline, or an explicit <2027.0.0 upper bound).

Suggested change
xarray = ">2026.1.0"
xarray = ">=2026.1.0,<2027.0.0"

Copilot uses AI. Check for mistakes.
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.

2 participants