sentry-cli 3.1.0__tar.gz → 3.2.0__tar.gz

{sentry_cli-3.1.0 → sentry_cli-3.2.0}/Cargo.lock

@@ -332,9 +332,9 @@ checksum = "1fd0f2584146f6f2ef48085050886acf353beff7305ebd1ae69500e27c67f64b"
 
 [[package]]
 name = "bytes"
-version = "1.10.1"
+version = "1.11.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "d71b6127be86fdcfddb610f7182ac57211d4b18a3e9c82eb2d17662f2227ad6a"
+checksum = "1e748733b7cbc798e1434b6ac524f0c1ff2ab456fe201501e6497c8417a4fc33"
 
 [[package]]
 name = "bzip2"
@@ -1054,9 +1054,9 @@ dependencies = [
 
 [[package]]
 name = "git2"
-version = "0.18.3"
+version = "0.20.4"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "232e6a7bfe35766bf715e55a88b39a700596c0ccfd88cd3680b4cdb40d66ef70"
+checksum = "7b88256088d75a56f8ecfa070513a775dd9107f6530ef14919dac831af9cfe2b"
 dependencies = [
  "bitflags 2.9.4",
  "libc",
@@ -1617,9 +1617,9 @@ checksum = "58f929b4d672ea937a23a1ab494143d968337a5f47e56d0815df1e0890ddf174"
 
 [[package]]
 name = "libgit2-sys"
-version = "0.16.2+1.7.2"
+version = "0.18.3+1.9.2"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "ee4126d8b4ee5c9d9ea891dd875cfdc1e9d0950437179104b183d7d8a74d24e8"
+checksum = "c9b3acc4b91781bb0b3386669d325163746af5f6e4f73e6d2d630e09a35f3487"
 dependencies = [
  "cc",
  "libc",
@@ -1844,9 +1844,9 @@ checksum = "61807f77802ff30975e01f4f071c8ba10c022052f98b3294119f3e615d13e5be"
 
 [[package]]
 name = "num-conv"
-version = "0.1.0"
+version = "0.2.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "51d515d32fb182ee37cda2ccdcb92950d6a3c2893aa280e540671c2cd0f3b1d9"
+checksum = "cf97ec579c3c42f953ef76dbf8d55ac91fb219dde70e49aa4a6b7d74e9919050"
 
 [[package]]
 name = "num-traits"
@@ -2668,7 +2668,7 @@ dependencies = [
 
 [[package]]
 name = "sentry-cli"
-version = "3.1.0"
+version = "3.2.0"
 dependencies = [
  "anyhow",
  "anylog",
@@ -3237,30 +3237,30 @@ dependencies = [
 
 [[package]]
 name = "time"
-version = "0.3.44"
+version = "0.3.47"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "91e7d9e3bb61134e77bde20dd4825b97c010155709965fedf0f49bb138e52a9d"
+checksum = "743bd48c283afc0388f9b8827b976905fb217ad9e647fae3a379a9283c4def2c"
 dependencies = [
  "deranged",
  "itoa",
  "num-conv",
  "powerfmt",
- "serde",
+ "serde_core",
  "time-core",
  "time-macros",
 ]
 
 [[package]]
 name = "time-core"
-version = "0.1.6"
+version = "0.1.8"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "40868e7c1d2f0b8d73e4a8c7f0ff63af4f6d19be117e90bd73eb1d62cf831c6b"
+checksum = "7694e1cfe791f8d31026952abf09c69ca6f6fa4e1a1229e18988f06a04a12dca"
 
 [[package]]
 name = "time-macros"
-version = "0.2.24"
+version = "0.2.27"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "30cfb0125f12d9c277f35663a0a33f8c30190f4e4574868a330595412d34ebf3"
+checksum = "2e70e4c5a0e0a8a4823ad65dfe1a6930e4f4d756dcd9dd7939022b5e8c501215"
 dependencies = [
  "num-conv",
  "time-core",

{sentry_cli-3.1.0 → sentry_cli-3.2.0}/Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 build = "build.rs"
 name = "sentry-cli"
-version = "3.1.0"
+version = "3.2.0"
 edition = "2021"
 rust-version = "1.91"
 
@@ -31,7 +31,7 @@ elementtree = "1.2.3"
 flate2 = { version = "1.0.25", default-features = false, features = [
   "rust_backend",
 ] }
-git2 = { version = "0.18.1", default-features = false }
+git2 = { version = "0.20.4", default-features = false }
 glob = "0.3.1"
 if_chain = "1.0.2"
 ignore = "0.4.20"

{sentry_cli-3.1.0 → sentry_cli-3.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sentry_cli
-Version: 3.1.0
+Version: 3.2.0
 Summary: A command line utility to work with Sentry.
 Home-page: https://github.com/getsentry/sentry-cli
 Author: Sentry
@@ -79,3 +79,7 @@ Also, there is a Dockerfile that builds an Alpine-based Docker image with
 docker build -t sentry-cli .
 docker run --rm -v $(pwd):/work sentry-cli --help
 ```
+
+## Internal docs
+
+Snapshot: [Sentry CLI distribution as of 2026-01-29](docs/snapshots/2026-01-29-sentry-cli-distribution.md).

{sentry_cli-3.1.0 → sentry_cli-3.2.0}/README.md

@@ -62,3 +62,7 @@ Also, there is a Dockerfile that builds an Alpine-based Docker image with
 docker build -t sentry-cli .
 docker run --rm -v $(pwd):/work sentry-cli --help
 ```
+
+## Internal docs
+
+Snapshot: [Sentry CLI distribution as of 2026-01-29](docs/snapshots/2026-01-29-sentry-cli-distribution.md).

sentry_cli-3.2.0/apple-catalog-parsing/AGENTS.md

@@ -0,0 +1,99 @@
+# Rust Development Guidelines
+
+## Code Organization
+
+- Follow existing module structure in `src/commands/` for new commands
+- Use `anyhow::Result` for error handling patterns
+- Consider cross-platform compatibility
+- Ensure backward compatibility for CLI interface
+
+## Common Patterns
+
+- Use existing error types and handling patterns
+- Follow established CLI argument parsing patterns using `clap`
+- Reuse utility functions from `src/utils/`
+- Match existing code style and naming conventions
+- Add appropriate logging using `log` crate patterns
+
+## Type Annotations and Inference
+
+- Prefer compiler type inference across the codebase
+- Do not add explicit type annotations in `let` bindings or turbofish syntax (e.g., `::<T>`) unless required for the code to compile or to disambiguate an API that inference cannot resolve
+- If the code compiles without explicit annotations, omit them
+
+## Development Commands
+
+Always run `cargo fmt --all`, prior to committing any Rust code, to ensure consistent formatting and to avoid CI failures.
+
+Some other commands you may find useful:
+
+```bash
+# Essential Rust workflow - run against the whole workspace
+cargo build --workspace
+cargo test --workspace
+cargo clippy --workspace
+
+# Local testing
+cargo run -- --help
+```
+
+## Error Handling Patterns
+
+- Use `anyhow::Result` for application-level errors
+- Use `thiserror` for library-level error types (see `src/utils/auth_token/error.rs`)
+- Chain errors with `.context()` for better error messages
+- Custom error types in `src/api/errors/` and `src/utils/dif_upload/error.rs`
+
+## Swift/Apple Integration
+
+- Swift code in `apple-catalog-parsing/` is used for parsing xarchive files
+- Used by the `build upload` command for iOS app processing
+- Built as a separate crate with FFI bindings to Rust
+- Only compiled on macOS targets
+- Tests run via `swift-test.yml` workflow in CI
+
+# Rust Testing Guidelines
+
+## Unit Tests
+
+- Colocate with source code
+- Use `#[cfg(test)]` modules
+- Mock external dependencies
+
+## Integration Tests
+
+- Use `trycmd` for CLI interface testing when asserting output
+- Use `assert_cmd` for testing behavior rather than just output
+- Structure: `tests/integration/_cases/<command>/<test>.trycmd`
+- Fixtures: `tests/integration/_fixtures/`
+- Expected outputs: `tests/integration/_expected_outputs/`
+- API mocks: `tests/integration/_responses/`
+
+## Snapshot Management
+
+```bash
+# Update snapshots
+TRYCMD=overwrite cargo test
+
+# Debug test output
+TRYCMD=dump cargo test
+```
+
+## Test Utilities
+
+- `TestManager`: Sets up test environment with mock server
+- `MockEndpointBuilder`: Creates API endpoint mocks
+- `copy_recursively`: Helper for fixture setup
+- Environment setup via `test_utils::env`
+
+## Platform-Specific Testing
+
+- Use `#[cfg(windows)]` for Windows-specific tests
+- Separate `.trycmd` files when behavior differs
+- Test on CI matrix: Linux, macOS, Windows
+
+## Assert Command vs Trycmd
+
+- `trycmd`: Best for testing exact CLI output, supports snapshot testing
+- `assert_cmd`: Better for testing behavior, exit codes, and when you need programmatic assertions
+- Example of `assert_cmd` usage can be found in `TestManager::run_and_assert()`

sentry_cli-3.2.0/apple-catalog-parsing/CLAUDE.md

@@ -0,0 +1,99 @@
+# Rust Development Guidelines
+
+## Code Organization
+
+- Follow existing module structure in `src/commands/` for new commands
+- Use `anyhow::Result` for error handling patterns
+- Consider cross-platform compatibility
+- Ensure backward compatibility for CLI interface
+
+## Common Patterns
+
+- Use existing error types and handling patterns
+- Follow established CLI argument parsing patterns using `clap`
+- Reuse utility functions from `src/utils/`
+- Match existing code style and naming conventions
+- Add appropriate logging using `log` crate patterns
+
+## Type Annotations and Inference
+
+- Prefer compiler type inference across the codebase
+- Do not add explicit type annotations in `let` bindings or turbofish syntax (e.g., `::<T>`) unless required for the code to compile or to disambiguate an API that inference cannot resolve
+- If the code compiles without explicit annotations, omit them
+
+## Development Commands
+
+Always run `cargo fmt --all`, prior to committing any Rust code, to ensure consistent formatting and to avoid CI failures.
+
+Some other commands you may find useful:
+
+```bash
+# Essential Rust workflow - run against the whole workspace
+cargo build --workspace
+cargo test --workspace
+cargo clippy --workspace
+
+# Local testing
+cargo run -- --help
+```
+
+## Error Handling Patterns
+
+- Use `anyhow::Result` for application-level errors
+- Use `thiserror` for library-level error types (see `src/utils/auth_token/error.rs`)
+- Chain errors with `.context()` for better error messages
+- Custom error types in `src/api/errors/` and `src/utils/dif_upload/error.rs`
+
+## Swift/Apple Integration
+
+- Swift code in `apple-catalog-parsing/` is used for parsing xarchive files
+- Used by the `build upload` command for iOS app processing
+- Built as a separate crate with FFI bindings to Rust
+- Only compiled on macOS targets
+- Tests run via `swift-test.yml` workflow in CI
+
+# Rust Testing Guidelines
+
+## Unit Tests
+
+- Colocate with source code
+- Use `#[cfg(test)]` modules
+- Mock external dependencies
+
+## Integration Tests
+
+- Use `trycmd` for CLI interface testing when asserting output
+- Use `assert_cmd` for testing behavior rather than just output
+- Structure: `tests/integration/_cases/<command>/<test>.trycmd`
+- Fixtures: `tests/integration/_fixtures/`
+- Expected outputs: `tests/integration/_expected_outputs/`
+- API mocks: `tests/integration/_responses/`
+
+## Snapshot Management
+
+```bash
+# Update snapshots
+TRYCMD=overwrite cargo test
+
+# Debug test output
+TRYCMD=dump cargo test
+```
+
+## Test Utilities
+
+- `TestManager`: Sets up test environment with mock server
+- `MockEndpointBuilder`: Creates API endpoint mocks
+- `copy_recursively`: Helper for fixture setup
+- Environment setup via `test_utils::env`
+
+## Platform-Specific Testing
+
+- Use `#[cfg(windows)]` for Windows-specific tests
+- Separate `.trycmd` files when behavior differs
+- Test on CI matrix: Linux, macOS, Windows
+
+## Assert Command vs Trycmd
+
+- `trycmd`: Best for testing exact CLI output, supports snapshot testing
+- `assert_cmd`: Better for testing behavior, exit codes, and when you need programmatic assertions
+- Example of `assert_cmd` usage can be found in `TestManager::run_and_assert()`

{sentry_cli-3.1.0 → sentry_cli-3.2.0}/sentry_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sentry_cli
-Version: 3.1.0
+Version: 3.2.0
 Summary: A command line utility to work with Sentry.
 Home-page: https://github.com/getsentry/sentry-cli
 Author: Sentry
@@ -79,3 +79,7 @@ Also, there is a Dockerfile that builds an Alpine-based Docker image with
 docker build -t sentry-cli .
 docker run --rm -v $(pwd):/work sentry-cli --help
 ```
+
+## Internal docs
+
+Snapshot: [Sentry CLI distribution as of 2026-01-29](docs/snapshots/2026-01-29-sentry-cli-distribution.md).

{sentry_cli-3.1.0 → sentry_cli-3.2.0}/sentry_cli.egg-info/SOURCES.txt

@@ -7,6 +7,8 @@ build.rs
 pyproject.toml
 setup.cfg
 setup.py
+apple-catalog-parsing/AGENTS.md
+apple-catalog-parsing/CLAUDE.md
 apple-catalog-parsing/Cargo.toml
 apple-catalog-parsing/build.rs
 apple-catalog-parsing/native/swift/AssetCatalogParser/Package.swift
@@ -22,6 +24,8 @@ sentry_cli.egg-info/PKG-INFO
 sentry_cli.egg-info/SOURCES.txt
 sentry_cli.egg-info/dependency_links.txt
 sentry_cli.egg-info/top_level.txt
+src/AGENTS.md
+src/CLAUDE.md
 src/bashsupport.sh
 src/config.rs
 src/constants.rs

sentry_cli-3.2.0/src/AGENTS.md

@@ -0,0 +1,99 @@
+# Rust Development Guidelines
+
+## Code Organization
+
+- Follow existing module structure in `src/commands/` for new commands
+- Use `anyhow::Result` for error handling patterns
+- Consider cross-platform compatibility
+- Ensure backward compatibility for CLI interface
+
+## Common Patterns
+
+- Use existing error types and handling patterns
+- Follow established CLI argument parsing patterns using `clap`
+- Reuse utility functions from `src/utils/`
+- Match existing code style and naming conventions
+- Add appropriate logging using `log` crate patterns
+
+## Type Annotations and Inference
+
+- Prefer compiler type inference across the codebase
+- Do not add explicit type annotations in `let` bindings or turbofish syntax (e.g., `::<T>`) unless required for the code to compile or to disambiguate an API that inference cannot resolve
+- If the code compiles without explicit annotations, omit them
+
+## Development Commands
+
+Always run `cargo fmt --all`, prior to committing any Rust code, to ensure consistent formatting and to avoid CI failures.
+
+Some other commands you may find useful:
+
+```bash
+# Essential Rust workflow - run against the whole workspace
+cargo build --workspace
+cargo test --workspace
+cargo clippy --workspace
+
+# Local testing
+cargo run -- --help
+```
+
+## Error Handling Patterns
+
+- Use `anyhow::Result` for application-level errors
+- Use `thiserror` for library-level error types (see `src/utils/auth_token/error.rs`)
+- Chain errors with `.context()` for better error messages
+- Custom error types in `src/api/errors/` and `src/utils/dif_upload/error.rs`
+
+## Swift/Apple Integration
+
+- Swift code in `apple-catalog-parsing/` is used for parsing xarchive files
+- Used by the `build upload` command for iOS app processing
+- Built as a separate crate with FFI bindings to Rust
+- Only compiled on macOS targets
+- Tests run via `swift-test.yml` workflow in CI
+
+# Rust Testing Guidelines
+
+## Unit Tests
+
+- Colocate with source code
+- Use `#[cfg(test)]` modules
+- Mock external dependencies
+
+## Integration Tests
+
+- Use `trycmd` for CLI interface testing when asserting output
+- Use `assert_cmd` for testing behavior rather than just output
+- Structure: `tests/integration/_cases/<command>/<test>.trycmd`
+- Fixtures: `tests/integration/_fixtures/`
+- Expected outputs: `tests/integration/_expected_outputs/`
+- API mocks: `tests/integration/_responses/`
+
+## Snapshot Management
+
+```bash
+# Update snapshots
+TRYCMD=overwrite cargo test
+
+# Debug test output
+TRYCMD=dump cargo test
+```
+
+## Test Utilities
+
+- `TestManager`: Sets up test environment with mock server
+- `MockEndpointBuilder`: Creates API endpoint mocks
+- `copy_recursively`: Helper for fixture setup
+- Environment setup via `test_utils::env`
+
+## Platform-Specific Testing
+
+- Use `#[cfg(windows)]` for Windows-specific tests
+- Separate `.trycmd` files when behavior differs
+- Test on CI matrix: Linux, macOS, Windows
+
+## Assert Command vs Trycmd
+
+- `trycmd`: Best for testing exact CLI output, supports snapshot testing
+- `assert_cmd`: Better for testing behavior, exit codes, and when you need programmatic assertions
+- Example of `assert_cmd` usage can be found in `TestManager::run_and_assert()`

sentry_cli-3.2.0/src/CLAUDE.md

@@ -0,0 +1,99 @@
+# Rust Development Guidelines
+
+## Code Organization
+
+- Follow existing module structure in `src/commands/` for new commands
+- Use `anyhow::Result` for error handling patterns
+- Consider cross-platform compatibility
+- Ensure backward compatibility for CLI interface
+
+## Common Patterns
+
+- Use existing error types and handling patterns
+- Follow established CLI argument parsing patterns using `clap`
+- Reuse utility functions from `src/utils/`
+- Match existing code style and naming conventions
+- Add appropriate logging using `log` crate patterns
+
+## Type Annotations and Inference
+
+- Prefer compiler type inference across the codebase
+- Do not add explicit type annotations in `let` bindings or turbofish syntax (e.g., `::<T>`) unless required for the code to compile or to disambiguate an API that inference cannot resolve
+- If the code compiles without explicit annotations, omit them
+
+## Development Commands
+
+Always run `cargo fmt --all`, prior to committing any Rust code, to ensure consistent formatting and to avoid CI failures.
+
+Some other commands you may find useful:
+
+```bash
+# Essential Rust workflow - run against the whole workspace
+cargo build --workspace
+cargo test --workspace
+cargo clippy --workspace
+
+# Local testing
+cargo run -- --help
+```
+
+## Error Handling Patterns
+
+- Use `anyhow::Result` for application-level errors
+- Use `thiserror` for library-level error types (see `src/utils/auth_token/error.rs`)
+- Chain errors with `.context()` for better error messages
+- Custom error types in `src/api/errors/` and `src/utils/dif_upload/error.rs`
+
+## Swift/Apple Integration
+
+- Swift code in `apple-catalog-parsing/` is used for parsing xarchive files
+- Used by the `build upload` command for iOS app processing
+- Built as a separate crate with FFI bindings to Rust
+- Only compiled on macOS targets
+- Tests run via `swift-test.yml` workflow in CI
+
+# Rust Testing Guidelines
+
+## Unit Tests
+
+- Colocate with source code
+- Use `#[cfg(test)]` modules
+- Mock external dependencies
+
+## Integration Tests
+
+- Use `trycmd` for CLI interface testing when asserting output
+- Use `assert_cmd` for testing behavior rather than just output
+- Structure: `tests/integration/_cases/<command>/<test>.trycmd`
+- Fixtures: `tests/integration/_fixtures/`
+- Expected outputs: `tests/integration/_expected_outputs/`
+- API mocks: `tests/integration/_responses/`
+
+## Snapshot Management
+
+```bash
+# Update snapshots
+TRYCMD=overwrite cargo test
+
+# Debug test output
+TRYCMD=dump cargo test
+```
+
+## Test Utilities
+
+- `TestManager`: Sets up test environment with mock server
+- `MockEndpointBuilder`: Creates API endpoint mocks
+- `copy_recursively`: Helper for fixture setup
+- Environment setup via `test_utils::env`
+
+## Platform-Specific Testing
+
+- Use `#[cfg(windows)]` for Windows-specific tests
+- Separate `.trycmd` files when behavior differs
+- Test on CI matrix: Linux, macOS, Windows
+
+## Assert Command vs Trycmd
+
+- `trycmd`: Best for testing exact CLI output, supports snapshot testing
+- `assert_cmd`: Better for testing behavior, exit codes, and when you need programmatic assertions
+- Example of `assert_cmd` usage can be found in `TestManager::run_and_assert()`

{sentry_cli-3.1.0 → sentry_cli-3.2.0}/src/api/data_types/chunking/build.rs

@@ -13,6 +13,8 @@ pub struct ChunkedBuildRequest<'a> {
     pub build_configuration: Option<&'a str>,
     #[serde(skip_serializing_if = "Option::is_none")]
     pub release_notes: Option<&'a str>,
+    #[serde(skip_serializing_if = "<[_]>::is_empty")]
+    pub install_groups: &'a [String],
     #[serde(flatten)]
     pub vcs_info: &'a VcsInfo<'a>,
 }