[GNU ELPA] Kubed version 0.7.1

Version 0.7.1 of package Kubed has just been released in GNU ELPA.
You can now find it in M-x list-packages RET.

Kubed describes itself as:

  ========================
  Kubernetes, Emacs, done!
  ========================

More at https://elpa.gnu.org/packages/kubed.html

## Summary:

  This library defines commands for interacting with Kubernetes
  resources, such as Kubernetes pods, services, deployments, and more.

  Use `kubed-display-pod' to display a Kubernetes pod,
  `kubed-edit-pod' to edit it, `kubed-delete-pods' to delete it, and
  `kubed-list-pods' to see a menu of all pods.  You can create new pods
  from YAML or JSON files with `kubed-create-pod'.

  Similar commands are defined for other types of resources as well.

## Recent NEWS:

             ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
              KUBED NEWS – HISTORY OF USER-VISIBLE CHANGES
             ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━


This file contains the release notes for Kubed, a rich Emacs interface
for Kubernetes.

For further details, see the Kubed manual:
[https://eshelyaron.com/kubed.html].


[https://eshelyaron.com/kubed.html] <https://eshelyaron.com/kubed.html>


Version 0.7.1 on 2026-06-19
═══════════════════════════

  This is a bugfix release, it fixes a regression in version 0.7.0 that
  caused reverting resource YAML buffers to fail in Emacs 29/30.

  See report at <https://github.com/eshelyaron/kubed/pull/21>


Version 0.7.0 on 2026-06-14
═══════════════════════════

  This release includes several minor improvements and bug fixes, along
  with one larger new feature:


Kubed now distinguishes between “execution environments”
────────────────────────────────────────────────────────

  Kubed commands run `kubectl' in the buffer from which you invoke them,
  so settings that affect `kubectl', from environment variables such as
  `KUBECONFIG' to running on a whole other host via Tramp, can differ
  from one buffer to the next.  Kubed now treats each distinct
  combination of these settings as an “execution environment”, and keeps
  its state separate for each one.  This lets you work in parallel with
  clusters reached through different `KUBECONFIG' files (for example as
  set per-directory by <https://github.com/purcell/envrc>).  The new
  “Execution Environments” section in the Kubed manual provides
  additional details.

  See feature request at
  <https://lists.sr.ht/~eshel/kubed-devel/%[email protected]%3E>


Version 0.6.1 on 2026-04-13
═══════════════════════════

  This is a maintenance release, it includes one important bug fix:


Fix “Invalid format string” error in Tramp integration
──────────────────────────────────────────────────────

  This version fixes a regression introduced in version 0.6.0, which
  caused an error when starting a shell or opening Dired inside a pod.

  See bug report at
  <https://lists.sr.ht/~eshel/kubed-devel/%[email protected]%3E>


Version 0.6.0 on 2026-04-11
═══════════════════════════

Kubed now uses the remote `kubectl' on remote hosts
───────────────────────────────────────────────────

  When you invoke Kubed commands in a buffer whose `default-directory'
  points to a directory on a remote host (such as
  `/ssh:[email protected]:/some/remote/dir/'), Kubed runs `kubectl' on
  the remote host, so you can interact with clusters that are configured
  in the remote kubeconfig and accessible from the remote host.

  Note that this is a rather extensive change, please tell us about
  issues/regressions if you see any!


`kubed-kubectl-program' is now connection-local
───────────────────────────────────────────────

  You can configure different `kubed-kubectl-program' values for
  different hosts on which you run `kubectl' via Kubed commands, by
  giving the variable a connection-local value for certain hosts.  For
  example:

  ┌────
  │ (connection-local-set-profile-variables
  │  'my-kubed-profile-for-somehost
  │  '((kubed-kubectl-program . "/home/user/my-kubectl")))
  │ 
  │ (connection-local-set-profiles
  │  '(:application kubed :machine "somehost.com")
  │  'my-kubed-profile-for-somehost)
  └────


New user option `kubed-default-context-and-namespace-alist'
───────────────────────────────────────────────────────────

  This user option generalizes and supersedes the existing user option
  `kubed-default-context-and-namespace', which is considered obsolete
  but is still available.  The new user option lets you set different
  defaults depending on the host on which Kubed is running `kubectl'.


Command `kubed-transient' is now bound to `k' in `kubed-prefix-map'
───────────────────────────────────────────────────────────────────

  This was already a recommended binding for this command, which opens
  the “root” Kubed transient menu.


New user option `kubed-logs-follow'
───────────────────────────────────

  The new user option `kubed-logs-follow' controls whether Kubed follows
  new log entries by default when showing Kubernetes logs.  It defaults
  to `t'.


New user option `kubed-logs-tail-lines'
───────────────────────────────────────

  Kubed commands that show logs for Kubernetes resources now fetch only
  the most recent 128 log lines by default, to avoid flooding the logs
  buffer with the full history of long-running workloads.  You can
  customize this limit with the new user option `kubed-logs-tail-lines';
  …  …