Skip to content

Implement TLC Feedback and Razor Feedback - #594

Merged
Martinski4GitHub merged 20 commits into
devfrom
TLCFeedback
Sep 3, 2026
Merged

Martinski4GitHub merged 20 commits into
devfrom
TLCFeedback

Conversation

@ExtremeFiretop

@ExtremeFiretop ExtremeFiretop commented Aug 24, 2026

Copy link
Copy Markdown
Owner

Implement TLC Feedback and Razor Feedback

TLC feedback is here:
https://www.snbforums.com/threads/merlinau-v1-6-6-the-ultimate-firmware-auto-updater.96306/post-1002422

And Razor feedback is here:
#593

Implements a message that does not print to when being invoked by AMTM
Implement a hardened mirror idea of Razor with a faster refresh
Debug Workflow
This reverts commit 9b5578c.
Fix Workflow
Authorize the use of secret key
Match Main
Improve wording
Updated project metadata and last modified date.
Updated last modified date in the script header.
Clarified licensing terms and trademark information.
Add additional terms for MerlinAU under GPLv3 Section 7.
This document outlines the trademark policy for MerlinAU, detailing the use of its marks, official project information, and guidelines for derivative works.
Added project metadata and licensing information.
Updated the formatting and structure of the CONTRIBUTING.md file to improve readability and clarity. Added sections for Contributor Certification and Documentation Styleguide.
Added licensing information, project authors, and trademark details for MerlinAU.
Clarified contribution guidelines and licensing terms in CONTRIBUTING.md.
Updated contribution section for clarity and links.
Updated section on official co-authorship and licensed use of MerlinAU Marks.
@Martinski4GitHub

Copy link
Copy Markdown
Collaborator

@ExtremeFiretop,

Just FYI,

Last weekend, my wife and I attended the wedding of one of her relatives. Since the event was taking place in a city fairly close to San Francisco, CA, we decided to take a few days off and visit San Francisco for a short vacation. So, we won't be back home until Saturday evening, which means that for the next few days, I won't have time to take a close look and review all the pending PRs.

Based on my quick reading of GitHub emails, none of the issues addressed by the PRs are critical bugs (like a crash or fatal errors stopping functionality), so I don't think we're in a hurry to issue a production release.

Take care, bud. I'll talk to you when I'm back home and caught up with all my work and personal emails.

@ExtremeFiretop

Copy link
Copy Markdown
Owner Author

@ExtremeFiretop,

Just FYI,

Last weekend, my wife and I attended the wedding of one of her relatives. Since the event was taking place in a city fairly close to San Francisco, CA, we decided to take a few days off and visit San Francisco for a short vacation. So, we won't be back home until Saturday evening, which means that for the next few days, I won't have time to take a close look and review all the pending PRs.

Based on my quick reading of GitHub emails, none of the issues addressed by the PRs are critical bugs (like a crash or fatal errors stopping functionality), so I don't think we're in a hurry to issue a production release.

Take care, bud. I'll talk to you when I'm back home and caught up with all my work and personal emails.

No rush at all, I have this pending. And something for YazFi. And that's about it.
Both are small things at this point. They can stay open until you return!

Hope the wedding went well!

@Martinski4GitHub

Copy link
Copy Markdown
Collaborator

@ExtremeFiretop,
Just FYI,
Last weekend, my wife and I attended the wedding of one of her relatives. Since the event was taking place in a city fairly close to San Francisco, CA, we decided to take a few days off and visit San Francisco for a short vacation. So, we won't be back home until Saturday evening, which means that for the next few days, I won't have time to take a close look and review all the pending PRs.
Based on my quick reading of GitHub emails, none of the issues addressed by the PRs are critical bugs (like a crash or fatal errors stopping functionality), so I don't think we're in a hurry to issue a production release.
Take care, bud. I'll talk to you when I'm back home and caught up with all my work and personal emails.

No rush at all, I have this pending. And something for YazFi. And that's about it. Both are small things at this point. They can stay open until you return!

Hope the wedding went well!

Yeah, the wedding festivities were fun and, as usual, we ran into a few relatives and friends whom we had not seen for at least a couple of years since they moved to another state. Lots of great food and dancing!! LOL!!

Well, I finally took a closer look and reviewed your PR changes. It's all looking good. The idea of having our own copy of the F/W image checksum signatures in the MerlinAU GitHub repo as a backup/mirror sounds reasonable, especially if it's fetched/checked every 15 minutes.

Yes, there's a 15-minute window where the checksum manifest could be outdated when RMerlin announces a new F/W release version and publishes new checksums, but I think (hope!) the number of actual users who may be affected within such a short window is not very large (although, apparently, several countries have been banned in the past , e.g. Brazil, Sweden, Turkey).

Since the issue is due to Cloudflare banning entire pools of IP addresses coming from certain countries, I'm thinking of adding a bit more error checking & reporting when fetching the checksums from RMerlin's website. It's highly unlikely that websites such as GitHub and SourceForge would become that aggressive and ban entire countries, so I think we're OK when connecting to those websites.

Let me write/modify some code and I'll submit a PR this evening.

Take care bud.

@Martinski4GitHub Martinski4GitHub left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

It's all looking good. Approved!!

@Martinski4GitHub
Martinski4GitHub merged commit 1ce9f45 into dev Sep 3, 2026
1 check passed
@ExtremeFiretop
ExtremeFiretop deleted the TLCFeedback branch September 4, 2026 12:39
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