Skip to content

fix: auto-changelog improvements to prepare for AI-powered release workflows in MetaMask clients - #127

Merged
HowardBraham merged 4 commits into
mainfrom
changelog-ai
Oct 22, 2026
Merged

HowardBraham merged 4 commits into
mainfrom
changelog-ai

Conversation

@HowardBraham

@HowardBraham HowardBraham commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Adds the following five improvements to auto-changelog, to prepare for AI-powered release workflows in MetaMask clients:

  • Uses the original PR from a hard-wrapped Runway cherry-pick body
    • Example: - bump: update a dependency cp-13.4\n4.0\n(#45299)
  • Repairs a Markdown link that accidentally splits a word
    • Example: CHANGELOG entry: f[ix: swap source amount becomes undefined](https://github.com/MetaMask/metamask-extension/pull/45469#top)
  • Guard against CHANGELOG entry: null (reason) and similar
    • Example: CHANGELOG entry: null (dev tooling only)
  • Keeps an authored entry when the PR has a no-changelog label
  • Uses the trailing squash-merge PR reference when a commit subject includes
    both an original PR and its own PR
    • Example: chore: cherry-pick revert a feature (#37564) (#37790) now
      links to #37790, rather than incorrectly linking to #37564

@HowardBraham HowardBraham self-assigned this Oct 22, 2026
@HowardBraham
HowardBraham requested a review from a team as a code owner October 22, 2026 19:38
@HowardBraham
HowardBraham deployed to default-branch October 22, 2026 19:38 — with GitHub Actions Active
Comment thread packages/auto-changelog/CHANGELOG.md Outdated

### Fixed

- Improvements to prepare for AI (#127)

@mcmire mcmire Oct 22, 2026 •

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.

What do you think about using imperative tense and using a link for the PR to match the rest of the changelog?

Also, what are your thoughts on being more descriptive about what the improvements are? And how exactly are we preparing for AI, what does that mean?

Taking a guess, maybe something like this?

Suggested change
- Improvements to prepare for AI (#127)
- Improve populating changelogs from commits/PRs to prepare for AI-powered release workflows in MetaMask clients ([#127](https://github.com/MetaMask/release-tools/pull/127))
- Handle extracting the PR number from a Runway-generated cherry-pick commit subject even when the subject has been hard-wrapped
- Don't skip a PR that has a non-empty `CHANGELOG entry:` line even when it also has a `no-changelog` label
- Handle parsing the PR number from a malformed link

});

it('keeps an authored entry when the PR has a no-changelog label', async () => {
nock.cleanAll();

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.

We need to automatically set up Nock to clean all mocks after each test like in other repos so we don't have to do this kind of bookkeeping. Oh well...

if (!github) {
await initOctoKit();
}
await initOctoKit();

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.

Would this mean each time getPrLabels is called, we make a new instance of Octokit? Is that desirable?

@HowardBraham HowardBraham changed the title fix: auto-changelog improvements to prepare for AI fix: auto-changelog improvements to prepare for AI-powered release workflows in MetaMask clients Oct 22, 2026
- suite-level nock.cleanAll() calls
- cached Octokit initialization
mcmire
mcmire previously approved these changes Oct 22, 2026

@mcmire mcmire left a comment

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.

LGTM.

@HowardBraham
HowardBraham added this pull request to the merge queue Oct 22, 2026
Merged via the queue into main with commit ff39da2 Oct 22, 2026
54 checks passed
@HowardBraham
HowardBraham deleted the changelog-ai branch October 22, 2026 22:11
JadeCong pushed a commit to CloudEngineHub/metamask-extension that referenced this pull request Oct 29, 2026
…MetaMask#47463)

## **Description**

This is the very last step in a chain of PRs to turn on fully-autonomous
CHANGELOG generation in Extension.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

### Previous PRs in the chain

#### release-tools/auto-changelog
MetaMask/release-tools#127
MetaMask/release-tools#130

#### github-tools
MetaMask/github-tools#300
MetaMask/github-tools#301
MetaMask/github-tools#303

<!--## **Manual testing steps**
## **Screenshots/Recordings**
## **Pre-merge author checklist**
## **Pre-merge reviewer checklist**-->

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Workflow-only change that adds a CI secret env var and removes an
action input; no runtime extension code or user-facing behavior changes.
> 
> **Overview**
> Turns on the **AI changelog proofreader** for release changelog
automation by passing **`AI_ANALYZER_LITELLM_KEY`** into the
`update-release-changelog` GitHub Action (same LiteLLM secret pattern as
other AI workflows).
> 
> Also **drops the explicit `previous-version-ref: 'null'`** input so
previous-version resolution is handled by the updated action rather than
being hard-coded in this repo.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
c801241. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
darkwing pushed a commit to darkwing/metamask-mobile that referenced this pull request Oct 29, 2026
…MetaMask#38444)

## **Description**

This is the very last step in a chain of PRs to turn on fully-autonomous
CHANGELOG generation in Mobile.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

### Previous PRs in the chain

#### release-tools/auto-changelog
MetaMask/release-tools#127
MetaMask/release-tools#130

#### github-tools
MetaMask/github-tools#300
MetaMask/github-tools#301
MetaMask/github-tools#303

<!--## **Manual testing steps**
## **Screenshots/Recordings**
## **Pre-merge author checklist**
## **Pre-merge reviewer checklist**-->

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes how release and OTA hotfix changelogs are produced in CI;
misconfiguration could break changelog PRs or tags, though behavior is
intended to match the removed script via github-tools v1.
> 
> **Overview**
> Mobile release changelog automation no longer runs the local
**`run-update-release-changelog-mobile.sh`** wrapper or manual
**github-tools** checkout, Node setup, and **`yarn`** steps.
**`create-release-pr.yml`** (OTA hotfix path) and
**`update-release-changelog.yml`** now call
**`MetaMask/github-tools/.github/actions/update-release-changelog@v1`**,
which owns branch checkout, version derivation from **`release/X.Y.Z`**
/ **`release/X.Y.Z-ota`**, and concurrent Runway updates on the release
branch.
> 
> This PR also threads **`AI_ANALYZER_LITELLM_KEY`** from
**`auto-create-release-pr.yml`** into **`create-release-pr.yml`** as an
optional reusable-workflow secret and passes it into both changelog
action steps so the new AI changelog proofreader can run during
autonomous **`CHANGELOG.md`** generation.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
1abeae5. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Co-authored-by: howard <howard@example.com>
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.

2 participants