hostctl 0.2.6__tar.gz → 0.2.7__tar.gz

{hostctl-0.2.6 → hostctl-0.2.7}/CHANGELOG.md

@@ -7,7 +7,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
-## [0.2.6] - 2026-08-16
+## [0.2.7] - 2026-08-16
+
+### Changed
+
+- Dependency floors now name versions hostctl is actually tested against.
+  `pathlib_next` moves to `>=0.9.1,<0.10` and `netimps` to `>=0.2.0,<0.3`
+  (the `ssh` extra's `pathlib_next[sftp-async]` moves from `>=0.8.4` to the
+  same `>=0.9.1`). Both ceilings are unchanged, and no API hostctl calls has
+  moved — this only stops resolvers from choosing an install that does not
+  work.
+
+  The `pathlib_next` floor is above the start of its minor series for one
+  measured reason: `Path.symlink_to()` — and with it the `force=` keyword —
+  first exists in **0.9.1**. The composite path forwards `symlink_to` to
+  whichever backend path it was handed, so against a stock 0.9.0 `Path` the
+  whole chain raises `AttributeError` rather than linking anything. The
+  previous `>=0.8.6` floor therefore advertised support for installs where
+  composite `symlink_to` could never work. `netimps` needs nothing past
+  `0.2.0` and floors at the series start.
 
 ### Added
 
@@ -511,7 +529,8 @@ test suite on Python 3.9 through 3.14.
   assigned to it; a config-less host now builds its own family configuration
   instead.
 
-[Unreleased]: https://github.com/jose-pr/hostctl/compare/v0.2.6...HEAD
+[Unreleased]: https://github.com/jose-pr/hostctl/compare/v0.2.7...HEAD
+[0.2.7]: https://github.com/jose-pr/hostctl/compare/v0.2.6...v0.2.7
 [0.2.6]: https://github.com/jose-pr/hostctl/compare/v0.2.5...v0.2.6
 [0.2.5]: https://github.com/jose-pr/hostctl/compare/v0.2.4...v0.2.5
 [0.2.4]: https://github.com/jose-pr/hostctl/compare/v0.2.3...v0.2.4

{hostctl-0.2.6 → hostctl-0.2.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: hostctl
-Version: 0.2.6
+Version: 0.2.7
 Summary: Run commands and access files on a host, local or remote, protocol-agnostic
 Project-URL: Homepage, https://github.com/jose-pr/hostctl/
 Project-URL: Documentation, https://jose-pr.github.io/hostctl/
@@ -24,8 +24,8 @@ Classifier: Topic :: System :: Filesystems
 Classifier: Topic :: System :: Systems Administration
 Classifier: Typing :: Typed
 Requires-Python: >=3.9
-Requires-Dist: netimps<0.3,>=0.1
-Requires-Dist: pathlib-next<0.10,>=0.8.6
+Requires-Dist: netimps<0.3,>=0.2.0
+Requires-Dist: pathlib-next<0.10,>=0.9.1
 Provides-Extra: container
 Requires-Dist: docker<8,>=7.1; extra == 'container'
 Provides-Extra: dev
@@ -44,7 +44,7 @@ Provides-Extra: serial
 Requires-Dist: pyserial<4,>=3.5; extra == 'serial'
 Provides-Extra: ssh
 Requires-Dist: asyncssh; extra == 'ssh'
-Requires-Dist: pathlib-next[sftp-async]<0.10,>=0.8.4; extra == 'ssh'
+Requires-Dist: pathlib-next[sftp-async]<0.10,>=0.9.1; extra == 'ssh'
 Provides-Extra: winrm
 Requires-Dist: pywinrm<0.6,>=0.5.0; extra == 'winrm'
 Provides-Extra: winrm-credssp

{hostctl-0.2.6 → hostctl-0.2.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "hostctl"
-version = "0.2.6"
+version = "0.2.7"
 authors = [{ name = "Jose A." }]
 description = "Run commands and access files on a host, local or remote, protocol-agnostic"
 readme = "README.md"
@@ -34,19 +34,23 @@ classifiers = [
 # them. Transport implementations remain extras, so importing hostctl never
 # requires them.
 #
-# Both ranges span two minors deliberately: hostctl uses no API added in
-# pathlib_next 0.9 or netimps 0.2, so raising the floor would exclude working
-# installs for nothing. The ceilings stay at the next major-ish boundary
+# Each floor is the `.0` of the dependency's current minor series, raised
+# above it only where hostctl needs a later patch. pathlib_next is that
+# exception: `Path.symlink_to()` -- and with it the `force=` keyword -- first
+# exists in 0.9.1, and the composite path forwards `symlink_to` to whichever
+# backend path it was handed, so against a stock 0.9.0 `Path` the call raises
+# `AttributeError` (measured on 3.9 and 3.14). netimps has no such case and
+# floors at the series start. The ceilings stay at the next major-ish boundary
 # because both projects are pre-1.0, where a minor may break. Composite kwargs
-# passthrough does not change this: forwarding is signature-aware, so `force=`
-# is forwarded when the installed pathlib_next provides it and rejected at the
-# boundary when it does not (verified against 0.9.0 and 0.9.1).
-dependencies = ["pathlib_next>=0.8.6,<0.10", "netimps>=0.1,<0.3"]
+# passthrough does not change this: forwarding is signature-aware, so a
+# `force=` the installed pathlib_next does not declare is rejected at the
+# composite boundary rather than inside a transport.
+dependencies = ["pathlib_next>=0.9.1,<0.10", "netimps>=0.2.0,<0.3"]
 
 [project.optional-dependencies]
 # SSH-backed run()/path(): asyncssh for shell exec, pathlib_next's SftpPath
 # (asyncssh-only since 0.8.2) for the remote path backend.
-ssh = ["asyncssh", "pathlib_next[sftp-async]>=0.8.4,<0.10"]
+ssh = ["asyncssh", "pathlib_next[sftp-async]>=0.9.1,<0.10"]
 # Windows Remote Management command execution.
 winrm = ["pywinrm>=0.5.0,<0.6"]
 # PowerShell Remoting Protocol runspaces (Python 3.10+ only).  The marker