Skip to content

release-readiness.md

Latest commit

 

History

History
57 lines (45 loc) · 3.98 KB

release-readiness.md

File metadata and controls

57 lines (45 loc) · 3.98 KB
Raw

First v0 milestone

Decision 0023 accepts preparing a consumer milestone before a v1 compatibility commitment. This checklist records preparation, not authorization to publish:

  • Complete application with native/buffered/streaming registration.
  • Local tests for both credentials, grant outcomes and streaming lifecycle.
  • External-module check using public imports.
  • Accurate support matrix, testing guide and allocation baselines.
  • Reproducible SDK versions and an isolated Smithy patch update.
  • Race tests, vet, module verification, formatting and Linux arm64/amd64 builds.

Release Please and GitHub App authentication are now configured for an initial v0.1.0 under decision 0024. The release guide documents the workflow and required App setup. Merging a generated release PR is the publication decision; automation does not resolve the remaining readiness items below.

Verified readiness (2026-09-27)

PR #1 merged on 2026-09-27. All four jobs in the run for f6a2624 passed: test (1.27.0), test (1.27.x), lambda-build (arm64) and lambda-build (amd64). This provides GitHub evidence for formatting, race tests, vet, module verification, external consumer checks and both Linux builds. Later commits require their own passing PR checks. Per the user's 2026-09-27 direction, Go validation runs only on PRs; main pushes run only release automation.

The organization Actions secrets RELEASE_PLEASE_CLIENT_ID and RELEASE_PLEASE_PRIVATE_KEY are provisioned with selected-repository access for go-lambda-edge. Secret metadata and repository access were verified on 2026-09-27; the obsolete repository variable and private-key secret were removed. The new key and Client ID were verified against the astrocompute-release-please App and its repository installation using read-only API calls without printing credentials. Its installation grants all three required write permissions. No branch protection was configured; the owner will configure it manually (decision 0025).

Outstanding evidence and owner choices

The first main run passed the original repeated validation but failed at App token creation: the repository installation lookup returned 404. The owner subsequently installed astrocompute-release-please, and installation access is now verified. Release Please has since executed successfully: the App opened the v0.1.0 release PR, updates it on each main push, and its Go checks pass.

The owner chose the Apache License, Version 2.0 on 2026-10-02, with Andrew Beck as copyright holder (decision 0023 R6). LICENSE is the unmodified canonical text.

The owner merged the release PR on 2026-10-02, and the release run published v0.1.0 at commit 9423302. Repository visibility is unchanged; make the repository public, enable private vulnerability reporting for the security policy, and then request the version from the Go module proxy so pkg.go.dev indexes it.

REST streaming's SDK deployment qualification remains open: local probes cannot establish AWS acceptance of the observed mode-header/connection behavior. Authoritative clarification or a separately approved live test is still needed. Live Cognito/STS interoperability is also unverified; local fixtures are synthetic. No cloud resources were deployed.

The nested docs/probes/iamproof module is historical research. Root tests and CI do not traverse it. Run its tests explicitly if relying on new probe evidence; current production proof tests live in the root module's iamproof package.