fix: release email links #9690

Merged

mfenniak merged 2 commits from VewDev/forgejo:fix-release-email-link into forgejo 2025-10-16 16:12:37 +02:00

Conversation 11 Commits 2 Files changed 1 +2 -2

VewDev commented 2025-10-15 00:19:27 +02:00

Contributor

Copy link

Use correct links (instance.com/owner/repo/archive/tag.extension) links in release emails, instead of the (/owner/repo) incomplete links.

I have manually tested this. Below is a screenshot of an email sent with the new version having correct hyperlinks.

Fixes #9482

Checklist

The contributor guide contains information that will be helpful to first time contributors. There also are a few conditions for merging Pull Requests in Forgejo repositories. You are also welcome to join the Forgejo development chatroom.

Tests

• I added test coverage for Go changes...
  • in their respective *_test.go for unit tests.
  • in the tests/integration directory if it involves interactions with a live Forgejo server.
• I added test coverage for JavaScript changes...
  • in web_src/js/*.test.js if it can be unit tested.
  • in tests/e2e/*.test.e2e.js if it requires interactions with a live Forgejo server (see also the developer guide for JavaScript testing).

Manual test screenshots

Documentation

• I created a pull request to the documentation to explain to Forgejo users how to use this change.
• I did not document these changes and I do not expect someone else to do it.

Release notes

• I do not want this change to show in the release notes.
• I want the title to show in the release notes with a link to this pull request.
• I want the content of the release-notes/<pull request number>.md to be be used for the release notes instead of the title.

Release notes

• Bug fixes
  • PR: release email links

Use correct links (instance.com/owner/repo/archive/tag.extension) links in release emails, instead of the (/owner/repo) incomplete links. I have manually tested this. Below is a screenshot of an email sent with the new version having correct hyperlinks. Fixes #9482 ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests - I added test coverage for Go changes... - [ ] in their respective `*_test.go` for unit tests. - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). #### Manual test screenshots  ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [x] I did not document these changes and I do not expect someone else to do it. ### Release notes - [ ] I do not want this change to show in the release notes. - [x] I want the title to show in the release notes with a link to this pull request. - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title. <!--start release-notes-assistant--> ## Release notes <!--URL:https://codeberg.org/forgejo/forgejo--> - Bug fixes - [PR](https://codeberg.org/forgejo/forgejo/pulls/9690): <!--number 9690 --><!--line 0 --><!--description cmVsZWFzZSBlbWFpbCBsaW5rcw==-->release email links<!--description--> <!--end release-notes-assistant-->

image.png

37 KiB

VewDev added the

test

needed

label 2025-10-15 00:19:27 +02:00

VewDev commented 2025-10-15 00:28:53 +02:00

Author

Contributor

Copy link

Do I need to add tests for this?

Do I need to add tests for this?

mfenniak commented 2025-10-15 03:17:54 +02:00

Member

Copy link

@VewDev If you can confirm that you've performed manual testing and include a screenshot in your PR description (eg. mouse over the link in an email, something like that), I'd be comfortable without any automated testing for this. 👍

@VewDev If you can confirm that you've performed manual testing and include a screenshot in your PR description (eg. mouse over the link in an email, something like that), I'd be comfortable without any automated testing for this. 👍

VewDev commented 2025-10-15 22:46:40 +02:00

Author

Contributor

Copy link

I have manually confirmed this now uses full hyperlinks

	<p>
		---
		<br>
		Downloads:
		<ul>
		=09
			<li>
				<a href=3D"http://localhost:3000/test/test/releases/tag/asd/archive/asd=
.zip" rel=3D"nofollow"><strong>Source Code (ZIP)</strong></a>
			</li>
			<li>
				<a href=3D"http://localhost:3000/test/test/releases/tag/asd/archive/asd=
.tar.gz" rel=3D"nofollow"><strong>Source Code (TAR.GZ)</strong></a>
			</li>
		=09
		=09
		</ul>
	</p>

This is the content of the HTML email with the new update.

However, while testing this, I found a related bug. The links are "correct" hyperlinks, but they are broken, there's nothing at that address.

I am going to upload a new commit to fix this second problem.

I have manually confirmed this now uses full hyperlinks ```html <p> --- <br> Downloads: <ul> =09 <li> <a href=3D"http://localhost:3000/test/test/releases/tag/asd/archive/asd= .zip" rel=3D"nofollow"><strong>Source Code (ZIP)</strong></a> </li> <li> <a href=3D"http://localhost:3000/test/test/releases/tag/asd/archive/asd= .tar.gz" rel=3D"nofollow"><strong>Source Code (TAR.GZ)</strong></a> </li> =09 =09 </ul> </p> ``` This is the content of the HTML email with the new update. However, while testing this, I found a related bug. The links are "correct" hyperlinks, but they are broken, there's nothing at that address. I am going to upload a new commit to fix this second problem.

VewDev changed title from WIP: fix: use full links in release emails to WIP: fix: release email links 2025-10-15 22:54:04 +02:00

VewDev force-pushed fix-release-email-link from 390fa9665d to 63c2ce3de1 2025-10-15 23:35:11 +02:00 Compare

VewDev commented 2025-10-15 23:35:55 +02:00

Author

Contributor

Copy link

Okay so the Release object already had TarURL and ZipURL properties, and building a hyperlink in the template was not needed at all.

I have changed my commit to use those properties, and now the links properly reference the files.

Okay so the Release object already had TarURL and ZipURL properties, and building a hyperlink in the template was not needed at all. I have changed my commit to use those properties, and now the links properly reference the files.

VewDev changed title from WIP: fix: release email links to fix: release email links 2025-10-15 23:37:52 +02:00

VewDev requested reviews from Gusted, Beowulf 2025-10-15 23:37:52 +02:00

mfenniak added

test

manual

and removed

test

needed

labels 2025-10-15 23:55:40 +02:00

mfenniak commented 2025-10-15 23:56:24 +02:00

Member

Copy link

@VewDev Just has a minor formatting consistency issue being reported by the automated checks: https://codeberg.org/forgejo/forgejo/actions/runs/110762/jobs/0

@VewDev Just has a minor formatting consistency issue being reported by the automated checks: https://codeberg.org/forgejo/forgejo/actions/runs/110762/jobs/0

VewDev added 1 commit 2025-10-16 08:21:14 +02:00

style: fix formatting consistency issues 9489634c1c

VewDev commented 2025-10-16 08:29:16 +02:00

Author

Contributor

Copy link

@mfenniak I have added a new commit fixing the formatting issue and all checks are apparently passing now

@mfenniak I have added a new commit fixing the formatting issue and all checks are apparently passing now

mfenniak approved these changes 2025-10-16 16:12:15 +02:00

mfenniak merged commit 5b13c6e024 into forgejo 2025-10-16 16:12:37 +02:00

mfenniak referenced this pull request from a commit 2025-10-16 16:12:46 +02:00

fix: release email links (#9690)

mfenniak added the

backport/v13.0/forgejo

label 2025-10-16 16:13:04 +02:00

mfenniak commented 2025-10-16 16:13:38 +02:00

Member

Copy link

@VewDev Thanks for fixing this!

@VewDev Thanks for fixing this!

❤️ 1

forgejo-release-notes-assistant added this to the Forgejo v14.0.0 milestone 2025-10-16 16:16:59 +02:00

forgejo-backport-action referenced this pull request 2025-10-16 16:18:15 +02:00

[v13.0/forgejo] fix: release email links #9714

forgejo-backport-action referenced this pull request from a commit 2025-10-16 16:18:22 +02:00

fix: release email links (#9690)

mfenniak added the

bug

confirmed

worth a release-note

labels 2025-10-16 16:19:41 +02:00

forgejo-backport-action commented 2025-10-16 16:20:44 +02:00

Member

Copy link

The backport to v13.0/forgejo failed. Check the latest run for more details.

The backport to `v13.0/forgejo` failed. Check the latest run for more details.

forgejo-backport-action commented 2025-10-16 16:20:48 +02:00

Member

Copy link

The backport to v13.0/forgejo failed. Check the latest run for more details.

The backport to `v13.0/forgejo` failed. Check the latest run for more details.

forgejo-release-notes-assistant commented 2025-10-16 16:21:18 +02:00

Member

Copy link

Where does that come from?

The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `release-notes/9690.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference.

This message and the release notes originate from a call to the release-notes-assistant.

@@ -33,2 +33,10 @@
 - [x] I want the title to show in the release notes with a link to this pull request.
 - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title.
+
+<!--start release-notes-assistant-->
+
+## Release notes
+<!--URL:https://codeberg.org/forgejo/forgejo-->
+- Bug fixes
+  - [PR](https://codeberg.org/forgejo/forgejo/pulls/9690): <!--number 9690 --><!--line 0 --><!--description cmVsZWFzZSBlbWFpbCBsaW5rcw==-->release email links<!--description-->
+<!--end release-notes-assistant-->

Release notes

• Bug fixes
  • PR: release email links

<details> <summary>Where does that come from?</summary> The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `release-notes/9690.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference. This message and the release notes originate from a call to the [release-notes-assistant](https://code.forgejo.org/forgejo/release-notes-assistant). ```diff @@ -33,2 +33,10 @@ - [x] I want the title to show in the release notes with a link to this pull request. - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title. + +<!--start release-notes-assistant--> + +## Release notes +<!--URL:https://codeberg.org/forgejo/forgejo--> +- Bug fixes + - [PR](https://codeberg.org/forgejo/forgejo/pulls/9690): <!--number 9690 --><!--line 0 --><!--description cmVsZWFzZSBlbWFpbCBsaW5rcw==-->release email links<!--description--> +<!--end release-notes-assistant--> ``` </details> <!--start release-notes-assistant--> ## Release notes <!--URL:https://codeberg.org/forgejo/forgejo--> - Bug fixes - [PR](https://codeberg.org/forgejo/forgejo/pulls/9690): <!--number 9690 --><!--line 0 --><!--description cmVsZWFzZSBlbWFpbCBsaW5rcw==-->release email links<!--description--> <!--end release-notes-assistant-->

mfenniak referenced this pull request from a commit 2025-10-16 18:58:59 +02:00

[v13.0/forgejo] fix: release email links (#9714)

jasewolf referenced this pull request from a commit 2025-11-16 14:02:47 +01:00

v13.0.2

alberic89 referenced this pull request from a commit 2026-02-23 18:42:55 +01:00

fix: release email links (#9690)

Sign in to join this conversation.

Reviewers

No reviewers

Gusted

Beowulf

mfenniak

Labels

Clear labels   

arch

riscv64

Archived

  

backport/v1.19

Scheduled for backport to Forgejo v1.19

Archived

  

backport/v1.20

Scheduled for backport to Forgejo v1.20

Archived

  

backport/v1.21/forgejo

Scheduled for backport to Forgejo v1.21

Archived

  

backport/v10.0/forgejo

Automated backport to v10.0

Archived

  

backport/v11.0/forgejo

Automated backport to v11.0

  

backport/v12.0/forgejo

Automated backport to v12.0

Archived

  

backport/v13.0/forgejo

Automated backport to v13.0

Archived

  

backport/v14.0/forgejo

Automated backport to v14.0

Archived

  

backport/v15.0/forgejo

Automated backport to v15.0

  

backport/v7.0/forgejo

Scheduled for backport to Forgejo v7.0

Archived

  

backport/v8.0/forgejo

Scheduled for backport to Forgejo v8.0

Archived

  

backport/v9.0/forgejo

Scheduled for backport to Forgejo v9.0

Archived

  

breaking

The release containing this change is not backward compatible

  

bug

Something is not working

Archived

  

bug

confirmed

it can be reproduced

  

bug

duplicate

bug has already been reported in the Forgejo tracker

  

bug

needs-more-info

the information provided does not contain enough details

  

bug

new-report

bug has just been reported and need triage (default label on issue creation)

  

bug

reported-upstream

bug cannot be fixed within Forgejo easily, it has been reported upstream

  

code/actions

Forgejo Actions feature

  

code/api

API

  

code/auth

Forgejo Authentication

  

code/auth/faidp

Forgejo as Identity Provider (in OAuth/OIDC flow)

  

code/auth/farp

Forgejo as Relying Party / Client (in OAuth/OIDC flow)

  

code/email

Everything related to email in Forgejo

  

code/federation

Federation

  

code/git

Related to the Git backend in Forgejo

  

code/migrations

Migration between Git forges (i.e. for GitHub, GitLab, Gitea, Forgejo, etc.). NOT for database migrations.

  

code/packages

Forgejo package and container registry

  

code/wiki

  

database

MySQL

https://www.mysql.com/

  

database

PostgreSQL

https://www.postgresql.org/

  

database

SQLite

https://sqlite.org/

  

dependency-upgrade

https://codeberg.org/forgejo/forgejo/issues/2779

  

dependency

Chi

https://github.com/go-chi/chi/

Archived

  

dependency

Chroma

https://github.com/alecthomas/chroma/

Archived

  

dependency

F3

https://f3.forgefriends.org/

  

dependency

ForgeFed

https://forgefed.org

  

dependency

garage

https://git.deuxfleurs.fr/Deuxfleurs/garage

  

dependency

Gitea

https://github.com/go-gitea/gitea

Archived

  

dependency

Golang

https://go.dev/

  

Discussion

  

duplicate

This issue or pull request already exists

  

enhancement/feature

New feature

  

forgejo/accessibility

Accessibility (a11y)

  

forgejo/branding

Branding (logo, name, tagline etc.)

  

forgejo/ci

Forgejo Actions CI configuration

  

forgejo/commit-graph

The commit graph feature and page.

  

forgejo/documentation

  

forgejo/furnace cleanup

Keeping Forgejo in sync with its dependencies and contributing back to them

Archived

  

forgejo/i18n

t9n/translation, l10n/localization, and i18n/internationalization of Forgejo

  

forgejo/interop

Interoperability with other services: Webhooks, bridges, integrations

  

forgejo/moderation

Moderation

  

forgejo/privacy

Privacy first

  

forgejo/release

Release management

  

forgejo/scaling

Performance and scaling

  

forgejo/security

Security (please disclose responsibly)

  

forgejo/ui

User interface

  

Gain

High

User research provides indicators that this would be good to have, interested contributors are encouraged to pick this.

  

Gain

Nice to have

This is likely worth having, but the assumption is not backed by user research data (it might benefit a small amount of users only.) Unlikely to receive much attention, but feel free to pick.

  

Gain

Undefined

Not enough information to assess the request's benefits. This issue may be closed if no gain is established: You can help by giving us more input.

  

Gain

Very High

User research indicates that this is an important improvement for Forgejo users. Contributions very welcome!

  

good first issue

Optimal for first-timers! Make sure to look for further explanations and ask for help if needed. If you want, you can consider the person who added this label as a point of contact.

  

i18n/backport-stable

This PR needs to be backported to stable branch of Forgejo safely and manually, using a migration script.

  

impact

large

Large impact: Potential data loss, many users affected, major degradation in UX.

  

impact

medium

Medium impact: Several users affected, degradation in UX, workarounds might be available but inconvenient.

  

impact

small

Small impact: No data loss, workarounds might be available, affects few users.

  

impact

unknown

Report was not yet triaged to assess impact.

  

Incompatible license

This pull request contains changes that are not (yet) compatible with the current Forgejo license

  

issue

closed

The issue was resolved in the repository of the dependency

  

issue

do-not-exist-yet

An issue should be created in the respository of the dependency

  

issue

open

An open issue exists in the upstream repository of the dependency

  

manual test

Pull requests that have been merged with a manual test

Archived

  

Manually tested during feature freeze

The manual test instructions were followed

  

OS

FreeBSD

Specific to the FreeBSD Operating System

  

OS

Linux

Specific to (GNU/)Linux Operating Systems

  

OS

macOS

Specific to the MacOS Operating System

  

OS

Windows

Specific to the Windows Operating System

  

problem

A user report about a problem. Needs to be triaged to find potential solutions.

  

QA

  

regression

found in the version of the milestone and not before

  

release blocker

Issues that must be fixed before the release can be published

  

Release Cycle

Feature Freeze

Only bug fixes with automated tests (except for CSS/JavaScript)

  

release-blocker

v7.0

Issues that must be fixed before Forgejo v7.0 can be released 17 April 2024

Archived

  

release-blocker

v7.0.1

Issues that must be fixed before Forgejo v7.0.1 can be released

Archived

  

release-blocker

v7.0.2

Issues that must be fixed before Forgejo v7.0.2 can be released

Archived

  

release-blocker

v7.0.3

Issues that must be fixed before Forgejo v7.0.3 can be released

Archived

  

release-blocker

v7.0.4

Issues that must be fixed before Forgejo v7.0.4 can be released

Archived

  

release-blocker

v8.0.0

Issues that must be fixed before Forgejo v8.0.0 can be released

Archived

  

release-blocker/v9.0.0

Issues that must be fixed before Forgejo v9.0.0 can be released

Archived

  

run-all-playwright-tests

Add this label to a PR to run all playwright tests manually.

  

run-end-to-end-tests

Trigger additional tests on the PR when it is ready to be merged

  

stage

2-research

Needs research to moe on.

  

stage

3-design

Needs design to move on

  

stage

4-implementation

This is actionable and waits for implementation

  

test

manual

manual testing has been documented

  

test

needed

test should be added

  

test

needs-help

help needed to add a test

  

test

not-needed

no additional test is needed

  

test

present

test has been added

  

untested

Pull requests that have been merged with no test and submitted as is to the dependency where they belong

Archived

  

User research - time-tracker

Time tracking feature for issues and the JS stopwatch.

  

valuable code

This PR was closed because the implementation is incomplete

  

worth a release-note

Add this PR to the release notes

  

User research - Accessibility

Requires input about accessibility features, likely involves user testing.

  

User research - Blocked

Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.

  

User research - Community

Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.

  

User research - Config (instance)

Instance-wide configuration, authentication and other admin-only needs.

  

User research - Errors

How to deal with errors in the application and write helpful error messages.

  

User research - Filters

How filter and search is being worked with.

  

User research - Future backlog

The issue might be inspiring for future design work.

  

User research - Git workflow

AGit, fork-based and new Git workflow, PR creation etc

  

User research - Labels

Active research about Labels

  

User research - Moderation

Moderation Featuers for Admins are undergoing active User Research

  

User research - Needs input

Use this label to let the User Research team know their input is requested.

  

User research - Notifications/Dashboard

Research on how users should know what to do next.

  

User research - Rendering

Text rendering, markup languages etc

  

User research - Repo creation

Active research about the New Repo dialog.

  

User research - Repo units

The repo sections, disabling them and the "Add more" button.

  

User research - Security

  

User research - Settings (in-app)

How to structure in-app settings in the future?

No labels

arch

riscv64

backport/v1.19

backport/v1.20

backport/v1.21/forgejo

backport/v10.0/forgejo

backport/v11.0/forgejo

backport/v12.0/forgejo

backport/v13.0/forgejo

backport/v14.0/forgejo

backport/v15.0/forgejo

backport/v7.0/forgejo

backport/v8.0/forgejo

backport/v9.0/forgejo

breaking

bug

bug

confirmed

bug

duplicate

bug

needs-more-info

bug

new-report

bug

reported-upstream

code/actions

code/api

code/auth

code/auth/faidp

code/auth/farp

code/email

code/federation

code/git

code/migrations

code/packages

code/wiki

database

MySQL

database

PostgreSQL

database

SQLite

dependency-upgrade

dependency

Chi

dependency

Chroma

dependency

F3

dependency

ForgeFed

dependency

garage

dependency

Gitea

dependency

Golang

Discussion

duplicate

enhancement/feature

forgejo/accessibility

forgejo/branding

forgejo/ci

forgejo/commit-graph

forgejo/documentation

forgejo/furnace cleanup

forgejo/i18n

forgejo/interop

forgejo/moderation

forgejo/privacy

forgejo/release

forgejo/scaling

forgejo/security

forgejo/ui

Gain

High

Gain

Nice to have

Gain

Undefined

Gain

Very High

good first issue

i18n/backport-stable

impact

large

impact

medium

impact

small

impact

unknown

Incompatible license

issue

closed

issue

do-not-exist-yet

issue

open

manual test

Manually tested during feature freeze

OS

FreeBSD

OS

Linux

OS

macOS

OS

Windows

problem

QA

regression

release blocker

Release Cycle

Feature Freeze

release-blocker

v7.0

release-blocker

v7.0.1

release-blocker

v7.0.2

release-blocker

v7.0.3

release-blocker

v7.0.4

release-blocker

v8.0.0

release-blocker/v9.0.0

run-all-playwright-tests

run-end-to-end-tests

stage

2-research

stage

3-design

stage

4-implementation

test

manual

test

needed

test

needs-help

test

not-needed

test

present

untested

User research - time-tracker

valuable code

worth a release-note

User research - Accessibility

User research - Blocked

User research - Community

User research - Config (instance)

User research - Errors

User research - Filters

User research - Future backlog

User research - Git workflow

User research - Labels

User research - Moderation

User research - Needs input

User research - Notifications/Dashboard

User research - Rendering

User research - Repo creation

User research - Repo units

User research - Security

User research - Settings (in-app)

Milestone

Clear milestone

No items

No milestone

Forgejo v14.0.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

4 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

forgejo/forgejo!9690

No description provided.