changelog: add links to bridge-utils, fix file name of weekly updates

[dongsupark]

Add a link to the original issue flatcar/Flatcar#638 in the changelog missing in from #4159.

Fix file name of weekly updates changelog from #3174.

[Copilot]

Pull request overview

Updates changelog entries to improve traceability and correct/complete weekly update records.

Changes:

• Add a reference link to Flatcar issue #638 in the bridge-utils removal changelog entry.
• Populate 2026-08-06-weekly-updates.md with the weekly package update bullets (correcting the previously incorrect/empty weekly updates entry).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
changelog/updates/2026-08-06-weekly-updates.md	Adds the weekly update bullet list for 2026-08-06.
changelog/changes/2026-07-29-drop-bridge-utils.md	Adds a direct link to the originating Flatcar issue for the bridge-utils removal entry.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.

[dongsupark]

Oh, the previous Copilot comment is not valid any more, because that was based on the commit including my file name mistake.
Now I have fixed the changelog file name from 2026 to 2025. (Yes, 2025 is the correct one)

[tormath1]

Thanks for the heads-up, to me we were still in 3035.

[krnowak]

Won't the rename cause the release automation to pick up the entries from the renamed file, because the timestamp of the file has changed?

[dongsupark]

Won't the rename cause the release automation to pick up the entries from the renamed file, because the timestamp of the file has changed?

Interesting question, so I have tested this branch with show-changes, but show nothing. That has something to do with how the script is implemented.

[dongsupark]

TL;DR we do not have to worry about such a regression in release notes.

What show-changes calls is not a normal git diff but a slightly different one, git difftool ....
You can test it with git difftool --no-prompt --extcmd='sh -c "if [ \"$LOCAL\" = /dev/null ] ; then cat \"$REMOTE\" ; fi"' main..HEAD -- "changelog/updates/", then it shows nothing.
On the other hand, git diff main..HEAD changelog/updates would print out a file rename change.
See also the long comment in show-change, https://github.com/flatcar/flatcar-build-scripts/blob/4dd31990ce7d60fcc1d8829997b0b290c0865e06/show-changes#L80.