Skip to main content

Module adapters

Module adapters 

Source
Expand description

Ecosystem adapters behind one batch-oriented interface.

Each adapter owns discovery, version grouping, edit planning, compatibility checks, and publication for its release targets. Adapters partitions units by target kind and is the only place that branches on it.

Re-exportsยง

pub use self::cargo::CargoRegistry;
pub use self::npm::NpmRegistry;
pub use self::registry::RegistryError;

Modulesยง

cargo ๐Ÿ”’
Cargo workspace discovery, version groups, and manifest/dependency planning.
changelog ๐Ÿ”’
Changelog transformation shared by the ecosystem adapters.
document ๐Ÿ”’
Versions at a key path inside a TOML, YAML, or JSON document.
holder ๐Ÿ”’
Release units whose version lives in a file of their own or at a key path inside a document: discovery, planning, and transactional application without any package registry.
npm ๐Ÿ”’
npm package lookup and publication.
pins ๐Ÿ”’
Versions of dependencies written into files of the depending unit.
registry ๐Ÿ”’
HTTP requests shared by the package registries.
utf8 ๐Ÿ”’
Decoding of file bytes shared by the adapters.
version_file ๐Ÿ”’
Plain files that hold nothing but a semantic version.

Structsยง

Adapters ๐Ÿ”’
Every supported ecosystem adapter, dispatching units by target kind.
EditContext ๐Ÿ”’
What edit planning needs beyond the units and their versions.
LocalChange
One unit changed by a local release plan.
LocalPlan
A validated local plan for any configured release target.
NoRegistry ๐Ÿ”’
Registry stand-in that is no PackageRegistry, so adapters built with it cannot publish.
Placed ๐Ÿ”’
A unit with the place its ecosystem reads the version from: a Cargo manifest path or a version holder.

Enumsยง

ResolveError ๐Ÿ”’
A unit cannot be resolved, versioned, or planned.

Type Aliasesยง

Configured ๐Ÿ”’
A configured unit that is not resolved yet.
HolderUnit ๐Ÿ”’
A resolved unit that keeps its version in a file or document.