divekit plugin pin

Synopsis

Pin one plugin to a Git reference (branch, tag, or commit), or pin a plugin of a plugin suite to a version.

A suite plugin is named by its runtime identity <suite>/<plugin>. Its pin is one of: an exact version (1.2.1), patch updates (~1.2 or ~1.2.1), or updates within a major version (^1 or ^1.2.1). The pin replaces the pin of the suite manifest for this origin. The locked version only moves when it no longer matches the pin; ‘divekit plugin update’ picks up newer releases that the pin allows. Use –clear to follow the suite manifest again.

Usage

divekit plugin pin <plugin> <ref> [flags]

Examples

# Pin a flat plugin to a tag
divekit plugin pin pmd v0.3.4

# Pin a suite plugin to exactly one version
divekit plugin pin maven/pmd 1.2.1

# Accept bug fixes only, or any compatible release
divekit plugin pin maven/pmd ~1.2
divekit plugin pin maven/pmd ^1

# Follow the suite manifest again
divekit plugin pin maven/pmd --clear

Flags

--clear   Remove the pin set on a suite plugin and follow the suite manifest again

Inherited Flags

-d, --distribution string   Target distribution override (default: project-level eval overrides and .divekit state)
  -l, --loglevel string       log level (debug, info, warn, error, fatal) (default "info")
      --no-index              skip project index update
      --non-interactive       run in non-interactive mode (fails if interactive input is required)
  -y, --yes                   assume yes/default for all prompts (non-interactive with automatic defaults)

Parent Command

• divekit plugin