Skip to content

Releases: andrew-codes/playnite-web

v5.0.1

13 Aug 14:01
@github-actions github-actions
v5.0.1
17ccad0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v5.0.1

5.0.1 (2024-08-13)

Bug Fixes

  • misc: 🐛 test game assets are not packaged with docker image (#471) (613b7f4), closes #470
Assets 3
Loading

v5.0.0

12 Aug 20:52
@github-actions github-actions
v5.0.0
a125d42
This commit was signed with the committer’s verified signature.
andrew-codes Andrew Smith
SSH Key Fingerprint: cgjTKL1GgG8S7cp2rv4u4zh3aPUeb4RRqMoOj+focP0 Learn about vigilant mode.
Compare
Choose a tag to compare
v5.0.0

5.0.0 (2024-08-12)

  • chore!: enable visual regression in e2e tests & game data/assets for local development (#402) (a83d3a1), closes #318
  • feat!: graphql based authentication/authorization (#403) (5c60ca4), closes #318
  • no longer supporting armv7 and armv6 (99eefa3)
  • remove gameAsset route (6318d10)

Bug Fixes

  • misc: 🐛 semantic release when releasing playnite-web (d234e0d)

chore

  • bump Node.js version (0ddfaf1)
  • deprecate HASS add-on for game-db-updater (c779b00)

Features

  • Added e2e test coverage for playlist home page (40c044b)
  • Can query all playlists (073af5f), closes #318
  • Can query all playlists (#423) (5727750), closes #318
  • CSP is enabled (6ee513f)
  • enable activation of games via graph API (c038f5f)
  • enable activation of games via graph API (#439) (11c671a), closes #425
  • enable querying graph for games (#427) (98d6efb)
  • enable real-time subscriptions to run state change events within Playnite Web (1489af8), closes #426
  • filter games by name via graph API (93fe279), closes #444
  • graph api (#404) (076a2dc), closes #318
  • graphql subscriptions for game run state change events (#432) (f579576), closes #426 #434
  • Home page consumes graphql playlists (21255d5)
  • Implement games on playlist resolver. (3c487d2), closes #424
  • optimize game assets (18bf1af)
  • Playlist homepage consumes graph api (#452) (c36381c), closes #442

Performance Improvements

BREAKING CHANGES

  • armv6 and armv7 CPUs are no longer supported until further notice.
  • resource route gameAsset/$type/$relatedId is deprecated and removed. Related entities in the graph API now can be queried for their icons, covers, etc. The ID on these GameAsset relations is the file name found in /asset-by-id/$id route.
  • required Node.js version is now ^22.5.0.
  • game-db-updater is deprecated and removed. For this reason, the HASS add-on for game-db-updater is also removed. Playnite Web now includes the game-db-updater in one application.
  • /activate endpoint has been removed. This will be
    replaced by a GraphQL endpoint.
  • game assets are no longer stored in the game database.
    They are now stored as files locally on the playnite-web-app under
    ./public/asset-by-id. When using docker, ensure this directory is an
    external volume to persist these images across restarts of the
    container.
Assets 3
Loading

v4.0.2

22 Jun 16:18
@github-actions github-actions
v4.0.2
dbcb12e
This commit was signed with the committer’s verified signature.
andrew-codes Andrew Smith
SSH Key Fingerprint: cgjTKL1GgG8S7cp2rv4u4zh3aPUeb4RRqMoOj+focP0 Learn about vigilant mode.
Compare
Choose a tag to compare
v4.0.2

Changelog

v4.0.2 (2024-06-22)

Full Changelog

Fixed bugs:

  • 4.01 playnite-web not updating without game_db_updater #392

Closed issues:

  • Dedicated developer guide documentation #237

Merged pull requests:

v4.0.1 (2024-06-12)

Full Changelog

Fixed bugs:

  • Release 4 only available arm64? #387

Merged pull requests:

v4.0.0 (2024-06-10)

Full Changelog

Implemented enhancements:

  • Playnite web app is the only required service to run #341

Fixed bugs:

  • Major releases fail release pipeline #376

Closed issues:

  • Increased reliability via automated testing #348

v3.2.1 (2024-06-05)

Full Changelog

v3.2.0 (2024-06-05)

Full Changelog

Support for ARM devices and installable as HASS add-on.

Implemented enhancements:

  • Smaller playnite-web-app image #339
  • Support cloud hosted Mongo databases #332
  • Support ARM Docker images #329
  • Automate the packaging and release of the playnite-web-plugin #321
  • Package playnite-web as HASS add-ons #319

Fixed bugs:

  • Released images are not tagged with specific version, only major.minor-latest #372
  • fix: broken Mongodb connection #342
  • .devcontainer via devpod breaks docker mongo development environment #316

Closed issues:

  • Discussions and chat are in gitter.im #364
  • Shorten pr workflow run times #363
  • Removed self-hosted gh action runner image #346
  • PRs do not require publishing images as status check #344
  • Main branch is upcoming release, not the current release #338
  • Publish GitHub runner to ghcr.io and its source code is within this repo #331
  • Reduce effort to keep all versions in sync with one another #330
  • Contributing guidelines #235

Merged pull requests:

v3.1.4 (2024-05-24)

Full Changelog

Release summary v3.2.0 #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.

Merged pull requests:

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](https://g...

Read more
Assets 4
Loading
0 Join discussion

v4.0.1

12 Jun 18:09
@github-actions github-actions
v4.0.1
5b69c91
Compare
Choose a tag to compare
v4.0.1

Changelog

v4.0.1 (2024-06-12)

Full Changelog

Fixed bugs:

  • Release 4 only available arm64? #387

Merged pull requests:

v4.0.0 (2024-06-10)

Full Changelog

Implemented enhancements:

  • Playnite web app is the only required service to run #341

Fixed bugs:

  • Major releases fail release pipeline #376

Closed issues:

  • Increased reliability via automated testing #348

v3.2.1 (2024-06-05)

Full Changelog

v3.2.0 (2024-06-05)

Full Changelog

Support for ARM devices and installable as HASS add-on.

Implemented enhancements:

  • Smaller playnite-web-app image #339
  • Support cloud hosted Mongo databases #332
  • Support ARM Docker images #329
  • Automate the packaging and release of the playnite-web-plugin #321
  • Package playnite-web as HASS add-ons #319

Fixed bugs:

  • Released images are not tagged with specific version, only major.minor-latest #372
  • fix: broken Mongodb connection #342
  • .devcontainer via devpod breaks docker mongo development environment #316

Closed issues:

  • Discussions and chat are in gitter.im #364
  • Shorten pr workflow run times #363
  • Removed self-hosted gh action runner image #346
  • PRs do not require publishing images as status check #344
  • Main branch is upcoming release, not the current release #338
  • Publish GitHub runner to ghcr.io and its source code is within this repo #331
  • Reduce effort to keep all versions in sync with one another #330
  • Contributing guidelines #235

Merged pull requests:

v3.1.4 (2024-05-24)

Full Changelog

Release summary v3.2.0 #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.

Merged pull requests:

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:

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 u...
Read more
Assets 4
Loading
0 Join discussion

v4.0.0

10 Jun 13:43
@github-actions github-actions
v4.0.0
822e3dd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.0.0

Changelog

Unreleased

Full Changelog

Merged pull requests:

v4.0.0 (2024-06-10)

Full Changelog

Implemented enhancements:

  • Playnite web app is the only required service to run #341

Fixed bugs:

  • Major releases fail release pipeline #376

Closed issues:

  • Increased reliability via automated testing #348

v3.2.1 (2024-06-05)

Full Changelog

v3.2.0 (2024-06-05)

Full Changelog

Support for ARM devices and installable as HASS add-on.

Implemented enhancements:

  • Smaller playnite-web-app image #339
  • Support cloud hosted Mongo databases #332
  • Support ARM Docker images #329
  • Automate the packaging and release of the playnite-web-plugin #321
  • Package playnite-web as HASS add-ons #319

Fixed bugs:

  • Released images are not tagged with specific version, only major.minor-latest #372
  • fix: broken Mongodb connection #342
  • .devcontainer via devpod breaks docker mongo development environment #316

Closed issues:

  • Discussions and chat are in gitter.im #364
  • Shorten pr workflow run times #363
  • Removed self-hosted gh action runner image #346
  • PRs do not require publishing images as status check #344
  • Main branch is upcoming release, not the current release #338
  • Publish GitHub runner to ghcr.io and its source code is within this repo #331
  • Reduce effort to keep all versions in sync with one another #330
  • Contributing guidelines #235

Merged pull requests:

v3.1.4 (2024-05-24)

Full Changelog

Release summary v3.2.0 #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.

Merged pull requests:

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:

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:

Read more
Assets 4
Loading
0 Join discussion

v3.2.1

05 Jun 12:49
@github-actions github-actions
v3.2.1
390feca
This commit was signed with the committer’s verified signature.
andrew-codes Andrew Smith
SSH Key Fingerprint: cgjTKL1GgG8S7cp2rv4u4zh3aPUeb4RRqMoOj+focP0 Learn about vigilant mode.
Compare
Choose a tag to compare
v3.2.1

Changelog

v3.2.1 (2024-06-05)

Full Changelog

v3.2.0 (2024-06-05)

Full Changelog

Support for ARM devices and installable as HASS add-on.

Implemented enhancements:

  • Smaller playnite-web-app image #339
  • Support cloud hosted Mongo databases #332
  • Support ARM Docker images #329
  • Automate the packaging and release of the playnite-web-plugin #321
  • Package playnite-web as HASS add-ons #319

Fixed bugs:

  • Released images are not tagged with specific version, only major.minor-latest #372
  • fix: broken Mongodb connection #342
  • .devcontainer via devpod breaks docker mongo development environment #316

Closed issues:

  • Discussions and chat are in gitter.im #364
  • Shorten pr workflow run times #363
  • Removed self-hosted gh action runner image #346
  • PRs do not require publishing images as status check #344
  • Main branch is upcoming release, not the current release #338
  • Publish GitHub runner to ghcr.io and its source code is within this repo #331
  • Reduce effort to keep all versions in sync with one another #330
  • Contributing guidelines #235

Merged pull requests:

v3.1.4 (2024-05-24)

Full Changelog

Release summary v3.2.0 #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.

Merged pull requests:

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:

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:

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 automa...
Read more
Assets 4
Loading
0 Join discussion

v3.2.0

05 Jun 12:20
@github-actions github-actions
v3.2.0
a3fc1d7
This commit was signed with the committer’s verified signature.
andrew-codes Andrew Smith
SSH Key Fingerprint: cgjTKL1GgG8S7cp2rv4u4zh3aPUeb4RRqMoOj+focP0 Learn about vigilant mode.
Compare
Choose a tag to compare
v3.2.0

Changelog

v3.2.0 (2024-06-05)

Full Changelog

Support for ARM devices and installable as HASS add-on.

Implemented enhancements:

  • Smaller playnite-web-app image #339
  • Support cloud hosted Mongo databases #332
  • Support ARM Docker images #329
  • Automate the packaging and release of the playnite-web-plugin #321
  • Package playnite-web as HASS add-ons #319

Fixed bugs:

  • fix: broken Mongodb connection #342
  • .devcontainer via devpod breaks docker mongo development environment #316

Closed issues:

  • Discussions and chat are in gitter.im #364
  • Shorten pr workflow run times #363
  • Removed self-hosted gh action runner image #346
  • PRs do not require publishing images as status check #344
  • Main branch is upcoming release, not the current release #338
  • Publish GitHub runner to ghcr.io and its source code is within this repo #331
  • Reduce effort to keep all versions in sync with one another #330
  • Contributing guidelines #235

Merged pull requests:

v3.1.4 (2024-05-24)

Full Changelog

Release summary v3.2.0 #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.

Merged pull requests:

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:

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:

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](https://[api.playnite.link/docs/manual/advanced/cmdlineArguments.html](https://api.playnite.link/docs/manual/advanced/cmdlineArg...
Read more
Assets 4
Loading
0 Join discussion

v3.1.4

24 May 15:16
@github-actions github-actions
v3.1.4
e4ffbba
This commit was signed with the committer’s verified signature.
andrew-codes Andrew Smith
SSH Key Fingerprint: cgjTKL1GgG8S7cp2rv4u4zh3aPUeb4RRqMoOj+focP0 Learn about vigilant mode.
Compare
Choose a tag to compare
v3.1.4

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:

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:

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:

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:

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:

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)

image

My Library Screenshot

browse-screenshot

Basic filtering by name and feature

image

image

Implemented enhancements:

Read more
Assets 4
Loading
0 Join discussion

v3.1.3

12 May 23:19
@github-actions github-actions
v3.1.3
c7d2a3b
This commit was signed with the committer’s verified signature.
andrew-codes Andrew Smith
SSH Key Fingerprint: cgjTKL1GgG8S7cp2rv4u4zh3aPUeb4RRqMoOj+focP0 Learn about vigilant mode.
Compare
Choose a tag to compare
v3.1.3

Changelog

Unreleased

Full Changelog

Merged pull requests:

  • 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:

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:

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:

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:

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)

image

My Library Screenshot

browse-screenshot

Basic filtering by name and feature

image

image

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:

Read more
Assets 3
Loading
0 Join discussion

v3.1.2

10 May 14:43
@github-actions github-actions
v3.1.2
88ca7d0
This commit was signed with the committer’s verified signature.
andrew-codes Andrew Smith
SSH Key Fingerprint: cgjTKL1GgG8S7cp2rv4u4zh3aPUeb4RRqMoOj+focP0 Learn about vigilant mode.
Compare
Choose a tag to compare
v3.1.2

Changelog

v3.1.2 (2024-05-10)

Full Changelog

Fixed bugs:

  • Application Error TypeError: Cannot read properties of null (reading 'name') #301
  • Platform (+1) should never be shown #208

Merged pull requests:

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:

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:

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:

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)

image

My Library Screenshot

browse-screenshot

Basic filtering by name and feature

image

image

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](https://g...
Read more
Assets 3
Loading
0 Join discussion