> For the complete documentation index, see [llms.txt](https://frc-radio.vivid-hosting.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://frc-radio.vivid-hosting.net/advanced-topics/offseason-kiosk-programmer/kiosk-release-notes.md). # Kiosk Release Notes ## Release Notes ### 1.0.0 Bumped minimum version to 1.3.0 (effectively same as 1.2.9, but, bumping minor version for week 0 usage) ### 0.8.5 Bumped minimum version to 1.2.9 Programmed/Unprogrammed teams are now accessible without the FTA password More confetti ### 0.7.0 Bumped minimum version to 1.2.2 Displays currently installed firmware release Added a "force firmware reflash" button ### 0.6.1 Fixed minimum versions and update times ### 0.6.0 Added logic to detect radios with firmware pre and post 1.2.x releases, 1.2.1 firmware is pre-packaged in this release ### 0.5.1 Updated packaged robot firmware release to 1.2.0 ### 0.5 Added backward compatibility with VH-109 releases earlier than 1.2.0 ### 0.4 Adds ability to pull WPA/SAE keys from FMS w/pin Notice: Due to a schema change in frc-radio-api, 0.4 will not be compatible with VH-109\_1.2.0 or later releases. The 0.5 version of the radio kiosk will be backward compatible on later releases of radio firmware. ### 0.3 Adds an admin page accessible by hovering over the "F" in "FRC" for 1 second before clicking. The admin page links to the upload page, can program test teams, view what teams have programmed their radios, and enable the option to use provide teams 2.4GHz keys. All features are gated behind the admin password. ### 0.2.1 Bugfix: The data/firmware folder was getting overwritten by a mounted data folder. Changed to a symlink solution. ### 0.2.0 Added firmware update capability, prepackaged artifacts for VH-109 FW release 1.1.2 ### 0.1.0 Initial release used at 2024 FIRST FRC Championship --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://frc-radio.vivid-hosting.net/advanced-topics/offseason-kiosk-programmer/kiosk-release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.