Skip to content

docs: record v1.3.0 security release and current installation - #263

Merged
jinxiao merged 1 commit into
mainfrom
codex/docs-v1.3-acceptance
Oct 23, 2026
Merged

jinxiao merged 1 commit into
mainfrom
codex/docs-v1.3-acceptance

Conversation

@jinxiao

@jinxiao jinxiao commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Issue

Refs #255

Publication issue #257 is closed after successful v1.3.0 publication. Non-blocking release-file disclosure follow-up: #262.

Summary

Pin current installation commands and compatibility requirements to published v1.3.0 / Go 1.27.3. Explain that Logger stacks remain Preview but are available in v1.3.0 and main; retain the historical v1.2.0 comparison and update the error-log output. Preserve previous release notes and acceptance records.

Record the actual publication at 2df7e85: one stable Latest Release, 27 matching module tags, 27 fresh public checksum consumers, complete exact PR/main CI, and 62 production-package vulnerability scans with zero findings. Also record official npm audit (103 dependency entries, zero advisories), pip-audit (eleven locked packages, zero advisories), and the independent public Logger/Tracer smoke. Update CHECKLIST only for verified milestones.

Testing

  • Release PR/main Full regression and publication run 39890005244 passed; no tag recovery or rewriting.
  • Public v1.3.0 Logger smoke passed API/error identity, attached stacks, compact single-line JSON and opt-out. Public Tracer selects x/crypto v0.58.0. CGO_ENABLED=0, GOWORK=off, fresh caches and public proxy/checksum database.
  • Local 26 utility-guide contracts, strict site build and discovery for 122 guides / 19 crawler policies passed. Native docs CI must pass on this final documentation head before merge.
  • No Go code/dependency/version changes, AWS cloud tests or race detector in this PR.

Risks and compatibility

The frozen X-Ray adapter is excluded from the release. Scan conclusions cover actual production package closures, not unused upstream tool dependencies. Historical evidence stays at its original scope. The P3 #262 file-list omission does not affect source packaging. Keep #255 open until main documentation deployment succeeds; this documentation PR does not publish another Go version.

Release notes

  • repository | documentation | Pin installation to v1.3.0 and record published security, Preview availability and public consumer acceptance.

Integration links

Optional repository integration links may appear below this section.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

@jinxiao

jinxiao commented Oct 23, 2026

Copy link
Copy Markdown
Contributor Author

Maintainer review of 319bd4c: no remaining blocking findings. The diff changes documentation and sanitized acceptance only. Published v1.3.0 / Go 1.27.3 installation commands match actual public consumption; Logger Preview availability and the error-output example match the published behavior, with the v1.2.0 comparison retained.

Acceptance was checked against the completed publication artifact, exact PR/main CI, one stable Latest Release, all 27 same-commit tags, 27 public checksum consumers, 62 zero-finding production-package scan logs and actual npm/Python audit JSON. Public smoke verifies the stack API, identity, compact JSON/opt-out and x/crypto v0.58.0. Historical records were preserved and #262 is disclosed as a non-blocking follow-up. Local strict build/discovery and exact-head native documentation CI passed. This is author/maintainer review, not independent approval.

The Issue reference formatting has been corrected in the PR description. Merge remains conditional on its latest native contribution check passing. Keep #255 open until the merged-main documentation deployment succeeds; no further Go release is needed.

@jinxiao
jinxiao merged commit 381a65c into main Oct 23, 2026
10 of 12 checks passed
@jinxiao
jinxiao deleted the codex/docs-v1.3-acceptance branch October 23, 2026 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant