Skip to content

Add GitHub release link as AMO release notes#9067

Merged
fregante merged 3 commits intomainfrom
copilot/add-summary-of-changes
Mar 10, 2026
Merged

Add GitHub release link as AMO release notes#9067
fregante merged 3 commits intomainfrom
copilot/add-summary-of-changes

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 10, 2026 •
edited
Loading

The "release notes" tab in Firefox's about:addons was empty after extension updates. This adds a release notes entry to each AMO submission containing a link to the corresponding GitHub release.

  • DAILY_VERSION exported as a job output from the Version job, making it available to downstream jobs
  • New step in Firefox CI job: writes amo-metadata.json with release_notes.en-US set to the GitHub release URL using the needs.Version.outputs.version context
  • Updated web-ext sign invocation: adds --amo-metadata /tmp/amo-metadata.json
- name: Create release notes
  run: echo "{\"release_notes\":{\"en-US\":\"https://github.com/${{ github.repository }}/releases/tag/${{ needs.Version.outputs.version }}\"}}" > /tmp/amo-metadata.json
- name: Upload build and source code
  run: npx web-ext@8 sign --channel listed --amo-metadata /tmp/amo-metadata.json

Test URLs

about:addons (after next release)

Screenshot

Empty tab before (highlighted in red):

Original prompt

This section details on the original issue you should resolve

<issue_title>Show summary of changes in update page in browser</issue_title>
<issue_description>### Description

When I update the WebExtension (using Firefox 148.0b15) I'd love to have at a glance the main changes without opening the GitHub release page. Example of the current update page (in German). The empty square in red is where the tab for changes should be:

Image

Would it be possible to add that to the Mozilla Add-On releases?

Thanks

Example URLs

about:addons</issue_description>

<agent_instructions>Add release notes to Mozilla Addon's version. The notes should just include a link to the GitHub release that is created in the next step. </agent_instructions>

Comments on the Issue (you are @copilot in this section)

@SunsetTechuila Related: https://github.com/fregante/ghatemplates/issues/17 @fregante The released notes are generated *after* we publish the version to AMO. And even then they're often tweaked. I don't want to have to manually update AMO's release notes if I make changes to GitHub's release.

What we can do is add a link to the GitHub release. This should be relatively easy to do. Let's ask copilot. </comment_new>

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

@fregante
Add GitHub release link as AMO release notes when publishing to Firefox
ae833a9 
Co-authored-by: fregante <1402241+fregante@users.noreply.github.com>
Copilot AI changed the title [WIP] Add summary of changes to update page Add GitHub release link as AMO release notes Mar 10, 2026
fregante
fregante approved these changes Mar 10, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@fregante fregante left a comment

Choose a reason for hiding this comment

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

@copilot LGTM after this change. Am I right?

.github/workflows/release.yml Outdated
- uses: actions/download-artifact@v4
- name: Create release notes
run: |
VERSION=$(jq -r '.version' artifact/manifest.json)
Copy link
Copy Markdown
Member

@fregante fregante Mar 10, 2026

Choose a reason for hiding this comment

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

The DAILY_VERSION env should already be available

Copy link
Copy Markdown
Contributor Author

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

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

Fixed in 5169c2a — exported DAILY_VERSION as a job output (needs.Version.outputs.version) and used that directly, removing the jq call.

@fregante fregante marked this pull request as ready for review March 10, 2026 14:08
@fregante fregante added the meta Related to Refined GitHub itself label Mar 10, 2026
@fregante
Use DAILY_VERSION job output instead of jq to get version
5169c2a 
Co-authored-by: fregante <1402241+fregante@users.noreply.github.com>
Copy link
Copy Markdown
Contributor Author

Copilot AI commented Mar 10, 2026

@copilot LGTM after this change. Am I right?

Yes, that's correct — DAILY_VERSION is set as a workflow env by daily-version-action, so it can be captured as a job output and referenced in downstream jobs via needs.Version.outputs.version. Updated in 5169c2a.

@fregante fregante enabled auto-merge (squash) March 10, 2026 14:15
@fregante
Copy link
Copy Markdown
Member

fregante commented Mar 10, 2026

YOLO

@fregante fregante merged commit e9fb8d8 into main Mar 10, 2026
14 checks passed
@SunsetTechuila SunsetTechuila deleted the copilot/add-summary-of-changes branch March 11, 2026 02:28
@SunsetTechuila SunsetTechuila mentioned this pull request Mar 11, 2026
Merged
@jman-schief
Copy link
Copy Markdown

jman-schief commented Apr 7, 2026

@fregante I am unsure if #8994 is fixed. Where should the release notes be visible? I am installing version 26.4.4 and I don't see any link to the release notes.

I was expecting the release notes link to be visibile in a separate tab.

Any hint?

thanks

@fregante
Copy link
Copy Markdown
Member

fregante commented Apr 7, 2026

Issue reopened

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@fregante fregante fregante approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@fregante fregante

Copilot code review Copilot

Labels

meta Related to Refined GitHub itself

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Show summary of changes in update page in browser

3 participants

@fregante @jman-schief