From 1e32a39a1dd7b8063c5f5161de5b826b30ca4a4a Mon Sep 17 00:00:00 2001 From: dlotterman Date: Tue, 10 Nov 2026 17:15:43 -0800 Subject: [PATCH] docs: explain plugin installs from pre-release-only repositories Explain that installing a plugin from a GitHub repository with only pre-releases installs the highest pre-release, and which tag formats plugin authors should use. Based on datum-cloud/datumctl#361. Replaces #145. Also repair datumctl/plugins/using-plugins.mdx: since a70ea1f the page has ended in 852 NUL bytes and a duplicated "Contexts & scoping" line, so git treats it as binary and reviews show no diff. --- datumctl/plugins/building-plugins.mdx | 2 +- datumctl/plugins/using-plugins.mdx | Bin 8391 -> 7633 bytes 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/datumctl/plugins/building-plugins.mdx b/datumctl/plugins/building-plugins.mdx index 4f84bd9..cd8952c 100644 --- a/datumctl/plugins/building-plugins.mdx +++ b/datumctl/plugins/building-plugins.mdx @@ -184,7 +184,7 @@ Users can always install directly from a GitHub release without a catalog: datumctl plugin install your-org/datumctl-dns ``` -This path requires a `checksums.txt` alongside your release archives, in goreleaser's default two-column format. +This path requires a `checksums.txt` alongside your release archives, in goreleaser's default two-column format. Tag releases with a semantic version such as `v1.2.3` or `v1.2.3-rc.1`. If you have published only pre-releases, datumctl installs the highest pre-release tag. ## Next steps diff --git a/datumctl/plugins/using-plugins.mdx b/datumctl/plugins/using-plugins.mdx index a59d07727f3f8c78b8083afe3462bacfdd590ccb..9401c6e5b152f6daa23fa013a9268c17fb4dad56 100644 GIT binary patch delta 237 zcmY+8u?@mN5Cl^a0}=u0#>l1tA|jv*ANb&3od2!AHh5MM1GHcTr%SMiNm(!w4))%2?UBuD2*D92KMximY*t&Hjf~ zUTyTDg?X=4y%np53wS3js=(RrNdH7x&t&Yuyf6FkCxxjB?H>*Qfee8t+F3r?LUtwq&S42y