Relative markdown links in code blocks are resolved against raw GitHub URL

[D-N91]

System Health details

System Information

version	core-2026.4.0
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	aarch64
user	root
virtualenv	false
python_version	3.14.2
os_name	Linux
os_version	6.12.47-haos-raspi
arch	aarch64
timezone	Europe/Zurich
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	4964
Installed Version	2.0.5
Stage	running
Available Repositories	2989
Downloaded Repositories	36

Home Assistant Cloud

logged_in	true
subscription_expiration	31. Juli 2026 um 02:00
relayer_connected	true
relayer_region	eu-central-1
remote_enabled	true
remote_connected	true
alexa_enabled	false
google_enabled	true
cloud_ice_servers_enabled	true
remote_server	eu-central-1-10.ui.nabu.casa
certificate_status	ready
instance_id	dcbda37128344df7a420920c47dff2a7
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 17.1
update_channel	stable
supervisor_version	supervisor-2026.03.2
agent_version	1.8.1
docker_version	29.1.3
disk_total	234.0 GB
disk_used	26.5 GB
nameservers	192.168.1.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	rpi5-64
supervisor_api	ok
version_api	ok
installed_addons	Mosquitto broker (6.5.2), Zigbee2MQTT (2.9.2-1), Matter Server (8.3.0), OpenCCU (3.85.7.20260131), Whisper (3.1.0), Piper (2.2.2), openWakeWord (2.1.0), Frigate (Full Access) (0.17.1), Glances (0.21.1), Advanced SSH & Web Terminal (23.0.4), Studio Code Server (6.0.1), File editor (5.8.0), Home Assistant Google Drive Backup (0.112.1)

Dashboards

dashboards	5
resources	28
views	8
mode	storage

Network Configuration

adapters	lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), vethef2c1dd (disabled), veth8e231b2 (disabled), veth7bcf6c5 (disabled), vethfc4ea92 (disabled), veth8721b70 (disabled), veth135b3d9 (disabled), veth46dc339 (disabled), veth4076f92 (disabled), veth77691ee (disabled), veth32e71dd (disabled), vetha29f53e (disabled), veth2bb5c9f (disabled), vethba62a30 (disabled), veth900403a (disabled), veth1381417 (disabled), veth72944c9 (disabled)
ipv4_addresses	lo (127.0.0.1/8), end0 (192.168.1.110/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vethef2c1dd (), veth8e231b2 (), veth7bcf6c5 (), vethfc4ea92 (), veth8721b70 (), veth135b3d9 (), veth46dc339 (), veth4076f92 (), veth77691ee (), veth32e71dd (), vetha29f53e (), veth2bb5c9f (), vethba62a30 (), veth900403a (), veth1381417 (), veth72944c9 ()
ipv6_addresses	lo (::1/128), end0 (fda1:9876:60d1:8900:b2f4:7ed5:7ebb:951c/64, fe80::562b:16bd:2b6c:b1a3/64), docker0 (fe80::90:58ff:fe1e:1b75/64), hassio (fe80::f073:7ff:fe3f:95a/64), vethef2c1dd (fe80::6857:c1ff:fede:f49c/64), veth8e231b2 (fe80::9412:d8ff:fe9d:ba85/64), veth7bcf6c5 (fe80::8829:caff:fe9c:7a1e/64), vethfc4ea92 (fe80::890:55ff:fe90:5068/64), veth8721b70 (fe80::3472:a0ff:fe46:e68c/64), veth135b3d9 (fe80::4ce3:13ff:fe3c:be8e/64), veth46dc339 (fe80::2072:8fff:fecd:7d31/64), veth4076f92 (fe80::ccb5:f8ff:fe9e:89da/64), veth77691ee (fe80::c014:1dff:fed5:5d52/64), veth32e71dd (fe80::9834:ccff:fe44:1f08/64), vetha29f53e (fe80::b06a:bbff:fe4b:bc4c/64), veth2bb5c9f (fe80::acb7:a7ff:fed4:4ec7/64), vethba62a30 (fe80::441b:9ff:feca:b73d/64), veth900403a (fe80::7478:d4ff:fe8c:e84c/64), veth1381417 (fe80::6822:a5ff:feb2:8b35/64), veth72944c9 (fe80::f44d:e4ff:fe21:8365/64)
announce_addresses	192.168.1.110, fda1:9876:60d1:8900:b2f4:7ed5:7ebb:951c, fe80::562b:16bd:2b6c:b1a3

Recorder

oldest_recorder_run	24. März 2026 um 15:52
current_recorder_run	2. April 2026 um 02:01
estimated_db_size	314.86 MiB
database_engine	sqlite
database_version	3.49.2

Checklist

• I'm running the newest version of HACS https://github.com/hacs/integration/releases/latest
• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• I have read https://hacs.xyz/docs/help/issues/
• This issue is related to the backend (integration part) of HACS.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This is a bug and not a feature request.
• This issue is not a duplicate issue of currently open or issues pending release.

Describe the issue

When viewing a repository README inside HACS, relative links that appear inside YAML code blocks (e.g. /config/entities) are being resolved against the raw.githubusercontent.com base URL instead of being preserved as-is.

Expected behavior: Links inside fenced code blocks should be rendered as plain text and not be processed or resolved at all.

Actual behavior: A relative link like Check Entities inside a ```yaml code block gets resolved to https://raw.githubusercontent.com////config/entities, which returns a 404.

Impact: Users who copy card templates containing HA internal deep-links from the HACS README view end up with broken URLs in their dashboard cards.

Example: D-N91/home-assistant-global-health-score#43

Reproduction steps

1. Open any HACS integration that has a README with relative markdown links inside YAML code blocks
2. Copy the YAML from the HACS-rendered README
3. Paste it into an HA markdown card
4. Click the link — it navigates to raw.githubusercontent.com instead of the local HA path

Debug logs

this problem accured at another HA instance, i do not have log files.

Diagnostics dump

same as debug logs, i dont have any

[hacs-bot]

Thank you for opening an issue in the HACS.

Before proceeding, please verify the following:

Select the correct issue template:
HACS provides different templates for different types of bugs. Choosing the right template ensures you're asked the right questions and helps route your bug appropriately.

Complete the ENTIRE issue template:
Make sure you've read the issue guidelines and filled out every single field in the issue template, even if some fields seem unrelated to your specific situation.

Fill out everything, even if it seems unnecessary:
Don't skip fields because they "don't seem relevant" to your bug. The template asks for specific information because:

• Problems often have unexpected causes that surface through "unrelated" details
• What seems unrelated to you might be the key to solving your bug
• Incomplete information requires follow-up questions, delaying resolution
• The template is designed based on years of troubleshooting experience
• Missing information forces those helping to make assumptions, which can lead to wrong solutions

Issues with incomplete templates take significantly longer to resolve or may be closed without resolution.

If you're experiencing a similar bug:
If your bug is identical to an existing one, please:

• Add a 👍 reaction to the original issue description
• Subscribe to notifications on that issue to stay updated
• Do not add comments like "same here", "I have this too", or "+1"

Adding duplicate comments creates noise and makes it harder to track and resolve issues. Reactions help prioritize issues based on how many users are affected.

Getting help:
If you need assistance filling out the template or understanding your issue:

• Issue Guidelines - Detailed instructions for reporting issues
• HACS Discord - Community support and real-time help

What happens next:
Maintainers and community members will review your issue and may:

• Ask for additional information if the template is incomplete
• Provide a solution or workaround
• Label the issue appropriately for tracking
• Link it to related issues or pull requests