posit-cli 0.1.0__tar.gz → 0.2.0__tar.gz

posit_cli-0.2.0/.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+  - package-ecosystem: uv
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: chore(deps)
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: chore(deps)

{posit_cli-0.1.0 → posit_cli-0.2.0}/.github/workflows/ci.yaml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7
-      - uses: astral-sh/setup-uv@v9.0.0
+      - uses: astral-sh/setup-uv@v10.3.3
       - uses: extractions/setup-just@v4
       # Fail fast if uv.lock has drifted from pyproject.toml.
       - run: uv lock --locked
@@ -33,7 +33,7 @@ jobs:
           - "3.14"
     steps:
       - uses: actions/checkout@v7
-      - uses: astral-sh/setup-uv@v9.0.0
+      - uses: astral-sh/setup-uv@v10.3.3
         with:
           python-version: ${{ matrix.python-version }}
       - uses: extractions/setup-just@v4
@@ -43,7 +43,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7
-      - uses: astral-sh/setup-uv@v9.0.0
+        # hatch-vcs reads the version from the tags, so fetch them.
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v10.3.3
       - uses: extractions/setup-just@v4
       - run: just build
       - run: just smoke

posit_cli-0.2.0/.github/workflows/release.yaml

@@ -0,0 +1,62 @@
+name: Release
+on:
+  push:
+    tags:
+      - "v*.*.*"
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v10.3.3
+      - uses: extractions/setup-just@v4
+      # The tag is the only source of the version, so this only guards against a
+      # build that did not pick the tag up (shallow clone, dirty tree, two tags on
+      # one commit).
+      - name: assert build version matches tag
+        env:
+          TAG: ${{ github.ref_name }}
+        run: |
+          ver="$(just version)"
+          if [ "$TAG" != "v$ver" ]; then
+            echo "::error::tag '${TAG}' does not match build version 'v${ver}'"
+            exit 1
+          fi
+      - name: assert tag is on main
+        env:
+          TAG: ${{ github.ref_name }}
+        run: |
+          if ! git merge-base --is-ancestor HEAD origin/main; then
+            echo "::error::tag '${TAG}' points to a commit that is not on main"
+            exit 1
+          fi
+      - run: just build
+      - run: just smoke
+      - uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+  # Runs only after PyPI accepts the upload, so a failed publish leaves no release.
+  github-release:
+    needs: publish
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+      - name: create GitHub release
+        env:
+          GH_TOKEN: ${{ github.token }}
+          TAG: ${{ github.ref_name }}
+        run: gh release create "$TAG" dist/* --title "$TAG" --generate-notes

{posit_cli-0.1.0 → posit_cli-0.2.0}/.gitignore

@@ -9,6 +9,9 @@ dist/
 .venv/
 venv/
 
+# Written at build time by hatch-vcs
+/src/posit_cli/_version.py
+
 # Tooling
 .pytest_cache/
 .ruff_cache/

{posit_cli-0.1.0 → posit_cli-0.2.0}/CLAUDE.md

@@ -37,4 +37,7 @@ posit-sdk) and the OAuth-release gotcha.
   `RSConnectClient`), which has no stability contract. `tests/test_rsconnect_contract.py` guards
   the surface we depend on; pin the rsconnect version and re-verify on bumps.
 
+- The git tag sets the version, through `hatch-vcs`. `pyproject.toml` has no `version` field.
+  Do not add one.
+
 See `RELEASE.md` for how to cut a release to PyPI.

posit_cli-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# Contributing
+
+This guide covers local development for `posit-cli`. End-user installation and CLI usage are documented in [README.md](README.md).
+
+## Prerequisites
+
+Install these tools before starting:
+
+- Git
+- Python 3.8 or newer
+- [uv](https://docs.astral.sh/uv/)
+- [just](https://github.com/casey/just)
+
+The project uses uv for dependency management and virtual environments. The supported Python versions are 3.8 through 3.14, which are tested in CI.
+
+## Set Up
+
+Clone the repository and change into its directory:
+
+```console
+git clone https://github.com/posit-dev/posit-cli.git
+cd posit-cli
+```
+
+Sync the project, test, and lint dependencies:
+
+```console
+just deps
+```
+
+This runs `uv sync --all-extras`, using `uv.lock` to create or update the project environment in `.venv`. You do not need to activate `.venv` when using the `just` recipes.
+
+To put an editable `posit` command on your `PATH`, run:
+
+```console
+just dev
+posit --help
+```
+
+`just dev` installs the checkout as an editable uv tool. Changes to the source are therefore available through `posit` without rebuilding or reinstalling the package. If the command is not found, add the directory printed by `uv tool dir --bin` to your `PATH`, or run `uv tool update-shell`.
+
+## Common Commands
+
+Run these commands from the repository root:
+
+| Command | Purpose |
+| --- | --- |
+| `just deps` | Sync runtime, test, and lint dependencies from `uv.lock`. |
+| `just dev` | Install the checkout as an editable uv tool. |
+| `just test` | Run tests against Python 3.13. |
+| `just test 3.8` | Run tests against a specific Python version. |
+| `just lint` | Check formatting and run Ruff. |
+| `just fmt` | Format files and apply Ruff fixes. |
+| `just build` | Build the wheel and source distribution in `dist/`. |
+| `just smoke` | Run `posit --help` from the latest built wheel. |
+| `just install` | Install the latest built wheel as a non-editable uv tool. |
+| `just uninstall` | Remove the uv-managed `posit-cli` tool. |
+| `just clean` | Remove build, test, and lint artifacts. |
+
+`just smoke` expects a wheel to exist in `dist/`, so run `just build` first unless another command has already built one.
+
+## Dependency Changes
+
+Runtime dependencies and optional test/lint dependencies are declared in `pyproject.toml`. When changing them:
+
+1. Update `pyproject.toml`.
+2. Run `uv lock` to update `uv.lock`.
+3. Run `just deps` to sync the local environment.
+4. Include both `pyproject.toml` and `uv.lock` in the change.
+
+CI checks that the lockfile is current with `uv lock --locked`.
+
+## Before Opening A Pull Request
+
+Run the checks relevant to your change. The normal local validation sequence is:
+
+```console
+just deps
+just lint
+just test
+just build
+just smoke
+```
+
+CI also runs the test suite against Python 3.8, 3.9, 3.10, 3.11, 3.12, 3.13, and 3.14. Add or update tests when changing behavior, and update user-facing documentation in `README.md` when the CLI changes.
+
+Keep commits focused and use Conventional Commit messages, such as `fix: handle expired Connect tokens` or `docs: clarify local setup`.
+
+## Releases
+
+Release preparation and publishing are documented in [RELEASE.md](RELEASE.md). In particular, do not add a hard-coded version to `pyproject.toml`; release versions come from Git tags through `hatch-vcs`.

{posit_cli-0.1.0 → posit_cli-0.2.0}/Justfile

@@ -1,5 +1,9 @@
 # posit-cli task runner. Run `just --list` to see recipes.
 
+# Sync project and development dependencies into the project environment
+deps:
+    uv sync --all-extras
+
 # Run the test suite against a single Python version (default 3.13)
 test py="3.13":
     uv run --python {{py}} --extra test pytest tests
@@ -25,13 +29,21 @@ smoke:
     WHL=$(ls -t dist/*.whl | head -1)
     uv run --no-project --with "$WHL" posit --help
 
-# Install the most recently built wheel into the active environment
+# Install the most recently built wheel as a standalone uv tool
 install: build
-    uv pip install "$(ls -t dist/*.whl | head -1)"
+    uv tool install --force "$(ls -t dist/*.whl | head -1)"
+
+# Install the project as an editable standalone uv tool
+dev:
+    uv tool install --editable --force .
+
+# Remove the installed standalone uv tool
+uninstall:
+    uv tool uninstall posit-cli
 
-# Print the current version
+# Print the version that a build gets from the current git state
 version:
-    @uv version --short
+    @uvx hatch version
 
 # Remove build/test artifacts
 clean:

{posit_cli-0.1.0 → posit_cli-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: posit-cli
-Version: 0.1.0
+Version: 0.2.0
 Summary: A single, friendly command-line interface for Posit Connect, in the spirit of gh.
 Author: Posit Software, PBC
 License-Expression: MIT
@@ -9,9 +9,11 @@ Requires-Python: >=3.8
 Requires-Dist: click>=8.0
 Requires-Dist: jq>=1.4
 Requires-Dist: keyring>=23.0
-Requires-Dist: rsconnect-python<2,>=1.30
+Requires-Dist: rsconnect-python<2,>=1.33
 Provides-Extra: lint
 Requires-Dist: ruff>=0.6; extra == 'lint'
+Provides-Extra: snowflake
+Requires-Dist: rsconnect-python[snowflake]; extra == 'snowflake'
 Provides-Extra: test
 Requires-Dist: pytest>=7; extra == 'test'
 Description-Content-Type: text/markdown
@@ -30,25 +32,47 @@ This project is in early-stage development and so far only supports Posit Connec
 
 ## Installation
 
-`posit-cli` isn't on PyPI yet. Install the latest version straight from GitHub
-with [`uv`](https://docs.astral.sh/uv/):
+Install [`posit-cli` from PyPI](https://pypi.org/project/posit-cli/) with
+[`uv`](https://docs.astral.sh/uv/):
+
+```console
+uv tool install posit-cli
+```
+
+To get unreleased changes, install from GitHub instead:
 
 ```console
 uv tool install git+https://github.com/posit-dev/posit-cli.git
 ```
 
-If you authenticate to GitHub over SSH, use the `git+ssh://` form instead (uv
-requires the `git@` username):
+If you authenticate to GitHub over SSH, use the `git+ssh://` form (uv requires
+the `git@` username):
 
 ```console
 uv tool install git+ssh://git@github.com/posit-dev/posit-cli.git
 ```
 
-Either way this puts the `posit` executable on your `PATH`. To upgrade later, run
+Each of these puts the `posit` executable on your `PATH`. To upgrade later, run
 `uv tool upgrade posit-cli`. See uv's
 [Git authentication docs](https://docs.astral.sh/uv/concepts/authentication/git/)
 for tokens and other hosts.
 
+### Connect on Snowflake
+
+To deploy to Posit Connect on Snowflake, install the Snowflake extra instead:
+
+```console
+uv tool install 'posit-cli[snowflake]'
+# or: pip install 'posit-cli[snowflake]'
+```
+
+This includes the Snowflake CLI. Before deploying, configure a
+[Snowflake CLI connection](https://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-connections)
+with access to your Connect instance and `authenticator` set to `snowflake_jwt`
+(key-pair authentication) or `oauth`. Select it with
+`--snowflake-connection-name` when adding the Connect server with
+`posit connect add`; see `posit connect add --help` for options.
+
 ## Getting started
 
 **1. Log in.** Point `posit` at your Connect server and authenticate. This runs
@@ -126,10 +150,27 @@ $ posit connect api v1/users -X GET -f page_size=5          # or force GET
 $ posit connect api v1/content -f name=my-app              # POST body (creates content)
 ```
 
+## `posit connect version`
+
+Print the Connect server version using your saved credentials:
+
+```console
+$ posit connect version
+$ posit connect version --name production
+$ posit connect version --server https://connect.example.com --api-key "$CONNECT_API_KEY"
+```
+
+The command supports `-n`/`--name`, `-s`/`--server`, `-k`/`--api-key`,
+`--no-tls-verify`, and `-c`/`--cacert`, with the same connection environment
+variables as `posit connect api`. It prints an empty line if the server hides
+its version. Rsconnect's `CONNECT_SERVER_VERSION` environment variable overrides
+the reported version.
+
 ## `posit connect *`
 
 `posit` wraps [`rsconnect-python`](https://github.com/posit-dev/rsconnect-python):
 it re-exposes the full `rsconnect` command set under `posit connect`, in addition to the `api` utility.
+The `version` command is overridden to report the Connect server version.
 
 ## Using `posit` with Claude Code
 

{posit_cli-0.1.0 → posit_cli-0.2.0}/README.md

@@ -12,25 +12,47 @@ This project is in early-stage development and so far only supports Posit Connec
 
 ## Installation
 
-`posit-cli` isn't on PyPI yet. Install the latest version straight from GitHub
-with [`uv`](https://docs.astral.sh/uv/):
+Install [`posit-cli` from PyPI](https://pypi.org/project/posit-cli/) with
+[`uv`](https://docs.astral.sh/uv/):
+
+```console
+uv tool install posit-cli
+```
+
+To get unreleased changes, install from GitHub instead:
 
 ```console
 uv tool install git+https://github.com/posit-dev/posit-cli.git
 ```
 
-If you authenticate to GitHub over SSH, use the `git+ssh://` form instead (uv
-requires the `git@` username):
+If you authenticate to GitHub over SSH, use the `git+ssh://` form (uv requires
+the `git@` username):
 
 ```console
 uv tool install git+ssh://git@github.com/posit-dev/posit-cli.git
 ```
 
-Either way this puts the `posit` executable on your `PATH`. To upgrade later, run
+Each of these puts the `posit` executable on your `PATH`. To upgrade later, run
 `uv tool upgrade posit-cli`. See uv's
 [Git authentication docs](https://docs.astral.sh/uv/concepts/authentication/git/)
 for tokens and other hosts.
 
+### Connect on Snowflake
+
+To deploy to Posit Connect on Snowflake, install the Snowflake extra instead:
+
+```console
+uv tool install 'posit-cli[snowflake]'
+# or: pip install 'posit-cli[snowflake]'
+```
+
+This includes the Snowflake CLI. Before deploying, configure a
+[Snowflake CLI connection](https://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-connections)
+with access to your Connect instance and `authenticator` set to `snowflake_jwt`
+(key-pair authentication) or `oauth`. Select it with
+`--snowflake-connection-name` when adding the Connect server with
+`posit connect add`; see `posit connect add --help` for options.
+
 ## Getting started
 
 **1. Log in.** Point `posit` at your Connect server and authenticate. This runs
@@ -108,10 +130,27 @@ $ posit connect api v1/users -X GET -f page_size=5          # or force GET
 $ posit connect api v1/content -f name=my-app              # POST body (creates content)
 ```
 
+## `posit connect version`
+
+Print the Connect server version using your saved credentials:
+
+```console
+$ posit connect version
+$ posit connect version --name production
+$ posit connect version --server https://connect.example.com --api-key "$CONNECT_API_KEY"
+```
+
+The command supports `-n`/`--name`, `-s`/`--server`, `-k`/`--api-key`,
+`--no-tls-verify`, and `-c`/`--cacert`, with the same connection environment
+variables as `posit connect api`. It prints an empty line if the server hides
+its version. Rsconnect's `CONNECT_SERVER_VERSION` environment variable overrides
+the reported version.
+
 ## `posit connect *`
 
 `posit` wraps [`rsconnect-python`](https://github.com/posit-dev/rsconnect-python):
 it re-exposes the full `rsconnect` command set under `posit connect`, in addition to the `api` utility.
+The `version` command is overridden to report the Connect server version.
 
 ## Using `posit` with Claude Code
 

posit_cli-0.2.0/RELEASE.md

@@ -0,0 +1,34 @@
+# Releasing
+
+The git tag is the only source of the version. `pyproject.toml` has no `version` field —
+`hatch-vcs` reads the tag at build time. Do not add one.
+
+Follow these steps to publish a new version to PyPI:
+
+1. Make sure `main` holds everything you want in the release.
+2. Tag the commit on `main` as `vX.Y.Z`.
+3. Push the tag. This triggers `.github/workflows/release.yaml`.
+
+```console
+git checkout main && git pull
+git tag v0.2.0
+git push origin v0.2.0
+```
+
+The release workflow confirms that the build picked the tag up and that the tag is on `main`,
+builds the wheel and sdist, smoke-tests the wheel, then publishes to PyPI through GitHub's OIDC
+trusted-publisher flow. No PyPI token is stored in this repo. After PyPI accepts the upload, a
+second job creates a GitHub release for the tag, with generated notes and the built artifacts
+attached.
+
+Run `just version` to see the version that a build gets from the current git state. A commit
+after the last tag gets a development version (for example `0.2.1.dev3+g1a2b3c4`), which PyPI
+rejects. Only a clean, tagged commit produces a release version.
+
+## One-time setup for a new repo
+
+- Create a `release` environment under the repo's Settings > Environments, with required
+  reviewers. The `publish` job runs under this environment; without required reviewers, any tag
+  push publishes to PyPI immediately with no human gate.
+- Configure a trusted publisher for `posit-cli` on PyPI with: Owner `posit-dev`, Repository name
+  `posit-cli`, Workflow name `release.yaml`, Environment name `release`.

{posit_cli-0.1.0 → posit_cli-0.2.0}/pyproject.toml

@@ -1,6 +1,7 @@
 [project]
 name = "posit-cli"
-version = "0.1.0"
+# The version comes from the git tag, through hatch-vcs. Never hard-code it here.
+dynamic = ["version"]
 description = "A single, friendly command-line interface for Posit Connect, in the spirit of gh."
 readme = "README.md"
 requires-python = ">=3.8"
@@ -11,7 +12,7 @@ dependencies = [
     # posit-cli reuses rsconnect-python's *internal* API (RSConnectExecutor,
     # RSConnectClient). These have no stability contract, so re-verify the internals
     # on bumps. See tests/test_rsconnect_contract.py.
-    "rsconnect-python>=1.30,<2",
+    "rsconnect-python>=1.33,<2",
     # rsconnect imports `keyring` optionally; we depend on it directly so OAuth
     # tokens land in the OS keyring.
     "keyring>=23.0",
@@ -24,13 +25,22 @@ dependencies = [
 posit = "posit_cli.__main__:cli"
 
 [project.optional-dependencies]
+snowflake = ["rsconnect-python[snowflake]"]
 test = ["pytest>=7"]
 lint = ["ruff>=0.6"]
 
 [build-system]
-requires = ["hatchling"]
+requires = ["hatchling", "hatch-vcs"]
 build-backend = "hatchling.build"
 
+[tool.hatch.version]
+source = "vcs"
+
+# Write the resolved version into the package. An sdist has no git metadata, so a
+# wheel built from an sdist reads this file instead of asking git.
+[tool.hatch.build.hooks.vcs]
+version-file = "src/posit_cli/_version.py"
+
 [tool.hatch.build.targets.wheel]
 packages = ["src/posit_cli"]
 

{posit_cli-0.1.0 → posit_cli-0.2.0}/skills/posit-cli/SKILL.md

@@ -175,6 +175,10 @@ posit connect deploy quarto ./report
 posit connect deploy manifest ./manifest.json   # deploy a prepared bundle
 ```
 
+To update existing Connect content instead of creating new content, pass its
+GUID with `--guid <guid>`. Find the GUID with
+`posit connect api v1/content -q '.[] | "\(.guid)  \(.title)"'`.
+
 Available deploy targets include `api`, `bokeh`, `bundle`, `dash`, `fastapi`,
 `flask`, `gradio`, `html`, `manifest`, `nodejs`, `notebook`, `panel`, `pyproject`,
 `quarto`, `shiny`, `streamlit`, `tensorflow`, `voila`. Use `quickstart` to
@@ -191,6 +195,8 @@ These are rsconnect commands — run `posit connect <command> --help` for detail
 - `add` / `list` / `remove` / `details` / `info` — manage saved servers and
   deployment metadata.
 - `login` / `logout` — OAuth credential management.
+- `token` — print the OAuth access token from `login` (for the Connect SDKs or
+  `curl`). `--refresh` gets a new one after a 401; exit status 4 means log in again.
 - `bootstrap` — create an initial admin user on a fresh Connect instance.
 
 ## When something fails
@@ -208,15 +214,21 @@ These are rsconnect commands — run `posit connect <command> --help` for detail
 
 ## Installing the CLI
 
-`posit-cli` isn't on PyPI yet; install from GitHub with [`uv`](https://docs.astral.sh/uv/):
+Install from PyPI with [`uv`](https://docs.astral.sh/uv/):
+
+```console
+uv tool install posit-cli    # `posit` onto your PATH
+uv tool upgrade posit-cli    # later, to update
+```
+
+For unreleased changes, install from GitHub instead:
 
 ```console
-uv tool install git+https://github.com/posit-dev/posit-cli.git   # `posit` onto your PATH
-uv tool upgrade posit-cli                                         # later, to update
+uv tool install git+https://github.com/posit-dev/posit-cli.git
 ```
 
-If GitHub is set up for SSH auth, use the `git+ssh://` form instead (uv requires
-the `git@` username):
+If GitHub is set up for SSH auth, use the `git+ssh://` form (uv requires the
+`git@` username):
 
 ```console
 uv tool install git+ssh://git@github.com/posit-dev/posit-cli.git

posit_cli-0.2.0/src/posit_cli/_version.py

@@ -0,0 +1,24 @@
+# file generated by vcs-versioning
+# don't change, don't track in version control
+from __future__ import annotations
+
+__all__ = [
+    "__version__",
+    "__version_tuple__",
+    "version",
+    "version_tuple",
+    "__commit_id__",
+    "commit_id",
+]
+
+version: str
+__version__: str
+__version_tuple__: tuple[int | str, ...]
+version_tuple: tuple[int | str, ...]
+commit_id: str | None
+__commit_id__: str | None
+
+__version__ = version = '0.2.0'
+__version_tuple__ = version_tuple = (0, 2, 0)
+
+__commit_id__ = commit_id = None

{posit_cli-0.1.0 → posit_cli-0.2.0}/src/posit_cli/connect/__init__.py

@@ -9,6 +9,7 @@ import click
 from rsconnect.main import cli as rsconnect_cli
 
 from .api import api as api_cmd
+from .version import version as version_cmd
 
 
 _epilog = (
@@ -29,3 +30,5 @@ for _name, _cmd in rsconnect_cli.commands.items():
     connect.add_command(_cmd, name=_name)
 
 connect.add_command(api_cmd, name="api")
+# The mounted command reports the rsconnect package version.
+connect.add_command(version_cmd, name="version")

posit_cli-0.2.0/src/posit_cli/connect/version.py

@@ -0,0 +1,68 @@
+"""Print the selected Connect server's version."""
+
+from typing import Optional
+
+import click
+from rsconnect.api import RSConnectException, RSConnectExecutor
+
+
+@click.command(
+    context_settings={"help_option_names": ["-h", "--help"]},
+    short_help="Show the Connect server version.",
+)
+@click.option("--name", "-n", default=None, help="Nickname of a saved server.")
+@click.option(
+    "--server",
+    "-s",
+    default=None,
+    envvar="CONNECT_SERVER",
+    help="Connect server URL [env: CONNECT_SERVER].",
+)
+@click.option(
+    "--api-key",
+    "-k",
+    default=None,
+    envvar="CONNECT_API_KEY",
+    help="Connect API key [env: CONNECT_API_KEY].",
+)
+@click.option(
+    "--no-tls-verify",
+    "insecure",
+    is_flag=True,
+    default=False,
+    envvar="CONNECT_INSECURE",
+    help="Skip TLS certificate verification (still uses TLS) [env: CONNECT_INSECURE].",
+)
+@click.option(
+    "--cacert",
+    "-c",
+    type=click.Path(exists=True, dir_okay=False),
+    default=None,
+    envvar="CONNECT_CA_CERTIFICATE",
+    help="Path to trusted TLS CA certificate.",
+)
+def version(
+    name: Optional[str],
+    server: Optional[str],
+    api_key: Optional[str],
+    insecure: bool,
+    cacert: Optional[str],
+) -> None:
+    """Print the Connect server version using saved credentials by default.
+
+    CONNECT_SERVER_VERSION overrides the reported version. If the server hides
+    its version, print an empty line.
+    """
+    try:
+        executor = RSConnectExecutor(
+            ctx=None,
+            name=name,
+            url=server,
+            api_key=api_key,
+            insecure=insecure,
+            cacert=cacert,
+        )
+        server_version = executor.client.server_version()
+    except RSConnectException as exc:
+        raise click.ClickException(str(exc)) from exc
+    click.echo(server_version)

{posit_cli-0.1.0 → posit_cli-0.2.0}/tests/test_rsconnect_contract.py

@@ -17,6 +17,7 @@ def test_executor_surface():
         assert expected in params, f"RSConnectExecutor lost __init__ param {expected!r}"
 
     assert hasattr(RSConnectClient, "request")
+    assert callable(getattr(RSConnectClient, "server_version", None))
     req_params = inspect.signature(RSConnectClient.request).parameters
     for expected in ("method", "path", "query_params", "body", "headers"):
         assert expected in req_params, f"RSConnectClient.request lost {expected!r}"