Will soon be used to import screens (including metadata) from any root directory.

Necessary for testing purposes. This includes adding a with_model trait for the firmware factory so it can be associated with a model when needed.

Ensures embedded lists are styled as a column of information. This will soon be used to render associated records.

Necessary to explain how design modes work. Will soon be added to the templates.

This will allow us to remove the existing documentation since this new project documents and fully automates Kubernetes support.

Necessary to encapsulate the creation of new firmware records. This will soon be used within actions.

Necessary to encapsulate the logic to obtain firmware. Will initially be used to refactor the Display API show action.

Necessary to ensure, when auto-provisioning a TRMNL B/W/R/Y device, that they are mapped properly. There was no communication that this was added and only discovered this when performing an automatic update of a B/W/R/Y device and noticing the wrong firmware was being installed.

Necessary to associate firmware with multiple models for improved database integrity. This will also allow us to ensure the right firmware is selected for OTA updates.

Necessary to join the two models together. This includes providing associations for the existing firmware and model relations.

Necessary to manage database records.

Will soon be used when rendering model information so you know how many models, at a glance, a firmware is associated with. A link to the first model is provided for convenience.

Necessary to find all records with associated models. This includes:

• Updating #by_version_desc to be #version_descending for improved readability.

• Using #version_descending as the default sort order.

• Joining by both the firmware model and model tables. The latter makes it possible to search by model attributes if necessary.

This is a breaking change that will soon be fixed when the firmware repository is updated to use this new functionality.

Enhances the repository with attachment management and associated model information. This make it easier to find firmware by model information including management of associated models.

Necessary to reduce duplication by encapsulating how to update an existing firmware record so this can be reused by multiple objects.

Handy for CLI use.

Necessary to ensure the mode, when exported, can be imported as well.

Ensures firmware is always associated with a model.

Necessary to include the associated model IDs (if any) in the API responses.

This is a breaking change which will require updating the API specs.

Now that firmware can be associated with multiple models, it becomes important to show model information including a direct link to the associated model.

Necessary to explain what these fields do. This also fixes the path to where the popovers are located and ensures the show view is using the correct part.

Sheds more light on what screens are and how they are used. This also includes documentation for the new import script.

Necessary to capture the screen mode (i.e. text or art). This is identical to extensions behavior.

Necessary to render the correct mode label which matches what was selected when creating or updating the template.

Necessary to ensure the mode is included in these attributes. The corresponding factory was updated to include the default mode which mimics database behavor as well. The exporter spec was updated to account for this new attribute as well.

Necessary to import screens using Metapath. This allows us to import screens with rich metadata.

Necessary to reduce duplication by delegating to this new object. This also cleans up the request spec use of versions used and the objects (i.e. let statements) needed for testing.

The firmware_url is also included in every response in order to silence the missing URL arrors in the device logs (another firmware change which now requires this to always be present).

Necessary to allow folks to set the screen mode. This is identical to extensions behavior.

Now that we can properly cache (synchronize) firmware for different models, we can enable automatic updates again so all devices can stay up-to-date with new firmware releases.

Finding firmware without the join table no longer makes sense because you need to know the model ID to any firmware specific information. This ensures the join is used which you can query by model attributes as well.

Reek was updated to ignore feature envy for the replace attachment method since there’s not much that can be done until attachment logic, across all relations/repositories, is extracted further.

Necessary to delegate creation of firmware to the new creator in order to reduce duplication and handle model associations. Changes to the shared fields will effect updates too.

This is a breaking change.

Necessary because I can’t get Capybara to perform a multi-select of models. As a workaround, these specs are simplified in favor of using unit testing for each action.

Necessary to download firmware for multiple models because we no longer use a universal binary. This also means that we answer a success with an array of firmware records or a failure with an array of errors for each download, attach, or creation failure.

Reek was update to ignore feature envy for the attach method as this is, currently, an issue with how Shrine works.

Necessary to delegate updating of firmware to the new updater in order to reduce duplication.

Weekly updates and maintenance.

Clarifies usage better.

Details. This also picks up a minor update to Domain Name as well.

Details.

Details. This also picks up RuboCop 1.92.0 for development purposes along with patch updates to the other gems.

This version introduces a breaking change with cateogries where they are nested arrays. To work around this, I flatten them in order to restore original behavior. Details.

Instead of using an empty array, provide a prompt instead.

Despite, internally, calling these screen templates, for UI purposes, they need to be known as designs in order to match UI terminology.

Ensures the firmware version is always supplied. As for the update_firmware key, that’ll be computed by the Display API show action since we only want this to be true when the device supports firmware updates and the versions don’t match.

Necessary to ensure the message is styled and is passed through to the view (i.e. message instead of body). Use of the emoji for the hero image has been dropped as well.

Ensures, when a device’s button is pressed, the associated device’s command is handled properly. This includes when the device is asleep so that it temporarily wakes to process the event.

In the situation where a device command is not recognized, an error screen will be rendered to explain why the command wasn’t processed. This is also why a new translation was added.

Use of trigger terminology has been replaced with event terminology because these are events issued by the device (a.k.a. wake reaason) which makes this easier to reason about.

Ensures the positioner honors manual playlists by checking the associated event (this will soon be provided by the Interrupter). At the moment, we don’t care what the event is, only that it’s present. In the future, this details of the event might become more useful.

In a nutshell, this means if an event is present or the playlist is automatic, the playlist will advance as requested. This also accounts someone manually pressing a button on the device (which previously wasn’t possible). Otherwise, only the current screen is shown because the playlist requires manual advancement.

Reek was updated to ignore the event control parameter because it’s a necessary evil in this case.

No longer needed now that we can point to the [Terminus Kubernetes](https://github.com/pradeepbbl/terminus-kubernetes) project.

Necessary to remove all traces of firmware kind since we’ll soon associate firmware with multiple models instead.