Skip to content

Dev 1.4.5 as Next Stable Release#470

Merged
ExtremeFiretop merged 20 commits intomainfrom
dev
May 15, 2025
Merged

Dev 1.4.5 as Next Stable Release#470
ExtremeFiretop merged 20 commits intomainfrom
dev

Conversation

@ExtremeFiretop
Copy link
Owner

@ExtremeFiretop ExtremeFiretop commented May 15, 2025

Forms post update = READY
Readme update = COMPLETED
Version.txt update = COMPLETED

Dev 1.4.5 as Next Stable Release
What's Changed/Fixed?:

PR: [ #468 ] - Include Update Button for Script in WebUI

PR: [ #469 ] - Fix & Improvements

  • Fix to prevent showing "vTBD" on the WebGUI page for "Script Update Available"
  • Improved some message wording.
  • General code improvements.
  • (Thanks @Martinski4GitHub )

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

@ExtremeFiretop ExtremeFiretop marked this pull request as ready for review May 15, 2025 23:33
@ExtremeFiretop ExtremeFiretop merged commit f1c2e98 into main May 15, 2025
1 check passed
@ExtremeFiretop
Copy link
Owner Author

ExtremeFiretop commented May 15, 2025

LOL @Martinski4GitHub

Sorry buddy I literally meant to enable auto-merge and instead actually merged it instead.
Luckily; all went well. Just had to pump out the forum post right away lol

@Martinski4GitHub
Copy link
Collaborator

LOL @Martinski4GitHub

Sorry buddy I literally meant to enable auto-merge and instead actually merged it instead. Luckily; all went well. Just had to pump out the forum post right away lol

No sweat and no worries!!! 👍😉
The current code was essentially ready to go, and I even ran it through the Linter tool after my most recent PR, and the code came up "clean" as before (i.e no errors and no new warnings).

@ExtremeFiretop
Copy link
Owner Author

LOL @Martinski4GitHub
Sorry buddy I literally meant to enable auto-merge and instead actually merged it instead. Luckily; all went well. Just had to pump out the forum post right away lol

No sweat and no worries!!! 👍😉 The current code was essentially ready to go, and I even ran it through the Linter tool after my most recent PR, and the code came up "clean" as before (i.e no errors and no new warnings).

Fantastic! I just didn't want you to think I was playing fast and loose

I got mixed up with the auto merge button and the merge button and it was my bad because I didn't read the prompt before accepting lol!

I figured we probably had nothing else for now. I know my list is completely empty. It's just maintenance from here on out

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

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants