Store submissions: v0.4.0 (release 407350097) #28
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
backmeupplz/plainwallet#28
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@backmeupplz — store submission outcomes. Release policy is automatic publication after approval for enabled stores; Play targets production. Only successful per-store outcomes confirm a submission request. Each outcome includes its evidence attempt; older outcomes are historical, not proof of current-attempt success. Paused/skipped stores made no submission attempt in that reported attempt. Submitted is not approved/live.
Release: https://github.com/backmeupplz/plainwallet/releases/tag/v0.4.0
Run: https://github.com/backmeupplz/plainwallet/actions/runs/37861270955
chrome
firefox
play
Play commit requests review with managed publishing disabled (owner-confirmed, not API-verified); confirm Changes in review and eventual production availability in Publishing overview. Chrome PENDING_REVIEW with a DEFAULT_PUBLISH receipt will publish after approval; STAGED or legacy/uncertain pending reviews require explicit reconciliation, not another submission. Chrome PUBLISHED and AMO public indicate public store state; pending states never prove live availability. Legacy Play commits are not proof of automatic production rollout.