Skip to content

[codex] Track release provenance and opt-in telemetry roadmap#68

Draft
toby-bridges wants to merge 1 commit into
masterfrom
docs/roadmap-release-telemetry
Draft

[codex] Track release provenance and opt-in telemetry roadmap#68
toby-bridges wants to merge 1 commit into
masterfrom
docs/roadmap-release-telemetry

Conversation

@toby-bridges

@toby-bridges toby-bridges commented Jun 10, 2026

Copy link
Copy Markdown
Owner

Summary

  • record the v2.3.0 release artifact verification false alarm caused by hashing a CRLF-converted Windows working-tree file instead of the Git tag blob
  • document release artifact provenance hardening as a follow-up
  • document a privacy-first, opt-in usage telemetry candidate for future active-install and step-failure visibility
  • gate any future remote telemetry behind release artifact provenance work

Validation

  • git diff --check
  • docs-only change; no pytest run

@toby-bridges toby-bridges force-pushed the docs/roadmap-release-telemetry branch from 0ba89c8 to 9b91ec2 Compare June 10, 2026 14:47
@toby-bridges toby-bridges changed the title [codex] Track release parity and opt-in telemetry roadmap [codex] Track release provenance and opt-in telemetry roadmap Jun 10, 2026
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