Skip to content

fix: regenerate poetry.lock to match pyproject.toml#140

Merged
ErikBjare merged 1 commit into
masterfrom
fix/relock-poetry
Jun 24, 2026
Merged

fix: regenerate poetry.lock to match pyproject.toml#140
ErikBjare merged 1 commit into
masterfrom
fix/relock-poetry

Conversation

@ErikBjare

Copy link
Copy Markdown
Member

poetry.lock had drifted from pyproject.tomlpoetry check --lock reports "pyproject.toml changed significantly since poetry.lock was last generated". In the activitywatch build this surfaces as:

Warning: poetry.lock is not consistent with pyproject.toml. You may be getting improper dependencies. Run `poetry lock [--no-update]` to fix it.

on every job (aw-core is built as a submodule there). Re-locked with Poetry 2.3.2. The diff is just the content-hash, generator version, and one normalized constraint (2023.03.62023.3.6) — no dependency versions change.

poetry.lock had drifted from pyproject.toml ('pyproject.toml changed
significantly since poetry.lock was last generated'), which made CI emit
'poetry.lock is not consistent with pyproject.toml. You may be getting
improper dependencies.' on every build. Re-locked with Poetry 2.3.2; the
only changes are the content-hash, generator version, and a normalized
version constraint — no dependency versions change.
@ErikBjare ErikBjare merged commit a4d2064 into master Jun 24, 2026
4 checks passed
@ErikBjare ErikBjare deleted the fix/relock-poetry branch June 24, 2026 11:04
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.

1 participant