Skip to content

fix: update doc-freshness skill to use correct release workflow#36

Merged
Troublor merged 2 commits intomainfrom
william/doc/update-doc-freshness-release-workflow
Apr 8, 2026
Merged

fix: update doc-freshness skill to use correct release workflow#36
Troublor merged 2 commits intomainfrom
william/doc/update-doc-freshness-release-workflow

Conversation

@Troublor
Copy link
Copy Markdown
Collaborator

@Troublor Troublor commented Apr 8, 2026

Summary

  • The old Phase 1.5 used gh release list on dist-docs, which has no GitHub Releases — making it impossible to determine the latest released mega-reth version.
  • The new approach checks mega-reth GitHub Releases directly for the latest version, then cross-references with dist-docs merged PRs (matching chore: release vX.Y.Z pattern) to confirm the release has been announced to external partners.
  • Adds hardfork activation gating for mega-evm spec changes: spec changes tied to a named hardfork are only doc-worthy after the hardfork activates on mainnet, determined by checking dist-docs release notes for activation timestamps.
  • Updates the dist-docs row in the Tracked Repos table to accurately describe what dist-docs is used for (release notes and hardfork schedules, not release tags).

@claude
Copy link
Copy Markdown
Contributor

claude bot commented Apr 8, 2026

The only changed file is .claude/skills/doc-freshness/SKILL.md. Per REVIEW.md, changes to .claude/ skill files are skipped in review. LGTM.

@Troublor Troublor merged commit cf9e74b into main Apr 8, 2026
5 checks passed
@Troublor Troublor deleted the william/doc/update-doc-freshness-release-workflow branch April 8, 2026 14:44
@Troublor
Copy link
Copy Markdown
Collaborator Author

Troublor commented Apr 8, 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