Skip to content

chore: remove obsolete historical tier listings - #4

Merged
0xSachinK merged 2 commits into
releases/stagingfrom
codex/remove-obsolete-release-tiers
Jul 30, 2026
Merged

chore: remove obsolete historical tier listings#4
0xSachinK merged 2 commits into
releases/stagingfrom
codex/remove-obsolete-release-tiers

Conversation

@0xSachinK

Copy link
Copy Markdown
Member

Summary

  • delete the three all-platform historical-taker manifests from the retired staging release ref
  • delete the three historical Earn manifests from the same ref
  • remove releases/staging as a GitHub Pages publication trigger so this stale ref cannot overwrite the canonical list

Safety

  • canonical main is unchanged and retains all six chargeback-only staging/production entries
  • no on-chain groups or memberships are mutated
  • history is preserved; this is a normal cleanup commit

Validation

  • npm run check (0 obsolete groups on this retired ref)
  • source scan for legacy tier slugs/IDs is clean
  • current Pages deployment from main contains only the six canonical chargeback-only groups

@0xSachinK

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5e2066a923

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/workflows/publish.yml Outdated
branches:
- main
- releases/staging
workflow_dispatch:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Guard manual dispatches against the retired staging ref

Removing the staging branch from the push filter does not prevent a maintainer from selecting releases/staging when invoking the remaining workflow_dispatch. In that scenario, actions/checkout builds this ref—which now contains zero group manifests—and the schema permits the empty list, so the deploy step can still overwrite the canonical Pages artifact with groups: []. Remove manual dispatch or add a job-level guard restricting deployments to refs/heads/main.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in b856d63: removed workflow_dispatch from the retired release ref as well, so it cannot publish through either pushes or manual dispatches. The canonical main workflow remains unchanged.

@0xSachinK

Copy link
Copy Markdown
Member Author

Codex review cycle 1: fixed the manual-dispatch publication edge in b856d63. No findings deferred or rejected. Local npm run check and the obsolete-source scan pass.

@0xSachinK

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: b856d63b48

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@0xSachinK
0xSachinK merged commit 3c1f75c into releases/staging Jul 30, 2026
1 check passed
@0xSachinK
0xSachinK deleted the codex/remove-obsolete-release-tiers branch July 30, 2026 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant