uv-upsync 2.4.1__tar.gz → 2.4.2__tar.gz

{uv_upsync-2.4.1 → uv_upsync-2.4.2}/.editorconfig

@@ -13,3 +13,7 @@ trim_trailing_whitespace = true
 [{*.py,*.pyi,*.ipynb}]
 indent_size = 4
 tab_width = 4
+
+[{*.rs}]
+indent_size = 4
+tab_width = 4

{uv_upsync-2.4.1 → uv_upsync-2.4.2}/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,6 @@
 # Pull Request Checklist
 
-<!-- Optional — uncomment if this PR closes an issue -->
+<!-- Optional: uncomment if this PR closes an issue -->
 <!-- Resolves: #issue-number-here -->
 
 ## Summary

{uv_upsync-2.4.1 → uv_upsync-2.4.2}/.github/workflows/ci.yaml

@@ -7,26 +7,26 @@ on:
   workflow_dispatch:
 
 concurrency:
-  group: ci-${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
 
 permissions:
   contents: read
 
 jobs:
   ci:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04-arm
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
 
       - name: Install just
-        uses: extractions/setup-just@v3
+        uses: extractions/setup-just@v4
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v6
+        uses: astral-sh/setup-uv@v10.1.0
         with:
-          python-version: "3.13"
+          python-version: "3.14"
 
       - name: Install dependencies
         run: just install
@@ -36,6 +36,3 @@ jobs:
 
       - name: Run tests
         run: just test
-
-      - name: Run audit
-        run: just audit

{uv_upsync-2.4.1 → uv_upsync-2.4.2}/.github/workflows/release.yaml

@@ -10,14 +10,18 @@ on:
 permissions:
   contents: write
 
+concurrency:
+  group: release
+  cancel-in-progress: false
+
 jobs:
   tag:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04-arm
     outputs:
       tag: v${{ steps.version.outputs.version }}
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
@@ -30,20 +34,22 @@ jobs:
         run: echo "$RUNNER_TEMP/git-cliff/bin" >> "$GITHUB_PATH"
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v6
+        uses: astral-sh/setup-uv@v10.1.0
         with:
-          python-version: "3.13"
+          python-version: "3.14"
 
       - name: Resolve version
         id: version
         run: |
           if [[ -n "${{ github.event.inputs.version }}" ]]; then
             VERSION="${{ github.event.inputs.version }}"
+            VERSION="${VERSION#v}"
           else
             VERSION=$(git-cliff --bumped-version)
             VERSION="${VERSION#v}"
           fi
           echo "version=${VERSION}" >> "$GITHUB_OUTPUT"
+          echo "resolved version: ${VERSION}"
 
       - name: Update version
         run: uv version "${{ steps.version.outputs.version }}"
@@ -67,42 +73,45 @@ jobs:
 
   release:
     needs: tag
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04-arm
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
           ref: ${{ needs.tag.outputs.tag }}
           fetch-depth: 0
 
-      - name: Generate Changelog
+      - name: Generate changelog
         uses: orhun/git-cliff-action@v4
         id: changelog
         with:
           args: --latest --strip header
 
       - name: Create GitHub Release
-        uses: softprops/action-gh-release@v2
+        uses: softprops/action-gh-release@v3
         with:
           tag_name: ${{ needs.tag.outputs.tag }}
           body: ${{ steps.changelog.outputs.content }}
 
   publish:
     needs: [tag, release]
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04-arm
+    permissions:
+      contents: read
+      id-token: write
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
           ref: ${{ needs.tag.outputs.tag }}
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v6
+        uses: astral-sh/setup-uv@v10.1.0
         with:
-          python-version: "3.13"
+          python-version: "3.14"
 
       - name: Build
         run: uv build
 
       - name: Publish to PyPI
-        run: uv publish --token ${{ secrets.PYPI_TOKEN }}
+        run: uv publish --trusted-publishing always

uv_upsync-2.4.2/.python-version

@@ -0,0 +1 @@
+3.14

uv_upsync-2.4.2/AGENTS.md

@@ -0,0 +1 @@
+CLAUDE.md

{uv_upsync-2.4.1 → uv_upsync-2.4.2}/CHANGELOG.md

@@ -2,6 +2,70 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.4.2] - 2026-09-20
+
+### Bug fixes
+
+- Import Self from typing-extensions for python 3.10
+- Import Self under TYPE_CHECKING to restore Python 3.10 support
+- **commands**: Widen write_dl rows annotation to Iterable
+
+### Build
+
+- Bump python to 3.14
+- Update dependencies
+- Update dependencies
+- Update dependencies
+- **deps**: Update dependency lockfile
+- **deps**: Update dependencies
+- **deps**: Update dependencies
+
+### CI/CD
+
+- Pin workflow python to 3.14 and rename action.yml to yaml
+- Pin setup-uv to v10.1.0
+- Drop label sync in favor of terraform
+- Publish to pypi via trusted publishing instead of a token
+- Ignore rules newly stabilized in ruff 0.16
+- Drop ruff format --check from lint; suppress more ty rules
+- Use uv run pytest for project venv; format example file
+- Fix action versions and test recipe failures
+- Drop hashFiles guard; move .no-tests sentinel handling into justfile
+- Flatten to one job per language
+- Bump action versions to latest major
+- Standardize workflow to per-language parallel pipelines on ubuntu-24.04-arm
+
+### Documentation
+
+- Use absolute raw url for logo and refresh version notes
+- Rewrite CLAUDE.md from scratch
+- Regenerate CLAUDE.md and add AGENTS.md
+- **release**: Drop trusted publishing header comments
+- Add pull request template
+- Shorten module docstring to fit the line-length limit
+- Regenerate CLAUDE.md
+- Document the module docstring convention
+- Normalize module and package docstrings
+- Normalize punctuation and drop AI-flavored phrasing
+- Refresh CLAUDE.md for current justfile + CI shape
+- **ci**: Document required secrets at top of workflow files
+
+### Miscellaneous
+
+- **assets**: Drop svg repo attribution comments
+- Repository housekeeping
+- Symlink AGENTS.md to CLAUDE.md
+- Remove local pull request template
+- **deps**: Update locked dependencies
+- Update dependency lockfile
+- Add editorconfig
+- **justfile**: Use uv lock --upgrade for update, scope pyupgrade to . excluding .venv
+- Standardize justfile recipes and refresh CLAUDE.md
+
+### Refactor
+
+- **justfile**: Standardize recipe names and ordering
+
 ## [2.4.1] - 2026-05-31
 
 ### Build
@@ -24,6 +88,10 @@ All notable changes to this project will be documented in this file.
 
 - Tidy logging and parser internals
 
+### Release
+
+- V2.4.1
+
 ## [2.4.0] - 2026-05-30
 
 ### Bug fixes

uv_upsync-2.4.2/CLAUDE.md

@@ -0,0 +1,73 @@
+# uv-upsync
+
+## What This Is
+
+A single-command CLI that raises the **lower bounds of dependency specifiers in `pyproject.toml`** to the latest published versions, then re-locks with `uv`.
+
+The distinction that defines the whole project: `uv lock --upgrade` refreshes the **lockfile** but leaves `httpx>=0.24.0` written as `>=0.24.0` forever. `uv-upsync` rewrites the human-authored bound in `pyproject.toml` itself, and does so surgically - only the version token is replaced, so operators, extras, environment markers, spacing and comments survive verbatim.
+
+Published to PyPI as `uv-upsync`. `README.md` owns the option table, the `[tool.uv-upsync]` keys and the usage examples.
+
+## Distribution Surfaces
+
+Any change to the CLI flags has to land in four places, not one:
+
+1. `src/uv_upsync/__main__.py` - the click options
+2. `README.md` - the options table and the `[tool.uv-upsync]` example block
+3. `action.yaml` - the composite GitHub Action (passes `inputs.args` through to `uvx uv-upsync`, captures stdout into a `summary` output for PR bodies)
+4. `.pre-commit-hooks.yaml` - the `uv-upsync` and `uv-upsync-check` hooks, both `pass_filenames: false` and gated on `^pyproject\.toml$`
+
+A new config key also needs a branch in `config.load_config` plus its validator, and the corresponding `flag = flag or settings.flag` line in `cli`.
+
+## Invariants Worth Knowing Before Editing
+
+- **Only lower bounds are raised.** `UPGRADABLE_OPERATORS = {">=", ">", "~="}`; `==`/`===` are never touched, and a specifier with more or fewer than exactly one lower-bound clause is skipped entirely. This conservatism mirrors uv's `--upgrade` and is deliberate
+- **Compound specifiers keep their cap.** `upgradable_specifier` splits off a residual `SpecifierSet` (the `<2.0`, the `!=`s) that every candidate version must still satisfy
+- **`_replace_version` is a token swap, not a re-serialization.** It partitions on `;` to protect markers, then does a single `str.replace` from the operator onward. Do not "improve" this into a `str(Requirement)` round-trip - that would normalize the author's formatting, which is exactly what the tool promises not to do
+- **Settings precedence is CLI > `[tool.uv-upsync]` > defaults**, implemented in `cli` as `flag = flag or settings.flag`. This means a falsy CLI value cannot override a truthy config value, which is intended for the flag-shaped options
+- **The lock strategy has three modes.** The full upgrade set is tried first. On failure: `--strict` restores the deep-copied `backup` document and exits 2; the default best-effort mode re-locks incrementally to keep the maximal subset that resolves; `--resolve` additionally binary-searches `eligible_versions` for the highest version of a failing package that does lock. `_apply_with_lock` always rewrites the accepted set at the end, because the last trial may have left a failing candidate on disk
+- **Exit codes:** `0` success, `1` from `--check` when upgrades exist, `2` (`ERROR_EXIT_CODE`) for any error. `main()` catches everything and renders uv-style `error:` lines instead of tracebacks, re-raising the traceback only under `--verbose`
+- **Non-text `--format` implies quiet.** `logger.configure(quiet=quiet or output_format != "text", ...)` keeps stdout parseable
+
+## Architecture
+
+Single flow, no plugin system, no async. `__main__.py` is the orchestrator and everything else is a leaf module it calls.
+
+```
+__main__.cli
+  -> config.load_config      read [tool.uv-upsync] defaults
+  -> parsers.iter_dependency_groups   locate the live tomlkit arrays
+  -> pypi.PyPIClient.fetch_many       concurrent PEP 691 lookups
+  -> parsers.plan_updates             compute the bumps (pure, no mutation)
+  -> __main__._apply_with_lock        write + `uv lock`, with fallback strategies
+  -> report.render / logging.Logger   emit the summary
+```
+
+The module boundaries that carry a rule (the rest is `ls src/uv_upsync/`):
+
+- `__main__.py` owns the entire click command surface - every flag is declared there - plus the write/lock/rollback orchestration
+- `parsers.py` owns all TOML and specifier logic: group iteration, requirement parsing, eligibility, bump policy, surgical rewrite, conflict extraction from uv's stderr
+- `report.py` is JSON and Markdown renderers only - text output belongs to `logging.Logger`, not to this module
+
+## Commands
+
+`just --list` and `CONTRIBUTING.md` carry the recipe table; CI runs the same recipes, so a green `just check` locally means a green CI. Two things the table does not say:
+
+- `just format` and `just lint` invoke ruff and ty via `uvx`, not from the project venv, so they resolve the latest release rather than the pinned one in `[dependency-groups]`. Version skew between the two is expected and occasionally shows up as new lint findings
+- `just update` runs `uvx uv-upsync` against this repo - the tool eats its own dogfood here
+
+Run the CLI itself with `uv run uv-upsync ...` (entry point `uv_upsync.__main__:main`).
+
+## Conventions
+
+- Module docstrings follow the house phrasing `"""Module that contains ..."""`. Docstrings take sentence punctuation; code comments never end with a period
+- **Tests mirror modules one-to-one** - `tests/test_<module>.py`. Mocking is `pytest-mock`'s `mocker` fixture, never `unittest.mock` directly. `conftest.py` resets `Logger._instance` between tests via an autouse fixture, because the logger is a process-wide singleton
+- Everything else - ruff select and ignores, import style, line length, pytest `addopts` - lives in `pyproject.toml` and is enforced by `just lint`. Add a targeted `# noqa: RULE` at the site (as `__main__.cli` does) rather than widening the global ignores
+
+## Release
+
+Fully automated - **do not bump the version in `pyproject.toml` by hand.** The `Release` workflow is `workflow_dispatch` only; git-cliff derives the next version from the commit history (or takes the `version` input), `uv version` writes it, `CHANGELOG.md` is regenerated, the tag is pushed, and PyPI publication goes through trusted publishing.
+
+This makes **Conventional Commits load-bearing**: `cliff.toml` sets `filter_unconventional = true`, so a commit that doesn't match a known prefix is dropped from the changelog entirely, and `features_always_bump_minor` / `breaking_always_bump_major` decide the version. Use `<type>(<scope>): <subject>` with scopes like `parsers`, `pypi`, `config`, `cli`. `CONTRIBUTING.md` has the full prefix table, the branch pattern and the CI/CD workflow table.
+
+`AGENTS.md` is a symlink to this file - edit `CLAUDE.md`, never the symlink.

{uv_upsync-2.4.1 → uv_upsync-2.4.2}/CODE_OF_CONDUCT.md

@@ -1,5 +1,18 @@
 # Contributor Covenant Code of Conduct
 
+- [Contributor Covenant Code of Conduct](#contributor-covenant-code-of-conduct)
+  - [Our Pledge](#our-pledge)
+  - [Our Standards](#our-standards)
+  - [Enforcement Responsibilities](#enforcement-responsibilities)
+  - [Scope](#scope)
+  - [Enforcement](#enforcement)
+  - [Enforcement Guidelines](#enforcement-guidelines)
+    - [Correction](#correction)
+    - [Warning](#warning)
+    - [Temporary Ban](#temporary-ban)
+    - [Permanent Ban](#permanent-ban)
+  - [Attribution](#attribution)
+
 ## Our Pledge
 
 We as members, contributors, and leaders pledge to make participation in our community a

{uv_upsync-2.4.1 → uv_upsync-2.4.2}/CONTRIBUTING.md

@@ -1,8 +1,20 @@
 # Contributing
 
+- [Contributing](#contributing)
+  - [Reporting Bugs](#reporting-bugs)
+    - [How to Submit a Bug Report](#how-to-submit-a-bug-report)
+  - [Suggesting Enhancements](#suggesting-enhancements)
+    - [How to Submit an Enhancement](#how-to-submit-an-enhancement)
+  - [Code Contributions](#code-contributions)
+    - [Local Development](#local-development)
+    - [CI/CD](#cicd)
+    - [Branches](#branches)
+    - [Commits](#commits)
+    - [Pull Requests](#pull-requests)
+
 Thank you for taking the time to contribute.
 
-These guidelines are intended to make contributions consistent and easy to review across repositories. They are guidance, not hard rules, and maintainers may adapt them when needed.
+These guidelines are intended to make contributions consistent and easy to review across repositories. They are guidance, not hard instructions, and maintainers may adapt them when needed.
 
 ## Reporting Bugs
 
@@ -13,9 +25,9 @@ When opening a bug report, include enough context for someone else to reproduce
 > [!NOTE]
 > If you find a closed issue that looks similar, open a new issue and link the previous one.
 
-### How To Submit a Bug Report
+### How to Submit a Bug Report
 
-Use the bug issue template and provide the following:
+Open a bug report and provide the following:
 
 - A clear, descriptive title
 - Reproduction steps (minimal and reliable if possible)
@@ -32,9 +44,9 @@ Before submitting an enhancement, check whether a similar request already exists
 
 Enhancement requests can include new features, changes to existing behavior, usability improvements, or performance improvements.
 
-### How To Submit an Enhancement
+### How to Submit an Enhancement
 
-Use the feature request template and provide the following:
+Open a feature request and provide the following:
 
 - A clear problem statement
 - The proposed solution
@@ -47,15 +59,37 @@ Concrete examples, API sketches, UI mockups, or references are helpful when rele
 
 ### Local Development
 
-1. Fork the repository and create a branch for your change.
-2. Set up the project using the repository's README or development docs.
-3. Run the project's tests and quality checks locally before opening a pull request.
+This repo needs [uv](https://docs.astral.sh/uv), which manages Python 3.14 for you, and `just`.
+
+This project uses [`just`](https://github.com/casey/just) as its task runner. Run `just --list` for the full set; these are the ones you need day to day:
 
-When a repository includes helper scripts or task runners, prefer using those documented commands.
+| Command        | What it does                                                                                                                         |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `just install` | Installs every dependency group and extra into the project virtualenv                                                                |
+| `just format`  | Rewrites the sources in place: modernizes syntax to Python 3.10+ with pyupgrade, then applies ruff's safe fixes and formatting       |
+| `just lint`    | Lints the project with ruff and type-checks it with ty, without changing any file                                                    |
+| `just test`    | Runs the test suite, skipped when the `.no-tests` sentinel is present                                                                |
+| `just check`   | Runs `lint` then `test` in sequence                                                                                                  |
+| `just update`  | Refreshes the lockfile to the latest resolvable versions, then raises the dependency lower bounds in `pyproject.toml` with uv-upsync |
+
+1. Fork the repository and clone your fork locally
+2. Create a branch using the naming pattern described below
+3. Make your changes, then run `just check` before opening a pull request
 
 > [!IMPORTANT]
 > Behavioral code changes should include or update tests.
 
+### CI/CD
+
+Workflows live in `.github/workflows`:
+
+| Workflow | Trigger | What it does |
+| --- | --- | --- |
+| CI | Push to `main`, pull requests, `workflow_dispatch` | Single `ci` job on `ubuntu-24.04-arm`; installs `just` and uv pinned to Python 3.14, installs the project dependencies, then lints, type-checks and tests the project |
+| Release | `workflow_dispatch` (optional `version` input) | Three chained jobs on `ubuntu-24.04-arm`: `tag` takes the version from the `version` input or derives the next one from the commit history with git-cliff, bumps the project version, regenerates `CHANGELOG.md` and pushes the release commit and its tag to `main`; `release` (needs `tag`) publishes the GitHub Release with the generated notes; `publish` (needs `tag` and `release`) builds the package and uploads it to PyPI via trusted publishing |
+
+CI must be green before a pull request is merged.
+
 ### Branches
 
 Branch names follow the pattern `<type>/<short-description>` using the same type prefixes as commits.
@@ -70,7 +104,7 @@ docs/update-sync-flow-diagram
 refactor/mcps-schema-alignment
 ```
 
-A branch covering multiple unrelated changes should be split — one concern per branch makes review and bisect much easier.
+A branch covering multiple unrelated changes should be split. One concern per branch makes review and bisect much easier.
 
 ### Commits
 
@@ -86,10 +120,10 @@ This project follows [Conventional Commits](https://www.conventionalcommits.org/
 [optional body]
 ```
 
-- **type** — one of the prefixes from the table below
-- **scope** — the module, command, or area being changed (e.g. `sync`, `mcps`, `github`, `landing`, `config`); omit when the change is truly cross-cutting
-- **subject** — imperative mood, lowercase, no trailing period, 72 characters or fewer
-- **body** — optional; use it to explain *why*, not *what*; wrap at 72 characters
+- **type** - one of the prefixes from the table below
+- **scope** - the module, command, or area being changed (e.g. `sync`, `mcps`, `github`, `landing`, `config`); omit when the change is truly cross-cutting
+- **subject** - imperative mood, lowercase, no trailing period, 72 characters or fewer
+- **body** - optional; use it to explain _why_, not _what_; wrap at 72 characters
 
 **Type prefixes**
 

{uv_upsync-2.4.1 → uv_upsync-2.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: uv-upsync
-Version: 2.4.1
+Version: 2.4.2
 Summary: uv-upsync - is a tool for automated dependency updates and version bumping in pyproject.toml.
 Project-URL: Homepage, https://github.com/pivoshenko/uv-upsync
 Project-URL: Repository, https://github.com/pivoshenko/uv-upsync
@@ -22,19 +22,21 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Scientific/Engineering
 Classifier: Topic :: Software Development
 Classifier: Topic :: Software Development :: Libraries
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: >=3.10
-Requires-Dist: click~=8.4.1
+Requires-Dist: click~=8.5.0
 Requires-Dist: httpx~=0.28.1
-Requires-Dist: packaging~=26.2
-Requires-Dist: tomlkit~=0.15.0
+Requires-Dist: packaging~=26.3
+Requires-Dist: tomlkit~=0.15.1
+Requires-Dist: typing-extensions~=4.16.0
 Description-Content-Type: text/markdown
 
 <h1 align="left">
-  <img src="assets/logo.svg" alt="" height="40" align="left" style="vertical-align: middle; margin-right: 12px;">
+  <img src="https://raw.githubusercontent.com/pivoshenko/uv-upsync/main/assets/logo.svg" alt="" height="40" align="left" style="vertical-align: middle; margin-right: 12px;">
   uv-upsync
 </h1>
 
@@ -60,26 +62,26 @@ Description-Content-Type: text/markdown
 
 `uv-upsync` is a [uv]-native tool for automated dependency updates and version bumping in `pyproject.toml`.
 
-`uv lock --upgrade` refreshes your **lockfile** but leaves the lower bounds in `pyproject.toml` untouched, so `httpx>=0.24.0` stays `>=0.24.0` forever. `uv-upsync` raises those human-authored bounds to the latest published version, re-locks with `uv`, and rolls back if the resolution fails — all while preserving your formatting, comments, operators, extras and environment markers.
+`uv lock --upgrade` refreshes your **lockfile** but leaves the lower bounds in `pyproject.toml` untouched, so `httpx>=0.24.0` stays `>=0.24.0` forever. `uv-upsync` raises those human-authored bounds to the latest published version, re-locks with `uv`, and rolls back if the resolution fails. Your formatting, comments, operators, extras and environment markers are preserved.
 
 [uv]: https://github.com/astral-sh/uv
 
 ### Features
 
-- **Built for the uv ecosystem** — familiar flags (`--project`, `--upgrade-package`, `--all-groups`, `--offline`, `--no-cache`, `--color`), uv-style output and a `uv lock` round-trip with automatic rollback on failure
-- **Index-aware** — resolves versions from the [PEP 691] index configured for your project via `[[tool.uv.index]]`, so private indexes work out of the box
-- **Correct by construction** — specifiers are parsed with [`packaging`], the canonical PEP 440/508 implementation, not regular expressions
-- **Conservative** — only raises lower bounds (`>=`, `>`, `~=`); pinned (`==`) requirements are never touched
-- **Range-aware** — compound specifiers like `>=1.2,<2.0` have their floor raised to the latest version that still satisfies the cap (`<2.0`) and any exclusions (`!=`)
-- **Controlled** — `--max-bump patch|minor|major` holds back larger jumps (auto-apply minors, review majors), and `--prerelease` opts into pre-release versions
-- **Format-preserving** — only the version token is rewritten; everything else, including comments and markers, is kept verbatim
-- **Fast** — version lookups are fetched concurrently and cached
-- **Selective** — target specific groups or packages, or exclude packages
-- **Configurable** — persist defaults in a `[tool.uv-upsync]` table, overridable per run
-- **Resilient** — by default an upgrade that does not resolve is held back individually instead of failing the whole run (`--strict` to opt out)
-- **Safe** — `--dry-run` to preview and `--check` for CI
-- **Scriptable** — `--format json` for tooling and `--format markdown` for pull request bodies
-- **Integrated** — ships a [pre-commit] hook and a GitHub Action
+- Familiar uv flags (`--project`, `--upgrade-package`, `--all-groups`, `--offline`, `--no-cache`, `--color`), uv-style output and a `uv lock` round-trip with automatic rollback on failure
+- Versions are resolved from the [PEP 691] index configured for your project via `[[tool.uv.index]]`, so private indexes work out of the box
+- Specifiers are parsed with [`packaging`], the canonical PEP 440/508 implementation, not regular expressions
+- Only lower bounds (`>=`, `>`, `~=`) are raised; pinned (`==`) requirements are never touched
+- Compound specifiers like `>=1.2,<2.0` have their floor raised to the latest version that still satisfies the cap (`<2.0`) and any exclusions (`!=`)
+- `--max-bump patch|minor|major` holds back larger jumps (auto-apply minors, review majors), and `--prerelease` opts into pre-release versions
+- Only the version token is rewritten; everything else, including comments and markers, is kept verbatim
+- Version lookups are fetched concurrently and cached
+- Target specific groups or packages, or exclude packages
+- Defaults live in a `[tool.uv-upsync]` table and can be overridden per run
+- By default an upgrade that does not resolve is held back individually instead of failing the whole run (`--strict` to opt out)
+- `--dry-run` previews the changes, `--check` gates CI
+- `--format json` for tooling, `--format markdown` for pull request bodies
+- Ships a [pre-commit] hook and a GitHub Action
 
 ## Installation
 
@@ -148,7 +150,7 @@ Audited 12 dependencies, all up to date
 
 ### Resolution
 
-After bumping the specifiers, `uv-upsync` re-locks with `uv`. If the combined upgrade does not resolve, the default **best-effort** mode keeps the largest subset of upgrades that locks and reports which ones were held back (naming the conflicting dependency when it can) — so a single incompatible dependency never costs you the rest:
+After bumping the specifiers, `uv-upsync` re-locks with `uv`. If the combined upgrade does not resolve, the default **best-effort** mode keeps the largest subset of upgrades that locks and reports which ones were held back, naming the conflicting dependency when it can. A single incompatible dependency never costs you the rest:
 
 ```console
 $ uv-upsync
@@ -191,25 +193,25 @@ Settings are resolved with the precedence **command line > `[tool.uv-upsync]` >
 
 ## Examples
 
-### Preview the upgrades
+### Preview the Upgrades
 
 ```shell
 uv-upsync --dry-run
 ```
 
-### Upgrade a single package
+### Upgrade a Single Package
 
 ```shell
 uv-upsync --upgrade-package httpx
 ```
 
-### Exclude packages
+### Exclude Packages
 
 ```shell
 uv-upsync --exclude click --exclude ruff
 ```
 
-### Upgrade specific groups
+### Upgrade Specific Groups
 
 ```shell
 # Only the project dependencies
@@ -219,7 +221,7 @@ uv-upsync --group project
 uv-upsync --group test --group docs
 ```
 
-### Fail CI when dependencies are stale
+### Fail CI When Dependencies Are Stale
 
 ```shell
 uv-upsync --check
@@ -241,8 +243,8 @@ repos:
 
 Two hooks are available:
 
-- **`uv-upsync`** — upgrade the bounds in `pyproject.toml` and re-lock (runs `uv lock`, so `uv` must be on your `PATH`)
-- **`uv-upsync-check`** — fail the commit if any dependency can be upgraded, without writing changes
+- `uv-upsync` upgrades the bounds in `pyproject.toml` and re-locks (runs `uv lock`, so `uv` must be on your `PATH`)
+- `uv-upsync-check` fails the commit if any dependency can be upgraded, without writing changes
 
 ## GitHub Action
 
@@ -272,7 +274,7 @@ jobs:
           branch: build/uv-upsync
 ```
 
-With `--format markdown` the action's `summary` output is a ready-made pull request body (`⬆️ click 8.1.8 → 8.2.1 …`). To gate pull requests instead, run the action with `args: --check` and drop the pull request step.
+With `--format markdown` the action's `summary` output is a ready-made pull request body (`⬆️ click 8.1.8 → 8.2.1 ...`). To gate pull requests instead, run the action with `args: --check` and drop the pull request step.
 
 | Input               | Description                                | Default |
 | ------------------- | ------------------------------------------ | ------- |