You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iceberg.apache.org by ze...@apache.org on 2026/09/02 17:53:57 UTC
(terraform-provider-iceberg) branch main updated: Docs change for rc version (#104)
This is an automated email from the ASF dual-hosted git repository.
zeroshade pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/terraform-provider-iceberg.git
The following commit(s) were added to refs/heads/main by this push:
new eac5bda Docs change for rc version (#104)
eac5bda is described below
commit eac5bda23e3f1a8dad97145a854cb0fd63d0d94a
Author: Alex Stephen <13...@users.noreply.github.com>
AuthorDate: Wed Sep 2 10:53:52 2026 -0700
Docs change for rc version (#104)
---
docs/releasing.md | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/docs/releasing.md b/docs/releasing.md
index 94652e3..8309211 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -229,6 +229,11 @@ The final GitHub release carries exactly the files the registry requires: one
`..._SHA256SUMS`, one `..._SHA256SUMS.sig` signed by the KEYS-registered key,
and one `..._manifest.json`.
+> **Note:** Because the binaries are promoted rather than rebuilt, `go version -m`
+> on one reports the RC tag it was built from (`v0.7.0-rc1`). The filenames and
+> the registry metadata carry the final version, and those are what Terraform
+> resolves against.
+
Within a few minutes the
[Terraform Registry](https://registry.terraform.io/providers/apache/iceberg) and
[OpenTofu Registry](https://search.opentofu.org/provider/apache/iceberg) detect
@@ -296,6 +301,9 @@ It expects `git`, `gpg`, `curl`, and `shasum`/`sha512sum` on your `PATH`.
The RAT License check needs `java` and `unzip`, but can be skipped with `VERIFY_RAT=0`.
Binary verification needs [`gh`](https://cli.github.com/) and can be skipped with `VERIFY_BINARY=0`.
+The binaries are named with the final version, but `go version -m` reports the RC
+tag they were built from. That is expected, and stays true of the final release.
+
A valid signature from a key in the `KEYS` file, a matching checksum, a clean RAT
check, verified binaries, and a clean build and test is a `+1`.