DE

↑ ↓ select, Enter open, Esc close

Get the latest WordPress version from the API

harmlessText processingdebian, ubuntu
user@server
curl -s https://api.wordpress.org/core/version-check/1.7/ | jq -r '.offers[0].version'

Fetches the version check from api.wordpress.org and prints only the version number of the first offer, which is the current stable release. Together with wp core version, this quickly shows whether an installation is lagging behind. It is also an example of how JSON from curl can be parsed directly with jq.

Note: The -s option suppresses curl’s progress meter, which would otherwise clutter the output.

Also searched as

  • get latest wordpress version command line
  • is wordpress up to date
  • parse curl json output with jq

Related one-liners

All in Text processing

Count WordPress plugins by status

$wp plugin list --format=json --path=/var/www/vhosts/example.com/httpdocs | jq -r 'group_by(.status)[] | "\(.[0].status): \(length)"'
harmlessText processing

Convert a JSON array to CSV with a header row

$jq -r '(.[0] | keys_unsorted) as $k | $k, (.[] | [.[$k[]]]) | @csv' plugins.json > plugins.csv
cautionText processing

Extract a single field from JSON with jq

$jq -r '.require.php' composer.json
harmlessText processing

Filter a JSON array by a field value

$jq '[.[] | select(.status == "active")]' plugins.json
harmlessText processing

Pretty-print JSON with indentation and colors

$jq . composer.json
harmlessText processing

Check Cache-Control of all CSS, JS and image files on a page

$curl -s https://example.com/ | grep -oE '(src|href)="[^"]+\.(css|js|woff2?|jpe?g|png|gif|webp|avif|svg)(\?[^"]*)?"' | cut -d'"' -f2 | sed -E 's#^//#https://#; s#^/#https://example.com/#' | grep '^http' | sort -u | while read -r a; do printf '%-45s %s\n' "$(curl -sI "$a" | grep -i '^cache-control:' | tr -d '\r')" "$a"; done
harmlessImages and performance

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.