Enum PublishConfig 

pub enum PublishConfig {
    Cargo {
        features: Vec<String>,
        registry: Option<String>,
        workspace: bool,
    },
    Npm {
        registry: Option<String>,
        access: Option<String>,
        workspace: bool,
    },
    Docker {
        image: String,
        platforms: Vec<String>,
        dockerfile: Option<String>,
    },
    Pypi {
        repository: Option<String>,
        workspace: bool,
    },
    Go,
    Custom {
        command: String,
        check: Option<String>,
        cwd: Option<String>,
    },
}

Per-package publish configuration. Typed enum — the user picks a known publisher (cargo, npm, docker, pypi, go) and sr handles both the “is it already published?” check (registry API call) and the actual publish command (shelled out). The custom variant is the escape hatch for arbitrary shell commands + a user-supplied state check.

Deserializes as an internally-tagged enum: { type: <publisher>, ... }.

Variants

Cargo

cargo publish to crates.io (or a custom registry).

Fields

features: Vec<String>

Feature flags forwarded to cargo publish --features ....

registry: Option<String>

Cargo registry name (defined in ~/.cargo/config.toml). None = default registry (crates.io).

workspace: bool

When true, publish every [workspace].members crate, not just the one at path. Check aggregates across members (completed iff every member is already on the registry).

Npm

npm publish to registry.npmjs.org (or a custom registry). Auto-detects pnpm / yarn / npm from lockfiles at path.

Fields

registry: Option<String>

Registry URL. None = default (https://registry.npmjs.org/).

access: Option<String>

Access level for scoped packages: “public” or “restricted”.

workspace: bool

When true, publish every workspace member (from package.json workspaces or pnpm-workspace.yaml). Uses the tool’s native recursive publish where available.

Docker

Push a container image to a registry using docker buildx build --push.

Fields

image: String

Fully-qualified image name (e.g. ghcr.io/owner/repo).

platforms: Vec<String>

Target platforms for buildx (e.g. ["linux/amd64", "linux/arm64"]). When empty, buildx picks the default.

dockerfile: Option<String>

Path to Dockerfile relative to the package dir. Default: Dockerfile.

Pypi

Publish to PyPI via twine upload or uv publish (auto-detected).

Fields

repository: Option<String>

Repository name (matches [tool.twine.repository] or env).

workspace: bool

When true, publish every uv workspace member ([tool.uv.workspace].members). Check aggregates across members.

Go

Go modules publish by git-tag; sr already cuts the tag, so this is effectively a noop documenting the package’s presence in the manifest.

Custom

Arbitrary publish command with a user-supplied state check. The only place sr shells out for a user-provided command; limited to registries that don’t have a built-in publisher.

Fields

command: String

Shell command that performs the publish.

check: Option<String>

Shell command that returns exit 0 iff the package is already published at the current version. Optional — when absent, the publisher always runs.

cwd: Option<String>

Working directory. Defaults to the package path.

Trait Implementations

impl Clone for PublishConfig

fn clone(&self) -> PublishConfig

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for PublishConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for PublishConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for PublishConfig

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.