Skip to content

docs: weekly release updates (2026-06-02)#171

Open
dannyneira wants to merge 3 commits into
mainfrom
skill/release-updates
Open

docs: weekly release updates (2026-06-02)#171
dannyneira wants to merge 3 commits into
mainfrom
skill/release-updates

Conversation

@dannyneira
Copy link
Copy Markdown
Member

@dannyneira dannyneira commented Jun 2, 2026

Summary

  • Ran release_updates tasks in order: changelog.
  • No working-tree file changes were detected in this run.

Validation

  • Ran the release update scripts successfully.

Co-Authored-By: Oz oz-agent@warp.dev

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Jun 2, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 2, 2026

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

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jun 2, 2026 10:52pm

Request Review

@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented Jun 2, 2026

@dannyneira

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

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

Overview

This PR adds a new release_updates skill with scripts to automate weekly changelog, license, telemetry, and Warp artifact preparation for docs maintenance. I found two correctness issues in the generated workflow: the documented default dry run cannot complete without real artifact sources, and newly-created changelog year files can be populated with entries from every historical year.

Concerns

  • The documented --dry-run all-task command fails once downstream tasks try to read artifact-derived license/telemetry inputs that the dry-run artifact step never creates.
  • The changelog updater does not filter entries to the requested output year when creating a new year file, so a new annual changelog can import older years' releases.

Verdict

Found: 0 critical, 2 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Dry run:

```bash
python3 .agents/skills/release_updates/scripts/run_release_updates.py --dry-run
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ [IMPORTANT] This documented all-task dry run currently fails: update_warp_app.py --dry-run does not produce artifact paths, but the later license/telemetry tasks still require those sources. Either document the required explicit inputs for all-task dry runs or make the downstream tasks skip source resolution in dry-run mode.

existing_body = ""
cutoff_date = None

entries = _new_entries(stable_changelogs=stable_changelogs, cutoff_date=cutoff_date)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ [IMPORTANT] When the target changelog file is new, cutoff_date is None, so _new_entries() returns every stable changelog entry across all years and writes historical releases into the new year file. Filter entries to the selected year before merging them.

@dannyneira dannyneira changed the title skills: add release_updates automation for release docs updates docs: weekly release updates (2026-06-02) Jun 2, 2026
@dannyneira dannyneira self-assigned this Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant