Skip to content

dns: bump to v0.7.0-dev.2 - #24

Merged
scotwells merged 2 commits into
mainfrom
dns/v0.7.0-dev.2
Aug 26, 2026
Merged

dns: bump to v0.7.0-dev.2#24
scotwells merged 2 commits into
mainfrom
dns/v0.7.0-dev.2

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

Bumps the dns plugin preview to v0.7.0-dev.2, still a pre-release for early feedback.

Three readability fixes to datumctl dns record list, all in the default table only — -o wide and -o json are unchanged and still give the full text:

  • Long values are shortened. tabwriter sizes a column to its widest cell, so one 400-byte DKIM key pushed STATUS off the right of every row in the table. The cost of one long value was paid by every short one.
  • Machine-written names are shortened. Verification tokens and ACME challenge labels run far past what human-authored records need; the cutoff keeps the latter intact.
  • --no-managed lists only the records you wrote, hiding the ones Datum manages on your behalf.

A footer names how many cells were shortened and points at -o wide / -o json, so nothing is silently hidden.

Upstream PRs: datum-cloud/dns-operator#107, datum-cloud/dns-operator#108, datum-cloud/dns-operator#109

🤖 Generated with Claude Code

Picks up three table-readability fixes to `datumctl dns record list`. A single 400-byte DKIM key used to size the VALUE column for the whole table, pushing STATUS off the right of every other row; long values and machine-written names are now shortened in the default view, with a note pointing at `-o wide` and `-o json` for the full text. `--no-managed` lists only the records you wrote, hiding the ones Datum manages on your behalf.

Release: https://github.com/datum-cloud/dns-operator/releases/tag/v0.7.0-dev.2

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@scotwells

Copy link
Copy Markdown
Contributor Author

CI hasn't picked this up yet — GitHub Actions is in a major outage and no pull_request run was created for this PR (or for a test PR I opened and closed). Nothing is wrong with the manifest; the event was dropped.

I ran both validation steps locally in the meantime, exactly as validate-pr.yaml does:

  • Schemaajv validate -s schema/plugin-v1alpha1.json --spec=draft7 -c ajv-formats → valid
  • URIs resolve and SHA256 matches — all five assets downloaded and hashed:
platform sha256
linux/amd64 5976ac38… OK
linux/arm64 1745d036… OK
darwin/amd64 73c43480… OK
darwin/arm64 9655a0e2… OK
windows/amd64 96eddb1a… OK

I'll push an empty commit to retrigger once Actions recovers, so this still merges on a real green run rather than on my say-so.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@scotwells

scotwells commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

Actions has recovered and validate passed on a1012ff1 (schema + all five SHA256s), matching what I'd verified locally.

Correction to my earlier comment: the original event wasn't dropped, just badly delayed — the run for 578bbc7b was eventually delivered off the throttled queue and also passed. Both runs are green.

Only a review stands between this and merge.

@scotwells
scotwells requested review from a team, JoseSzycho and kevwilliams August 26, 2026 17:58
@scotwells
scotwells enabled auto-merge August 26, 2026 18:12
@scotwells
scotwells disabled auto-merge August 26, 2026 18:36
@scotwells
scotwells merged commit f5184bf into main Aug 26, 2026
2 checks passed
@scotwells
scotwells deleted the dns/v0.7.0-dev.2 branch August 26, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants