Skip to content

Dev 1.4.2 as Next Stable Release#456

Merged
ExtremeFiretop merged 22 commits intomainfrom
dev
Apr 14, 2025
Merged

Dev 1.4.2 as Next Stable Release#456
ExtremeFiretop merged 22 commits intomainfrom
dev

Conversation

@ExtremeFiretop
Copy link
Owner

@ExtremeFiretop ExtremeFiretop commented Apr 14, 2025

Forms post update = COMPLETED
Readme update = COMPLETED
Version.txt update = COMPLETED
Dev 1.4.2 as Next Stable Release

What's Changed/Fixed?:

PR: [ #451 ] - Minor Fixes and Additions
-After the Router PWD is set, we now add a successfully tested or unvalidated result to the main menu.
-Change the wording for the update process to fix nitpicks related to "anyways" vs "anyway" as reported by: jksmurf
-Update Minimum Versions to 3 behind production

  • Version"3004.386.13.2" for the 386 branch;
  • Version "3004.388.8.0" for the 388 branch
  • Version "3004.388.8.2" for the 3006.102 branch

-Fix the WebUI status for the changelog approval being "Disabled" instead of "TBD"
-Fixes some visual nitpicks of the WebUI

PR: [ #452 ] - Code Improvements
-Make sure the "FW_New_Update_Changelog_Approval" option is initialized properly under all circumstances.
-Show the Password "Verified" status in GREEN = GOOD.
-Minor cleanup.
(Thanks @Martinski4GitHub )

PR: [ #453 ] - Fix Changelog and Email Notifications and Patch Uninstall
-Fix a report from nlurker here for blank changelog URLs in the email notifications: https://www.snbforums.com/threads/merlinau-v1-4-1-the-ultimate-firmware-auto-updater-gnuton-support.91326/post-951011
The Changelog check (pre-approval) was not running before the email notification with the run_now parameter.
-Quick fix to allow uninstall of the script when installed on unsupported routers as reported by mxxcon here: https://www.snbforums.com/threads/merlinau-v1-4-1-the-ultimate-firmware-auto-updater-gnuton-support.91326/post-951128

PR: [ #454 ] - Improvement
-Miscellaneous code improvements.
(Thanks @Martinski4GitHub )

PR: [ #455 ] - Fixes and Code Improvements
-Improved uninstallation workflow when users attempt to install MerlinAU on unsupported routers.
-Now the code will automatically prompt users to uninstall immediately after informing them that their current router model is unsupported. In such scenarios, this provides users a quick & easy way to uninstall.
(Thanks @Martinski4GitHub )

As always, we highly recommend you update ASAP as this includes functional improvements and little bug fixes.

Thanks!

ExtremeFiretop and others added 18 commits April 9, 2025 02:20
Minor Fixes
Some additional code improvements.
Patch Changelog and Email Notifications
…otifications

Patch Changelog and Email Notifications and Fix Uninstall
- Fixed bug introduced in PR #453 which was allowing installation in all unsupported models.
- Miscellaneous code improvements.
Improved uninstallation workflow when users attempt to install MerlinAU on unsupported router models.

Now the code will automatically ask users to uninstall right after informing them that their current router model is unsupported. On such scenarios, this provides users a quick & easy way to uninstall.
@ExtremeFiretop ExtremeFiretop added bug Something isn't working enhancement New feature or request labels Apr 14, 2025
@ExtremeFiretop
Copy link
Owner Author

@Martinski4GitHub

I think this is ready. Feel free to review :)

@ExtremeFiretop
Copy link
Owner Author

Also; should we still remove the build number from the version.txt or have we stopped caring yet?

@Martinski4GitHub
Copy link
Collaborator

@Martinski4GitHub

I think this is ready. Feel free to review :)

Looks good to me!!

@Martinski4GitHub
Copy link
Collaborator

Also; should we still remove the build number from the version.txt or have we stopped caring yet?

I think we should remove it from both branches now, and then we'll add it to the development branch only when it's needed.
IOW, the default will be NO build timestamp, unless we're making a lot of changes and we want users to switch to the develop branch for testing & validation purposes (e.g. Beta testing).

My 2 cents.

@ExtremeFiretop
Copy link
Owner Author

ExtremeFiretop commented Apr 14, 2025

Also; should we still remove the build number from the version.txt or have we stopped caring yet?

I think we should remove it from both branches now, and then we'll add it to the development branch only when it's needed. IOW, the default will be NO build timestamp, unless we're making a lot of changes and we want users to switch to the develop branch for testing & validation purposes (e.g. Beta testing).

My 2 cents.

Done! And Post is ready :)

Copy link
Collaborator

@Martinski4GitHub Martinski4GitHub left a comment

Choose a reason for hiding this comment

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

Good to go and ready to be shipped!!!

@ExtremeFiretop ExtremeFiretop merged commit ffbfba1 into main Apr 14, 2025
3 checks passed
@Martinski4GitHub
Copy link
Collaborator

@ExtremeFiretop,

I'm being summoned to dinner. Talk to you later or perhaps tomorrow.
Have a good night, bud!!!

@ExtremeFiretop
Copy link
Owner Author

@ExtremeFiretop,

I'm being summoned to dinner. Talk to you later or perhaps tomorrow. Have a good night, bud!!!

Enjoy dinner!
Chat soon. Thanks again bud!!

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

Labels

bug Something isn't working enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants