jx step next-version

jx step next-version

Writes next semantic version

Synopsis

This pipeline step command works out a semantic version, writes a file ./VERSION and optionally updates a file

jx step next-version [flags]

Examples

  jx step next-version
  jx step next-version --filename package.json
  jx step next-version --filename package.json --tag
  jx step next-version --filename package.json --tag --version 1.2.3
  
  # lets use git to create a new version from a tag and tag git
  jx step next-version --use-git-tag-only --tag

Options

      --charts-dir string   the directory of the chart to update the version (in conjunction with --tag)
  -d, --dir string          the directory to look for files that contain a pom.xml or Makefile with the project version to bump
  -f, --filename string     Filename that contains version property to update, e.g. package.json
  -h, --help                help for next-version
      --semantic-release    use conventional commits to determine next version. Ignores the --use-git-tag-only and --version options See https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines
  -t, --tag                 tag and push new version
      --use-git-tag-only    only use a git tag so work out new semantic version, else specify filename [pom.xml,package.json,Makefile,Chart.yaml]
      --version string      optional version to use rather than generating a new one

Options inherited from parent commands

  -b, --batch-mode   Runs in batch mode without prompting for user input
      --verbose      Enables verbose output. The environment variable JX_LOG_LEVEL has precedence over this flag and allows setting the logging level to any value of: panic, fatal, error, warn, info, debug, trace

SEE ALSO

• jx step - pipeline steps

Auto generated by spf13/cobra on 2-Sep-2020

Feedback

Was this page helpful?

Yes No

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.