Crate dependency_check_updates_core 

Core domain types and orchestration for dependency-check-updates.

Defines shared traits that each language crate implements:

• ManifestHandler — parse manifests and apply format-preserving updates
• RegistryClient — resolve versions from package registries
• Scanner — discover manifest files in a directory

Re-exports

pub use error::DcuError;

pub use http::DEFAULT_MAX_CONCURRENT_REQUESTS;

pub use http::DEFAULT_REQUEST_TIMEOUT_SECS;

pub use http::build_client;

pub use manifest::ManifestHandler;

pub use manifest::ParsedManifest;

pub use manifest::RegistryClient;

pub use manifest::ScanResult;

pub use manifest::Scanner;

pub use style::FileStyle;

pub use style::IndentStyle;

pub use style::LineEnding;

pub use types::BumpType;

pub use types::DependencySection;

pub use types::DependencySpec;

pub use types::ManifestKind;

pub use types::ManifestRef;

pub use types::PlannedUpdate;

pub use types::ResolvedVersion;

pub use types::TargetLevel;

pub use util::collect_task_results;

pub use util::strip_range_prefix;

pub use version::SelectableVersion;

pub use version::select_version;

Modules

error

The crate-wide error type DcuError returned by manifest, registry, and patch operations.

http

Shared HTTP client construction for the registry clients.

manifest

Shared manifest handling abstractions.

style

File formatting detection (indentation, line endings, trailing newline) used to preserve a manifest’s original style when rewriting it.

types

Core domain types shared across every ecosystem crate: manifest kinds, dependency sections, version targets, and the parsed/resolved/planned value objects that flow through the scan → resolve → patch pipeline.

util

Small cross-ecosystem helpers shared by the registry clients.

version

Generic, ecosystem-agnostic version selection.