Add release and security checklist - #23
Merged
Merged
Conversation
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: PR appears to be for a Terraform provider project, not one of the monitored repos (kernel, infra, hypeman, hypeship); please opt in manually if deploy monitoring is needed. To monitor this PR anyway, reply with |
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 10, 2026 20:13
d291397 to
5c40b04
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 11, 2026 14:26
5c40b04 to
24de4e1
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 11, 2026 14:58
24de4e1 to
24a4cd2
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 11, 2026 15:09
24a4cd2 to
a13019f
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 12, 2026 14:55
a13019f to
e7d50dc
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 15, 2026 19:22
e7d50dc to
374e2df
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 22, 2026 14:17
374e2df to
560b548
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
2 times, most recently
from
June 22, 2026 18:29
f73c178 to
c165f56
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 26, 2026 14:30
c165f56 to
544f32d
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 26, 2026 14:46
544f32d to
236f2f1
Compare
Merged
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 26, 2026 14:59
236f2f1 to
894993f
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 26, 2026 17:19
894993f to
1b8f180
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
2 times, most recently
from
June 29, 2026 13:43
6910d15 to
9be19e2
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
June 29, 2026 19:14
605d826 to
ec75679
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 02:34
ec75679 to
6d983b9
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 02:48
6d983b9 to
5e0df2f
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 19:38
5e0df2f to
65a2384
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 19:51
65a2384 to
9e1c5c4
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
2 times, most recently
from
July 2, 2026 20:15
54a2157 to
3d6f08e
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 20:25
3d6f08e to
72e1b39
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 20:37
72e1b39 to
bbe1a34
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 20:47
bbe1a34 to
5f986a4
Compare
IlyaasK
force-pushed
the
ci-checks
branch
2 times, most recently
from
July 2, 2026 20:52
06f19d8 to
ee8d5f6
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 20:52
5f986a4 to
8e073ad
Compare
IlyaasK
force-pushed
the
release-security-checklist
branch
from
July 2, 2026 20:57
8e073ad to
1ebeb33
Compare
tnsardesai
approved these changes
Jul 2, 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
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.
What changed
terraform-registry-manifest.jsonwith Terraform Plugin Framework protocol["6.0"].docs/release.mdwith release, Terraform Registry, GoReleaser, signing/checksum, and security/state review checklists.docs/teach.mdwith the release/security lesson.Intentionally unsupported
Tests run
jq . terraform-registry-manifest.json >/dev/nullbash -n scripts/check-docs.shterraform fmt -check -recursive examplesGOCACHE=/private/tmp/terraform-provider-kernel-ci-go-cache go test -short -timeout=2m ./...GOCACHE=/private/tmp/terraform-provider-kernel-ci-go-cache go vet ./...git diff --check ci-checksbash scripts/check-docs.shReview gates
All five gates passed after the accepted autoreview fix:
Note
Low Risk
Documentation and a static registry manifest only; no provider logic, credentials, or release pipeline behavior changes.
Overview
Adds
terraform-registry-manifest.jsondeclaring Terraform Plugin Framework protocol6.0, which release assets are expected to ship as a versioned manifest derived from this file.Adds
docs/release.md, a pre-publish checklist covering CI commands, opt-in acceptance tests, registry asset naming (zips, checksums, GPG signature), GoReleaser/registry setup notes, and explicit security/state expectations (sensitiveapi_key, no runtime browser ops in the client, durable-onlykernel_browser_poolstate,force=falseon delete, import behavior).No release automation, GoReleaser config, or workflow changes are included in this diff.
Reviewed by Cursor Bugbot for commit 1ebeb33. Bugbot is set up for automated code reviews on this repo. Configure here.