Skip to content

[codex] Use generated release notes placeholder#501

Merged
gschier merged 1 commit into
mainfrom
codex/release-notes-placeholder
Jul 6, 2026
Merged

[codex] Use generated release notes placeholder#501
gschier merged 1 commit into
mainfrom
codex/release-notes-placeholder

Conversation

@gschier

@gschier gschier commented Jul 6, 2026

Copy link
Copy Markdown
Member

What changed

The app release workflow now seeds draft GitHub releases with <!-- generated-by-yaak-releases --> instead of a placeholder changelog link.

Why

The website release tooling only replaces GitHub release bodies that are empty or already marked as generated. The previous changelog link looked like manual release notes, so release_ship_beta preserved it and skipped the generated notes update.

Impact

Future beta and stable release shipping can replace the draft release body with the website-formatted generated notes.

Validation

  • git diff --check -- .github/workflows/release-app.yml

No tags were created or changed.

@gschier gschier marked this pull request as ready for review July 6, 2026 16:54
@gschier gschier merged commit 2fee5ba into main Jul 6, 2026
7 checks passed
@gschier gschier deleted the codex/release-notes-placeholder branch July 6, 2026 16:54
@greptile-apps

greptile-apps Bot commented Jul 6, 2026

Copy link
Copy Markdown

Greptile Summary

This PR replaces the hardcoded changelog link in the Tauri release body with an HTML comment marker (<!-- generated-by-yaak-releases -->) so that the website's release tooling can identify and overwrite it with generated notes.

  • The old releaseBody value ([Changelog __VERSION__](https://yaak.app/blog/__VERSION__)) was mistaken for manual release notes by the release_ship_beta tool, which skipped replacing it; the new marker is the sentinel the tooling checks for.
  • The draft release will now appear to have a blank body in the GitHub UI until the downstream release-shipping step fills it in with formatted notes.

Confidence Score: 5/5

Safe to merge — the change touches only the draft release body placeholder and has no effect on build, signing, or artifact upload steps.

A single string is swapped in a with: block of the Tauri release action. The rest of the workflow is untouched, no secrets or conditionals are affected, and the new marker is inert until the downstream release-shipping tool reads it.

No files require special attention.

Important Files Changed

Filename Overview
.github/workflows/release-app.yml Single-line change: releaseBody updated from a Changelog URL template to an HTML comment sentinel marker; no logic, secret, or structural changes.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant GHA as GitHub Actions (release-app.yml)
    participant GHR as GitHub Releases
    participant RT as Website Release Tooling (release_ship_beta)

    GHA->>GHR: "Create draft release body: "<!-- generated-by-yaak-releases -->""
    Note over GHR: Draft visible with blank-looking body
    RT->>GHR: Read release body
    GHR-->>RT: "<!-- generated-by-yaak-releases -->"
    RT->>RT: Check: is body empty or marked as generated?
    Note over RT: Marker recognized
    RT->>GHR: Replace body with formatted generated notes
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant GHA as GitHub Actions (release-app.yml)
    participant GHR as GitHub Releases
    participant RT as Website Release Tooling (release_ship_beta)

    GHA->>GHR: "Create draft release body: "<!-- generated-by-yaak-releases -->""
    Note over GHR: Draft visible with blank-looking body
    RT->>GHR: Read release body
    GHR-->>RT: "<!-- generated-by-yaak-releases -->"
    RT->>RT: Check: is body empty or marked as generated?
    Note over RT: Marker recognized
    RT->>GHR: Replace body with formatted generated notes
Loading

Reviews (1): Last reviewed commit: "Use generated release notes placeholder" | Re-trigger Greptile

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