Test for release

[BarbourSmith]

This is a place to test the current version to see if it is ready for release.

[BarbourSmith]

@MaslowBot please build

[github-actions]

🤖 WebUI Compilation Complete 🤖

✅ Successfully compiled ESP3D WebUI for English language

Build Details:

• Commit: a05a6db5f70768d4375877e3bf94a308638d4d71
• Language: en (English)
• WebUI size: 126.76 KB (compressed)
• Build time: ~3 seconds

Download:
Download the "Updated UI.zip" file from the Actions tab.

Installation Instructions:

1. Download and extract the "Updated UI.zip" file
2. Upload the index.html.gz file from the extracted folder to your ESP3D device
3. The README.txt file in the zip contains detailed instructions

This comment was automatically generated in response to a build request comment.

[davidelang]

@BarbourSmith please tag this commit
git tag v1.13 a05a6db
this will make the version show up correctly (the tag can be removed if needed 'git tag v1.13 -d')

or if you don't like v1.13 call it v1.13-rc1 (release candidate 1). If you want to go this route we should add logic to the auto-update to treat -rc as lower than no postfix or -#)

[atari-zero]

@BarbourSmith Tested this along with #444. I did not encounter any interface issues. All interface elements worked fine - right click movement, trace contour, loading and unloading files, measurement unit switch, changing maslow.yaml in settings.

[BarbourSmith]

Excellent!

[BarbourSmith]

@BarbourSmith please tag this commit git tag v1.13 a05a6db this will make the version show up correctly (the tag can be removed if needed 'git tag v1.13 -d')

or if you don't like v1.13 call it v1.13-rc1 (release candidate 1). If you want to go this route we should add logic to the auto-update to treat -rc as lower than no postfix or -#)

@davidelang The main branch is now tagged 1.13. What else do I need to do with the tags to get everything to publish nicely?

[davidelang]

BarbourSmith wrote:

@davidelang The main branch is now tagged 1.13. What else do I need to do with the tags to get everything to publish nicely?

That should be it. If you compile the main branch (as opposed to a PR with a whitespace change) it should show up as v1.13 if they both show up as v1.13 then you can merge #198 it will then give a popup if the versions don't match (as you will be on v1.13-X-gabcedf deleting the v1.13 tag and adding it again to the tip of the UI branch will then silence the warning David Lang