Plugin Maintenance

Plugin Maintenance

This page covers the normal upkeep flow for Proton Pulse after the first store submission.

Related docs:

• Developer Guide
• On-Device Test Plan
• Data Cache and Metrics

Repos

• Plugin repo: /home/mike/src/decky-proton-pulse-project/decky-proton-pulse
• Decky database repo: /home/mike/src/decky-proton-pulse-project/decky-plugin-database
• Plugin repo URL: git@github.com:mdeguzis/decky-proton-pulse.git
• Database fork URL: git@github.com:mdeguzis/decky-plugin-database.git
• Database upstream: https://github.com/SteamDeckHomebrew/decky-plugin-database.git

Normal Update Flow

1. make the plugin changes in decky-proton-pulse
2. run local checks
3. commit and push the plugin repo
4. tag or release if needed
5. update the submodule in decky-plugin-database
6. push the database branch
7. open or update the Decky database PR

Update The Plugin Repo

From /home/mike/src/decky-proton-pulse-project/decky-proton-pulse:

git status
make coverage
make build
git add <files>
git commit -m "<message>"
git push origin <branch>

Before pushing a store-facing update:

• make sure package.json version is correct
• keep LICENSE present
• avoid committing unrelated generated churn unless you want it in the release

Cut A Tag Or GitHub Release

If the update is release-worthy:

git checkout main
git pull --ff-only origin main
git tag <tag-name>
git push origin <tag-name>

Examples:

• v0.2.0
• v0.2.1
• v0.3.0-rc1

Update The Decky Database Submodule

From /home/mike/src/decky-proton-pulse-project/decky-plugin-database:

git remote -v
git checkout main
git pull --ff-only upstream main
git checkout -b update/decky-proton-pulse-<version>

What you want:

• origin points to your fork
• upstream points to SteamDeckHomebrew/decky-plugin-database

Then update the submodule:

cd plugins/decky-proton-pulse
git fetch --tags origin
git checkout <plugin-commit-or-tag>
cd ../..
git add plugins/decky-proton-pulse
git commit -m "Update Decky Proton Pulse to <version-or-tag>"
git push -u origin update/decky-proton-pulse-<version>

Useful checks:

git submodule status plugins/decky-proton-pulse
git status
git diff --submodule

Open Or Update The Decky Database PR

Open a PR from your fork branch into:

• base repo: SteamDeckHomebrew/decky-plugin-database
• base branch: main

Suggested update title:

• Update Decky Proton Pulse to <version>

Suggested PR body:

## Summary
- Update Decky Proton Pulse in the plugin database
- Submodule points to: <commit-sha>

## Plugin
- Repo: https://github.com/mdeguzis/decky-proton-pulse
- Version: <version>
- Tag: <tag-or-none>
- License: BSD-3-Clause

## Testing
- Tested on a real Steam Deck
- Verified:
  - report browsing and ranking
  - launch option apply
  - logs
  - compatibility tools
  - settings and cache flows

## Notes
- Briefly call out user-visible fixes or changes

If there is already an open Decky database PR for Proton Pulse:

1. push the updated database branch
2. update the PR description if the version or testing notes changed
3. reply in the PR if reviewers asked for something specific

Handle Review Follow-Ups

If Decky reviewers request changes:

1. update decky-proton-pulse
2. commit and push the plugin repo changes
3. in decky-plugin-database/plugins/decky-proton-pulse, checkout the new plugin commit
4. commit the updated submodule pointer
5. push the same database branch
6. reply on the PR with a short summary of what changed

Keep Metadata Clean

Before store-facing updates, check:

• plugin.json
• package.json
• README.md
• LICENSE

Things to keep tidy:

• version numbers match the intended release
• publish metadata stays accurate
• README explains the plugin clearly
• no accidental AI co-author footers or stray metadata in release-facing commits
• no unrelated experiments bundled into a store update

Useful Recurring Checks

From decky-proton-pulse:

git status
git log --oneline --decorate -5
make coverage
make build
DECK_IP=$(cat ~/.deckip) make deploy-reload

From decky-plugin-database:

git status
git branch --show-current
git submodule status plugins/decky-proton-pulse

Fast Checklist

• plugin changes committed
• plugin branch pushed
• version updated if needed
• tests and checks passed
• release/tag created if desired
• database branch created from fresh upstream/main
• submodule updated to the intended plugin commit
• database branch pushed to fork
• Decky database PR opened or updated
• PR body includes version, commit, and testing notes