v3.1.4

[github-actions[bot]]

Changelog

v3.1.4 (2024-05-24)

Full Changelog

Release summary v3.1.4 #290
No new features in this release. This release contains chore related work to automate the release process for the Playnite extension (*.pext) file. This will ensure every release has this file in its assets available for download.

Implemented enhancements:

• Automate the packaging and release of the playnite-web-plugin #321

Merged pull requests:

• chore: package Playnite plugin via toolbox in automation #323 (andrew-codes)
• background process #317 (andrew-codes)
• docker in docker #315 (andrew-codes)
• add prebuild devcontainer #314 (andrew-codes)
• Enable devpod (test) #313 (andrew-codes)
• fix: application Error TypeError: Cannot read properties of null (reading 'name') #310 (andrew-codes)
• fix: activate game fails with a 500 server error #309 (andrew-codes)

v3.1.3 (2024-05-12)

Full Changelog

Fixed bugs:

• Activate game fails with a 500 server error #308
• Application Error TypeError: Cannot read properties of null (reading 'name') #301

v3.1.2 (2024-05-10)

Full Changelog

Fixed bugs:

• Platform (+1) should never be shown #208

Merged pull requests:

• fix: errors caused when game data is missing #306 (andrew-codes)

v3.1.1 (2024-05-09)

Full Changelog

Fixed bugs:

• Activating a game does not publish MQTT message #295
• Closing filter pane causes navigating back in user history #294
• Game details on home view is broken #293

Merged pull requests:

• Activating a game does not publish MQTT message #298 (andrew-codes)
• Game details on home view is broken + filter navigation #297 (andrew-codes)
• Closing filter pane causes navigating back in user history #296 (andrew-codes)

v3.1.0 (2024-05-09)

Full Changelog

This release introduces the ability to drill down into a game and view its description. If you have enabled authentication via environment parameters, the game details will also show a button allowing you to activate the game on a given platform. Activating a game will publish a message to MQTT that can be handled by external consumers. One use case for this feature could be as follows:

1. Activate a game, publishing a MQTT message.
2. MQTT message is received by Home Assistant and triggers an automation.
3. Automation reads the platform from the message to start the desired platform via Home Assistant.
4. If the platform is for PC, then the Home Assistant automation can start the desired game via the message's game's ID (Playnite ID). This can happen by remotely starting Playnite from a shell command and providing the game's ID as a CLI parameter.

Of course, what you do with the MQTT message is up to you!

Implemented enhancements:

• Features requiring authentication are optional #280
• Game details from home screen in addition to browse #277
• Sort activation actions alphabetically #275
• Activate game from details view #184
• Sign in/out main menu link #183
• Game details view #182
• Auto trim white spaces on search #124

Fixed bugs:

• Home Screen game details transition is jarring #285
• Dev image broken #278

Closed issues:

• Fix release branching strategy #279
• Update deprecated actions from pipelines #264

Merged pull requests:

• Update deprecated actions from pipelines #288 (andrew-codes)
• Auto trim white spaces on search #287 (andrew-codes)
• Home Screen game details transition is jarring #286 (andrew-codes)
• Sort activation actions by user priority or alphabetically #284 (andrew-codes)
• Game details from home screen in addition to browse #283 (andrew-codes)
• fix: broken dev image #282 (andrew-codes)
• feat: features requiring authentication are optional #281 (andrew-codes)
• login link, game details, game activation #274 (andrew-codes)

v3.0.1 (2024-05-06)

Full Changelog

Fixed bugs:

• Error installing plugin to Playnite from releases #230

Closed issues:

• v3.0.1 Release summary #269
• Releasing playinite-web docker image fails using yarn #268
• Remove need to store LFS files #267

Merged pull requests:

• release 3.0.1 #272 (andrew-codes)
• fix: released playnite-web image failing to start #271 (andrew-codes)
• fix: use yarn install issue in released images #270 (andrew-codes)

v3.0.0 (2024-04-22)

Full Changelog

New and improved UX! Basic filtering (by name and by feature). Filter by platform soon to follow!

Now Playing (homepage)

My Library Screenshot

Basic filtering by name and feature

Implemented enhancements:

• Home view shows playing and plan to play games #219
• Filter and find should always be available (scrolling to top is not sufficient) #211
• Filter values are in alphabetical order #204
• Completion status instead of developer/publisher as subtitle to game #203
• Removing individual filters quickly #202
• Filter options #185
• Show platforms for games #180
• Clear button on find filter #179
• Better spacing of grid view games on all resolutions #168
• Can access filters after scrolling past them on browse view #166
• Header nav bar (sticky) on mobile #164
• Redesign desktop experience #156
• Redesign tablet experience #155
• Redesign mobile experience #154

Closed issues:

• Broken images are not ideal #225
• Use dialog for selecting filter values #224
• Mobile navigation transitions collide with menu closing transition #209
• Filter bar left margin on mobile is too much #199
• Navigate away from browse crashes #198
• Add extra vertical spacing on game grid #192
• Header no longer sticky on mobile #191
• UI tweaks #181
• Mobile landscape drawer open button #178
• Mobile landscape needs more spacing from edge of screen #177
• Nav to top header not centered on moblie #176
• Left navbar should not animate on page transitions #175
• Menu doesn't show on phones #169
• Filter by name is not whole word only #167
• Filter on own line on phone #165
• Tighten header spacing on phone #163
• Setup staging environment #157
• PR image packages are incorrectly published under different name #90

2.0.2 (2024-04-21)

Full Changelog

Closed issues:

• Enable a latest release image #238
• Enable development of more than one release version #234

2.0.1 (2024-04-11)

Full Changelog

Implemented enhancements:

• Exact match on words when searching #125
• Search for owned games by multiplayer type #118

Closed issues:

• Build and package via GitHub action #27

2.0.0 (2024-01-29)

Full Changelog

Implemented enhancements:

• Search for owned games by release date range #121
• Search for owned games by genre #120
• Remember me #106
• Non-touch centric UI / vertical scroll #103
• Improve responsiveness of menu and UI when browsing library #94
• Consistent UI #92
• Trigger publishing of entire library from mqtt message #91
• Display owned game platforms #82
• Enable features requiring authentication #81
• Allow configuring port #80
• Mobile phone UI #63
• Publish game state #56

Fixed bugs:

• Games have improper dimensions; visible when searching #117
• Layout on phone not correct #116
• Scroll is broken on HA iPad app #110
• Game grid does not work on all devices/screen resolutions #99
• Add back search capabilities #98
• Show < 6 games in grid when on small tablets #97
• Swiping on iPad can stop user from continuing without being at the end for the game grid #96
• UI is missing navigation when embedded in iframe #79
• Flash of unstyled content (search bar) on the browse view #78

Closed issues:

• Update read me for release #151
• Search should be global to library #126

1.0.0 (2024-01-05)

Full Changelog

Implemented enhancements:

• Navigation to views #74
• Support varying sized screens #71
• Enable deletion of entities via sync #66
• Sync all entity type changes #65
• iPad size UI #62
• Browse games view #61
• On deck view #60
• Searching for games by title #55
• Playnite web can list all games #52
• Game library is persisted and accessible to other playnite-web services #28
• Ensure library db is kept updated in case of extended downtime from updater #26
• MQTT connection information can be provided via Playnite's GUI configuration #21
• Playnite plugin publishes message when remote data sources have finished updating #12
• Playnite plugin can be triggered to update library from remote sources #11
• Updating game in Playnite publishes game data for the updated game #10
• Plugin will always publish games with updates regardless of if the request states to exclude them #9
• Limit number of games published per publishing cycle #8
• Publish games from Playnite #7

Closed issues:

• Allow publishing of entire library, on-demand #69
• Fix retention policy #34
• Automate build and packaging for release #31
• README with instructions on how to run #29
• Release workflow #16
• Pull request workflow #5
• Playnite plugin app #4
• playnite-web app #3
• Mono-repo setup #2
• Local development environment #1

* This Changelog was automatically generated by github_changelog_generator

---

This discussion was created from the release v3.1.4.