hubcio opened a new pull request, #3467:
URL: https://github.com/apache/iggy/pull/3467

   Per-directory major/range updates multiply review load and, for
   the Python projects, are broken by construction: the three
   directories share apache-iggy via a path dependency, so each
   uv.lock embeds the SDK's requirement metadata, and a per-directory
   update ships the sibling lockfile rewrite without the manifest
   change it was derived from - it can never pass the lockfile check
   (#3451, #3450). Collapse every entry's grouping to a single
   all-update-types group so each component (SDK impl plus its
   bdd/examples directories) opens at most one version-update PR per
   cycle, keeping manifest and lockfile edits for the same dependency
   in one coherent PR. Security updates bypass groups and stay
   separate.
   
   Also ignore Python base images in the docker entry: the
   interpreter version is pinned and synced by
   sync-python-interpreter-version.sh, so a lone image bump would
   fail the sync check.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to