[ndbroadbent]

Replace the expired public-key copy in the repository with the existing release signer, BD2DE4CA3CF5BA4D (fingerprint 531ED8661E17EAC44124AE57BD2DE4CA3CF5BA4D). This key was already registered in the Terraform Registry. No signing key was generated and no signing secret changed.

Validation: imported the public key into an isolated keyring and used gpgv to verify the published 0.2.2 SHA256SUMS signature successfully. Provider CI passed its build, vet and tests.

Correction to the original diagnosis: Registry ingestion is blocked by HashiCorp issue #67, not an established signing-key problem. HashiCorp confirms that claimed namespaces receive GitHub App events, so no repository webhook is expected. The reported Resync preview would remove existing versions; do not confirm it. Provider PR #2 corrects the README guidance and documents tested installation options; its CI passed. Normal Registry installation of 0.2.2 still needs verification after ingestion is repaired.

[ndbroadbent]

QA — 2026-10-21, commit 7d86fe0fa437c48682c51cc3aa2c6e5cd07a9bb1:

• Imported the public key into an isolated keyring and verified the published 0.2.2 SHA256SUMS signature with gpgv: good signature from fingerprint 531ED8661E17EAC44124AE57BD2DE4CA3CF5BA4D.
• Provider CI passed its build, vet and tests: https://github.com/DocSpring/terraform-provider-logstruct/actions/runs/39544017395
• The 0.2.2 binary release workflow also passed: https://github.com/DocSpring/terraform-provider-logstruct/actions/runs/39542885030
  Registry publication remains incomplete: the public API lists versions only through 0.1.12. The current signing key is already registered. The blocker is tracked in [Bug Report]: DocSpring/logstruct v0.2.0 and v0.2.1 not ingested, and Resync would remove every published version hashicorp/terraform-registry-support#67. Claimed namespaces receive GitHub App events, so no repository webhook is expected. Do not confirm the reported Resync preview that would remove published versions. Normal Registry installation of 0.2.2 remains unverified.

Correction (2026-10-21): the earlier claim that key registration and a missing repository webhook caused the ingestion failure was unsupported.