review: bump py3.14.3 and pysudoer 0.0.3

[qlrd]

• Review chore/bump-py3143 changes;

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

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

[qlrd]

Review of Copilot comments from selfcustody#230 (bump py3.14.3):

Comment 1 — any_order=True weakens test:
cACK. Worth checking the test intent, but not blocking.

Comment 2 — Poetry git dep @v0.0.3 in URL, use tag = "v0.0.3":
ACK. Correct Poetry syntax — tag field is the proper way to pin a git dependency version.

Comment 3 — <=3.14.3 too restrictive, prefer <3.15:
ACK. Valid — current bound rejects future 3.14.x patches.

Comment 4 — Black job across Python matrix is wasteful:
cACK. Nit but reasonable — Black output is Python-version-independent.

@copilot comments 2 and 3 should be addressed. Comment 4 is a valid optimization nit.

[Copilot]

Review of Copilot comments from selfcustody#230 (bump py3.14.3):

Comment 1 — any_order=True weakens test:...

Addressed in commit e8344af:

• Comment 2: Fixed Poetry git dependency syntax — changed git = "https://github.com/qlrd/pysudoer.git@v0.0.3" to git = "https://github.com/qlrd/pysudoer.git", tag = "v0.0.3" in pyproject.toml.
• Comment 3: Changed Python upper bound from <=3.14.3 to <3.15 to allow future 3.14.x patch versions.
• Comment 4: Removed the matrix from the Black job in tests.yml — it now runs only on Python 3.12, since Black formatting is Python-version-independent.

[qlrd]

tACK e8344af

Copilot addressed comments 2, 3, and 4. Comment 1 left as cACK (non-blocking).

@copilot all resolved.

[Copilot]

Pull request overview

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

---

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

[Copilot]

The project Python constraint was broadened to <3.15, but the locked pysudoer dependency is limited to <=3.14.3 (per its package metadata). On Python 3.14.4+ this will likely make poetry install/resolution fail. Either keep the project constraint at <=3.14.3 or bump/update pysudoer (and other deps) to versions that declare support for newer 3.14 patch releases.

Suggested change

	python = ">3.10,<3.15"
	python = ">3.10,<=3.14.3"

[qlrd]

cACK. Valid concern — need to verify pysudoer's declared Python constraint before broadening. If pysudoer caps at 3.14.3, the project bound should match.

[Copilot]

pysudoer was switched to git + tag syntax, but poetry.lock is not updated in this PR. Since CI uses poetry.lock, this can leave installs pinned to whatever is currently locked (often reference = HEAD) and can also trigger Poetry's “pyproject changed significantly” error. Re-run poetry lock (or the repo’s preferred lock update command) and commit the updated lockfile so the tag pin and Python constraint are reflected.

Suggested change

	pysudoer = { git = "https://github.com/qlrd/pysudoer.git", tag = "v0.0.3" }
	pysudoer = "^0.0.3"

[qlrd]

ACK. poetry.lock must be regenerated after changing dependency syntax. However, suggesting pysudoer = "^0.0.3" (PyPI) is incorrect — pysudoer is not on PyPI, it's a git-only dependency. The lock file just needs a poetry lock run.

[qlrd]

@copilot please apply the following fix:

1. Run poetry lock to regenerate the lockfile after the dependency changes;

Note: pysudoer is NOT on PyPI — keep the git + tag syntax, do not change to "^0.0.3".