Repository navigation
Conversation
Issues FoundNo issues with your PR description were found. Next Steps
Thank you for your contribution! If you need any help, please reach out on our Discord server. ❤️ |
maroun2
force-pushed
the
update/deck-progress-tracker-1.5.1
branch
from
November 16, 2026 15:23
8a0c51d to
61e9c0a
Compare
Contributor
Author
|
Testing reports for other plugins:
|
maroun2
force-pushed
the
update/deck-progress-tracker-1.5.1
branch
from
November 16, 2026 15:27
61e9c0a to
43e7aa3
Compare
maroun2
marked this pull request as ready for review
November 16, 2026 15:41
Contributor
Author
|
Can I do something more to get this PR moving. Or just wait? |
This branch is waiting to be deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update Deck Progress Tracker to 1.5.2
Updates Deck Progress Tracker from 1.3.6 (
b83abe4) to 1.5.2 (58656cb, tag1.5.2). The plugin repository is unchanged.1.4.x (1.4.7 release notes)
1.5.0 (release notes)
1.5.1 (release notes)
howlongtobeatpyand its dependencies are now committed inpy_modules/vendor, pinned and hashed inrequirements.txt. They are pure-Python (py3-none-any) wheels only, with no compiled.sofiles. The standard store build (decky plugin build) therefore includes them withoutrelease.sh, a Dockerfile or a custom backend. Each vendored package keeps its license files in its*.dist-infodirectory.1.5.2 (release notes)
Build check
58656cb(1.5.2) with Decky CLI 0.0.7, the same command CI uses:decky plugin build -b -o <out> -s directory <plugin>. It succeeded, andpnpm-lock.yamlis atlockfileVersion: '9.0'.py_modules/vendor(492 entries), includinghowlongtobeatpy.main.pythe way Decky Loader does, on CPython 3.11 (the Python embedded in Decky Loader ≤ 3.2.10) and on CPython 3.14 (Decky Loader ≥ 3.3.0). On both versions,howlongtobeatpyimported from the bundledpy_modules/vendor, no native extensions were loaded, and live HLTB lookups (Hollow Knight, Celeste, Portal 2, plus a candidate search) returned correct results.Task Checklist
Developer
Plugin
Tested on SteamOS Stable 3.9.5 (build 20261023.100) and Beta 3.9.6 (build 20261112.101), both with Decky Loader v3.3.1. On Stable, 1.5.0 was installed from its release URL and a library sync ran with 0 errors in the log. On Beta, I installed the store-built 1.5.2 zip (Decky CLI 0.0.7, including
py_modules/vendor) through Decky's installer. Results on Beta:py_modules/vendor);The previous Beta run on 1.5.1 also confirmed tag badges on library tiles.
Backend
Community
I have tested Decky DoT DNS (#1180) and Audio Output Switcher (#1103). The links to both reports are in this comment.
Testing