fix(deps): update module go.datum.net/datumctl to v0.18.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
go.datum.net/datumctl	v0.15.0 → v0.18.0

---

Release Notes

datum-cloud/datumctl (go.datum.net/datumctl)

v0.18.0

Compare Source

A new datumctl api proxy command gives you a local authenticated gateway to the Datum Cloud API — point any tool at localhost and it talks to the platform with zero token plumbing.

What's new

• datumctl api proxy — starts a loopback proxy that injects your session credentials on every request and refreshes them transparently, so a dev server, test harness, or curl can talk to the Datum Cloud API without ever handling a token. Supports --project/--organization scoping to a single control plane, passes through Kubernetes-style watches and SSE unbuffered, and binds to 127.0.0.1 only with Host-header validation against DNS rebinding. See docs/api-proxy.md. (#​247)

Full Changelog: datum-cloud/datumctl@v0.17.4...v0.18.0

v0.17.4

Compare Source

What's Changed

• fix: honor ^C during interactive login waits by @​ecv in #​252
• fix: quit login gracefully on ^D (EOF) during auth waits by @​ecv in #​253

Full Changelog: datum-cloud/datumctl@v0.17.3...v0.18.0

v0.17.3

Compare Source

What's Changed

• feat(services): embed services list/enable/status in datumctl core by @​scotwells in #​250
• feat: Gate datumctl on per-org cloud-portal onboarding by @​mattdjenkinson in #​239

New Contributors

• @​mattdjenkinson made their first contribution in #​239

Full Changelog: datum-cloud/datumctl@v0.17.2...v0.17.3

v0.17.2

Compare Source

What's Changed

• fix: hard-error on unknown 'auth' subcommands by @​ecv in #​245
• fix: keep whoami honest about which environment you're in by @​scotwells in #​249

Full Changelog: datum-cloud/datumctl@v0.17.1...v0.17.2

v0.17.1

Compare Source

Changelog

• 8c60a31 Merge pull request #​241 from datum-cloud/fix/trusted-plugin-flag-passthrough
• 83cf617 Merge pull request #​244 from datum-cloud/fix/auth-help-stale-login-examples
• 98ab9f9 fix(plugindispatch): forward args verbatim to trusted PATH plugins
• 50e6d44 fix: correct stale 'datumctl auth login' references

v0.17.0

Compare Source

Signing in to two Datum Cloud environments with the same email address used to silently corrupt your login — this release fixes the root cause, heals existing installs automatically, and makes datumctl auth switch show you exactly which account you're on.

---

Fixed: logging in to two environments no longer breaks each other (#​237)

Signing in to production and staging with the same email stored both logins under one credential slot, so the second sign-in silently overwrote the first. datumctl auth list still showed both accounts, but after datumctl auth switch the CLI would send one environment's token to the other's API and fail with:

error: You must be logged in to the server (the server has asked for the client to provide credentials)

Logins are now kept separate per environment, so switching accounts, automatic token refresh, and logout all stay scoped to the right one.

Existing installs heal themselves the next time they authenticate — no manual steps, and the migration never deletes a token it can't first preserve.

[!NOTE]
If your login was already overwritten before upgrading, that one token is unrecoverable. Run datumctl login --hostname <that environment's auth host> once to re-establish it; every other environment keeps working without any action.

datumctl auth switch now shows your active account (#​237)

The account you're currently signed in as is labeled (active) in the picker, and the picker now opens on it — so it's always clear what you're switching from:

Which login session?
> swells@datum.net  (api.staging.env.datum.net)  (active)
  swells@datum.net  (api.datum.net)

Full Changelog: datum-cloud/datumctl@v0.16.0...v0.17.0

v0.16.0

Compare Source

The plugin system just got its ecosystem. In v0.15.0 you could install plugins from a single Datum-operated catalog. Now anyone — a community author, an open-source project, or an enterprise platform team — can publish their own catalog, and you can register, search, browse, and install across all of them through the same commands you already know. The curated datum catalog stays the trusted, zero-configuration default, so nothing changes if you never add one.

---

New: register third-party catalogs (datumctl plugin index) (#​224)

Plugins can now come from more than one place. Add a community or internal catalog with a single command — and an explicit one-time trust decision so you always know what you're opting into.

datumctl plugin index add acme https://plugins.acme.example/index.yaml
datumctl plugin index list

New: search and install across every catalog (#​224)

search and install now span every registered catalog at once, with clear official vs. third-party badges wherever a plugin appears — provenance is never ambiguous. Pin a specific release from any catalog when you need to.

datumctl plugin search dns
datumctl plugin install dns

New: interactive marketplace browser (datumctl plugin browse) (#​224)

Prefer to explore? datumctl plugin browse opens an interactive view across all catalogs, each result clearly badged by source.

For enterprises (#​224)

Private internal catalogs are first-class. A new datumctl plugin validate command lets authors check a manifest before publishing, and allow-list guardrails let platform teams scope which publishers are permitted — down to individual GitHub owners or repositories — with the policy re-enforced continuously, not just at the moment a catalog is added.

[!NOTE]
Third-party plugins run with your Datum credentials, so provenance, the one-time trust decision, and credential handling all got a careful security pass. The curated datum catalog remains the trusted, zero-setup default.

Docs

• Homebrew install note — the install guide now includes the brew trust step needed by newer Homebrew versions (#​215).

Full Changelog: datum-cloud/datumctl@v0.15.2...v0.16.0

v0.15.2

Compare Source

What's Changed

• feat: add --exec-interactive-mode to auth update-kubeconfig by @​ecv in #​221

New Contributors

• @​ecv made their first contribution in #​221

Full Changelog: datum-cloud/datumctl@v0.15.1...v0.15.2

v0.15.1

Compare Source

What's Changed

• fix(deps): update module go.miloapis.com/milo to v0.25.0 by @​renovate[bot] in #​190
• chore(deps): bump go.opentelemetry.io/otel from 1.40.0 to 1.41.0 in the go_modules group across 1 directory by @​dependabot[bot] in #​200
• fix(deps): update module charm.land/bubbletea/v2 to v2.0.7 by @​renovate[bot] in #​201
• chore(deps): update go toolchain directive to v1.26.4 by @​renovate[bot] in #​203
• fix(deps): update module go.miloapis.com/milo to v0.27.0 by @​renovate[bot] in #​205
• fix(deps): update module k8s.io/klog/v2 to v2.140.0 by @​renovate[bot] in #​206
• fix: honor -v verbosity for HTTP logging in all commands by @​scotwells in #​207
• fix(deps): update module go.miloapis.com/milo to v0.28.1 by @​renovate[bot] in #​208
• fix(nix): use shared nix-update-hash workflow by @​drewr in #​199
• fix: non-standard SPDX license by @​0xmc in #​216

New Contributors

• @​0xmc made their first contribution in #​216

Full Changelog: datum-cloud/datumctl@v0.15.0...v0.15.1

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 6 additional dependencies were updated

Details:

Package	Change
go.yaml.in/yaml/v2	v2.4.3 -> v2.4.4
golang.org/x/net	v0.52.0 -> v0.55.0
golang.org/x/sys	v0.44.0 -> v0.47.0
golang.org/x/term	v0.43.0 -> v0.45.0
golang.org/x/text	v0.35.0 -> v0.37.0
golang.org/x/tools	v0.43.0 -> v0.44.0