Release v0.9.0

Release v0.8.0

Release v0.7.1

Release v0.7.0

- FIX: Show current context/ns color in interactive (fzf) mode. (ahme…

…tb#109)

- TEST: Add integration tests for kubectx (ahmetb#111, ahmetb#113) and kubens (ahmetb#105, ahmetb#117)

v0.6.2

- FEATURE: use XDG_CACHE_HOME to store data instead of $HOME/.kube if available
  (ahmetb#93)
- FEATURE: introduce KUBECTX_IGNORE_FZF variable to override interactive mode
  when fzf is detected (ahmetb#82)
- FIX: support Windows Subsystem for Linux (WSL) by detecting kubectx.exe in
  PATH when kubectl is not (ahmetb#96)
- FIX: zsh completion script glitch that printed only two contexts (ahmetb#81)
- IMPROVED: print errors when kubectl[.exe] is not detected in PATH (ahmetb#92)
- IMPROVED: better error handling when executed subcommands (like kubectl) fail
  (ahmetb#95)

v0.6.1

- FIX: fix crash when kubectx/kubens is installed --with-short-names and fzf(1)
  is in PATH, but calling the binaries with the wrong name. (ahmetb#78)

Release v0.6.0

- FEATURE: interactive search mode when kubectx and kubens are ran without any
  arguments and fzf(1) is detected in PATH. (ahmetb#71, ahmetb#74)
- FIX: kubectx -d now doesn't ignore arguments after the first argument. (ahmetb#75)
- FIX: empty output bug when TERM=vt100 even though NO_COLOR is set. (ahmetb#57, ahmetb#73)
- FIX: --help exits with code 0 now. (ahmetb#69, ahmetb#72)

Release v0.5.1

v0.5.0 (2018-04-09)

- SECURITY FIX: A context name that contains '/' in the name could arbitrarily
  overwrite any on the filesystem through a crafted context name when it is
  used with kubectx.

  This is fixed in ahmetb#37 by @jvassev. kubectx now handles context names with '/'.

- FEATURE: Renaming context will now overwrite if the specified name already
  exists, through deleting the existing context entry in kubeconfig. (ahmetb#25)

- FEATURE: Deleting context entries in kubeconfig with "kubectx -d NAME" ('.'
  for current). This only deletes the context entry and does not touch 'users'
  and 'clusters' keys in kubeconfig (and therefore might leak those entries).
  Use this only if you do not care about the extra values in your kubeconfig.
  (ahmetb#23, ahmetb#38)