Skip to content

docs: add internal release changelog tracker#1340

Merged
jcllobet merged 5 commits intodevfrom
task/release-changelog-tracker
Apr 4, 2026
Merged

docs: add internal release changelog tracker#1340
jcllobet merged 5 commits intodevfrom
task/release-changelog-tracker

Conversation

@jcllobet
Copy link
Copy Markdown
Collaborator

@jcllobet jcllobet commented Apr 4, 2026

Summary

  • keep changelog/release-tracker.md as an internal OpenWork release-tracking file
  • add #### Lines of code changed since previous release and #### Release importance to each entry
  • normalize release importance into Minor release: ... or Major release: ... so downstream code can split on the first colon

Validation

  • git diff --check
  • python3 -c 'from pathlib import Path; text=Path("changelog/release-tracker.md").read_text(); assert "#### Lines of code changed since previous release" in text; assert "98 lines changed since v0.11.99(58 insertions, 40 deletions)." in text; assert "1248 lines changed sincev0.11.100 (933 insertions, 315 deletions)." in text; assert "Minor release:" in text; assert "Major release:" not in text; print("validated OpenWork line-count and release-importance sections")'

Notes

  • internal docs-only prep; nothing was published to the public changelog page or docs
  • no UI behavior changed, so Docker/Chrome MCP verification was not applicable for this PR

Prepare a private release-tracking table for OpenWork so changelog summaries can be reviewed in-repo before anything is published publicly.
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openwork-app Ready Ready Preview, Comment Apr 4, 2026 6:24pm
openwork-den Ready Ready Preview, Comment Apr 4, 2026 6:24pm
openwork-den-worker-proxy Ready Ready Preview, Comment Apr 4, 2026 6:24pm
openwork-landing Ready Ready Preview, Comment, Open in v0 Apr 4, 2026 6:24pm
openwork-share Ready Ready Preview, Comment Apr 4, 2026 6:24pm

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 4, 2026

The following comment was made by an LLM, it may be inaccurate:

Replace the release tracker table with oldest-to-newest markdown sections so new OpenWork releases can be appended more intuitively.
Replace top-level label bullets with  subsections so release fields are easier to target while keeping list bullets only where they add structure.
Set the changelog and docs publication fields to explicit True or False values so the tracker has no ambiguous blanks.
Track text-line diff size and a normalized major/minor release summary so each release entry can describe both scope and user impact in a machine-friendly way.
Copy link
Copy Markdown
Collaborator Author

@jcllobet jcllobet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jcllobet jcllobet merged commit 615d11c into dev Apr 4, 2026
14 checks passed
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