[fix] Add release notes summary to a file when it is too big

[unidevel]

This PR fixed the error when geneating release notes by adding the summary to a file with name release-notes-missing-<version>.md under presto root folder, release owner need to remove this file before the release notes PR is meges.

2026-03-31T15:32:30.556Z	INFO	main	com.facebook.presto.release.AbstractCommands	Finished running command: git remote get-url origin
2026-03-31T15:32:30.556Z	INFO	main	com.facebook.presto.release.tasks.GenerateReleaseNotesTask	origin url: https://github.com/unix280/presto, repo: unix280/presto
2026-03-31T15:32:31.214Z	INFO	main	com.facebook.airlift.bootstrap.LifeCycleManager	Life cycle stopping...
2026-03-31T15:32:31.219Z	INFO	main	com.facebook.airlift.bootstrap.LifeCycleManager	Life cycle stopped.
2026-03-31T15:32:31.219Z	ERROR	main	Bootstrap	Uncaught exception in thread main
java.lang.RuntimeException: GraphQL error: [{type=UNPROCESSABLE, path=[createPullRequest], locations=[{line=2, column=5}], message=Body is too long (maximum is 65536 characters)}]
	at com.facebook.presto.release.git.GithubGraphQlAction.githubApi(GithubGraphQlAction.java:236)
	at com.facebook.presto.release.git.GithubGraphQlAction.createPullRequest(GithubGraphQlAction.java:205)
	at com.facebook.presto.release.tasks.GenerateReleaseNotesTask.run(GenerateReleaseNotesTask.java:203)
	at com.facebook.presto.release.tasks.AbstractReleaseCommand.run(AbstractReleaseCommand.java:50)
	at com.facebook.presto.release.PrestoReleaseService.main(PrestoReleaseService.java:43)

Tested with:

1. Release action in presto-release-tools => https://github.com/unix280/presto-release-tools/actions/runs/23812204200/job/69401985641
2. Prepare release action in presto => https://github.com/unix280/presto/actions/runs/23812844511
3. Release notes PR => docs: Add release notes for 0.297 unix280/presto#52
4. Release notes missing list file => https://github.com/unix280/presto/blob/release-notes-0.297/release-notes-missing-0.297.md

[sourcery-ai]

Reviewer's Guide

Implements logic to handle GitHub PR body length limits for generated release notes by optionally writing the full summary to a versioned file and using a truncated body in the PR, and updates the release workflow to support mock publishing without failing the job.

Sequence diagram for generating release notes PR with summary file fallback

sequenceDiagram
    participant ReleaseService as PrestoReleaseService
    participant Task as GenerateReleaseNotesTask
    participant Git as GitClient
    participant FS as FileSystem
    participant GH as GithubGraphQlAction

    ReleaseService->>Task: run()
    Task->>Git: createBranch(release-notes-{version})
    Task->>Task: build releaseNotes
    Task->>Task: build releaseNotesSummary
    Task->>Task: fullSummary = releaseNotesSummary + RELEASE_NOTES_FOOTER

    alt fullSummary length > githubPrBodyLimit
        Task->>Task: build truncationMessage
        Task->>Task: compute availableSpace
        Task->>Task: truncatedSummary = releaseNotesSummary.substring(...)
        Task->>Task: prBody = truncatedSummary + RELEASE_NOTES_FOOTER + truncationMessage
        Note over Task,FS: summaryFileCreated = true
    else fullSummary within limit
        Task->>Task: prBody = fullSummary
        Note over Task,FS: summaryFileCreated = false
    end

    Task->>Git: checkout(branch release-notes-{version})
    Task->>FS: update RELEASE_NOTES_LIST_FILE

    alt summaryFileCreated is true
        Task->>FS: write release-notes-missing-{version}.md with fullSummary
    end

    Task->>Git: commit release notes changes
    Task->>Git: push origin release-notes-{version}

    Task->>GH: createPullRequest(base=master, head=origin:release-notes-{version}, title=docs: Add release notes for {version}, body=prBody)
    GH-->>Task: releaseNotesPullRequest URL
    Task-->>ReleaseService: done

Loading

Class diagram for updated GenerateReleaseNotesTask

classDiagram
    class GenerateReleaseNotesTask {
        - String releaseNotesSummary
        - String RELEASE_NOTES_FOOTER
        - GitClient git
        - Repository repository
        - String RELEASE_NOTES_LIST_FILE
        + void run()
        - void createReleaseNotesCommit(String version, String branch, String releaseNotes, Optional~String~ fullSummary)
    }

    class GitClient {
        + void checkout(Optional~String~ remote, Optional~String~ branch)
        + void push(String remote, String branch, boolean force)
    }

    class Repository {
        + String getOriginName()
    }

    class Optional~String~ {
        + boolean isPresent()
        + String get()
        + static Optional~String~ of(String value)
        + static Optional~String~ empty()
    }

    GenerateReleaseNotesTask --> GitClient : uses
    GenerateReleaseNotesTask --> Repository : uses
    GenerateReleaseNotesTask --> Optional~String~ : uses

Loading

File-Level Changes

Change	Details	Files
Handle oversized release notes by truncating the PR body and persisting the full summary to a versioned file when it exceeds GitHub limits.	Build a full release notes summary including the existing footer and compute its length against a conservative GitHub PR body limit. If the full summary exceeds the limit, construct a truncated PR body that fits within the limit and append an explanatory note with a link to the full summary file and deletion instructions. Introduce a boolean flag and Optional parameter to indicate when a full summary file should be created and pass this into the release notes commit creation method. Extend the release notes commit creation method to optionally write the full summary into a file named release-notes-missing-<version>.md at the repo root and log its creation.	presto-release-tools/src/main/java/com/facebook/presto/release/tasks/GenerateReleaseNotesTask.java
Update the release GitHub Actions workflow to allow mock publishing runs without failing the job on Maven deploy errors.	Wrap the Maven deploy step in a conditional that checks a MOCK_PUBLISHING GitHub Actions variable. When mock publishing is enabled, allow the Maven deploy command to fail while logging a message and continuing the workflow; otherwise, retain the original strict behavior.	.github/workflows/release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• The availableSpace calculation for the truncated summary can go negative if the truncation message + footer + buffer exceed githubPrBodyLimit, which would cause substring to throw; consider wrapping it in Math.max(0, ...) before using it.
• The relative link in truncationMessage (../blob/release-notes-%s/release-notes-missing-%s.md) may not resolve correctly from the PR body; it would be more robust to use an absolute GitHub URL built from the origin repo/branch or a simple filename reference without a relative path.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `availableSpace` calculation for the truncated summary can go negative if the truncation message + footer + buffer exceed `githubPrBodyLimit`, which would cause `substring` to throw; consider wrapping it in `Math.max(0, ...)` before using it.
- The relative link in `truncationMessage` (`../blob/release-notes-%s/release-notes-missing-%s.md`) may not resolve correctly from the PR body; it would be more robust to use an absolute GitHub URL built from the origin repo/branch or a simple filename reference without a relative path.

## Individual Comments

### Comment 1
<location path="presto-release-tools/src/main/java/com/facebook/presto/release/tasks/GenerateReleaseNotesTask.java" line_range="204-213" />
<code_context>
+        if (fullSummary.length() > githubPrBodyLimit) {
</code_context>
<issue_to_address>
**issue:** Guard against negative `availableSpace` when truncating the summary

If `truncationMessage.length() + RELEASE_NOTES_FOOTER.length() + 100` is greater than `githubPrBodyLimit`, `availableSpace` becomes negative, causing `substring(0, availableSpace)` to throw. Please clamp `availableSpace` at 0 (e.g., `Math.max(0, availableSpace)`) or short‑circuit to a minimal fallback body when `availableSpace <= 0`.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[unidevel]

@sourcery-ai review

[sourcery-ai]

Hey - I've left some high level feedback:

• The Markdown link in the truncation notice (../blob/release-notes-%s/release-notes-missing-%s.md) is unlikely to resolve correctly from a PR description; consider using a repo-relative path (e.g. /blob/release-notes-%s/...) or just referencing the filename without a link so users can reliably locate the file.
• When truncating releaseNotesSummary to fit the PR body limit, the substring is cut at an arbitrary character boundary; consider trimming at the last newline or word boundary within availableSpace to avoid broken Markdown and mid-word truncation in the rendered PR description.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The Markdown link in the truncation notice (`../blob/release-notes-%s/release-notes-missing-%s.md`) is unlikely to resolve correctly from a PR description; consider using a repo-relative path (e.g. `/blob/release-notes-%s/...`) or just referencing the filename without a link so users can reliably locate the file.
- When truncating `releaseNotesSummary` to fit the PR body limit, the substring is cut at an arbitrary character boundary; consider trimming at the last newline or word boundary within `availableSpace` to avoid broken Markdown and mid-word truncation in the rendered PR description.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[steveburnett]

LGTM!

Makes sense.

Note for the future, if relevant:
The summary states that the release owner must remove the release-notes-missing-<version>.md file before the release notes PR is merged. If we plan to keep this workaround for the future, suggest automating the file deletion as part of the release process.