OS Manuals

/usr/bin/bumpconstraints

Testing tools

From tw 0.0.58-r0 (os), captured 2026-11-05 by running bumpconstraints --help (exit 0). permalink

Update Python package versions in a constraints file.

Package specifications should be in the format: package==version # comment
Comments (starting with #) are optional but recommended for documenting why versions are being bumped.

Package updates can be provided as arguments or read from a file using -u/--updates-file.

Examples:
  tw bumpconstraints "requests==2.31.0 # Security update CVE-2023-XXXXX"
  tw bumpconstraints -c requirements.txt "django==4.2.0 # LTS version"
  tw bumpconstraints -u updates.txt -c constraints.txt
  tw bumpconstraints --only-replace=false "newpackage==1.0.0 # Adding new dependency"

Usage:
  bumpconstraints [PACKAGE==VERSION ...] [flags]

Flags:
  -c, --constraints-file string   Path to the constraints file to update (default "constraints.txt")
  -h, --help                      help for bumpconstraints
      --only-replace              Only update packages already in the constraints file (default true)
  -u, --updates-file string       Path to file containing package updates (one per line)
Options (4)
OptionDescriptionSource
-c, --constraints-file stringPath to the constraints file to update (default "constraints.txt")help
-h, --helphelp for bumpconstraintshelp
--only-replaceOnly update packages already in the constraints file (default true)help
-u, --updates-file stringPath to file containing package updates (one per line)help

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.