Store submissions: v0.4.0 (release 407350097) #28

Closed
opened 2026-10-08 23:49:36 +00:00 by github-actions[bot] · 0 comments
github-actions[bot] commented 2026-10-08 23:49:36 +00:00 (Migrated from github.com)

@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

{
  "store": "chrome",
  "state": "paused",
  "submission": "skipped",
  "reason": "Owner pause; no store access or submission attempted",
  "attempt": 2,
  "evidence": "selection"
}

firefox

{
  "store": "firefox",
  "version": "0.4.0",
  "versionId": 6557023,
  "state": "unreviewed",
  "autoPublishApproved": true,
  "publication": "automatic-after-approval",
  "attempt": 2,
  "evidence": "submission-job"
}

play

{
  "store": "play",
  "state": "paused",
  "submission": "skipped",
  "reason": "Owner pause; no store access or submission attempted",
  "attempt": 2,
  "evidence": "selection"
}

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.

@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 ```json { "store": "chrome", "state": "paused", "submission": "skipped", "reason": "Owner pause; no store access or submission attempted", "attempt": 2, "evidence": "selection" } ``` ### firefox ```json { "store": "firefox", "version": "0.4.0", "versionId": 6557023, "state": "unreviewed", "autoPublishApproved": true, "publication": "automatic-after-approval", "attempt": 2, "evidence": "submission-job" } ``` ### play ```json { "store": "play", "state": "paused", "submission": "skipped", "reason": "Owner pause; no store access or submission attempted", "attempt": 2, "evidence": "selection" } ``` 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
backmeupplz/plainwallet#28
No description provided.