ci: build and publish the plugin from the release itself - #112
Merged
Conversation
Publishing a plugin release has been two manual steps: run goreleaser by hand to attach the archives, then hand-edit plugins/dns.yaml in datum-cloud/datumctl-plugins to bump the version, rewrite five download URLs, and copy five digests out of checksums.txt. Both are mechanical, both sit between "released" and "users can install it", and the second is caught only by catalog CI when a digest is wrong. This runs both from the release event. goreleaser attaches the archives with `mode: append`, so it adds to the release the tagger already wrote rather than replacing the notes, and the catalog step then opens the bump PR through the shared update-plugin-index action. The catalog PR still goes through review and CI there; nothing is auto-merged. Both jobs live in one workflow because the catalog update reads the checksums.txt that goreleaser uploads, and `needs:` cannot reach across workflow files. That ordering is what makes the workflow safe: an earlier draft guarded against releases carrying no plugin assets, on the evidence that v0.6.5 through v0.6.8 have none. That evidence does not hold — the plugin was only added on 2026-08-22 and v0.6.8 was tagged on 2026-07-29, so those releases predate it entirely. Every release cut from main now ships the plugin, which means a missing checksums.txt is not a release to skip politely but a build that failed, and skipping it would have left the catalog silently pinned to an old version. Sequencing the jobs removes the question: this workflow is what puts the assets there. goreleaser uploads with the built-in token, since the release is in this repository. The catalog is not, so that job mints a token from the release bot app — the same app datumctl/release.yaml uses — in the job that consumes it, because a masked value handed between jobs arrives empty. Verified against a clean checkout of v0.7.0-dev.2, which is the state CI sees: goreleaser's own validate step passes there (locally it needed --skip=validate only because of untracked files) and all five archives plus checksums.txt are produced. actionlint is clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
scotwells
changed the title
scotwells
force-pushed
the
ci/auto-update-plugin-index
branch
from
August 26, 2026 19:09
54e8fb4 to
650b4c4
Compare
0xmc
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publishing a release now ships the plugin end to end — the archives get built and attached, and the PR bumping the plugin catalog opens on its own.
Today both halves are manual, which is the gap between "released" and "users can install it." That's the step most likely to get skipped when a preview tag is meant to reach people while their feedback still matters.
The catalog PR still gets review and CI in that repo — nothing is auto-merged. Hand-written release notes are preserved.
Needs an org admin first: confirm
datumctl-pluginsis among the selected repositories for thedatum-release-botapp. If it isn't, only the catalog step fails; the release and its archives are unaffected.Verified against a clean checkout of v0.7.0-dev.2: all five archives and
checksums.txtbuild, and the catalog update reproduces the manifest hand-written for datum-cloud/datumctl-plugins#24 byte for byte.🤖 Generated with Claude Code