Skip to content

fix(milestones): a milestone can pay out more than its first issue - #675

Open
yggdrasilworld wants to merge 2 commits into
MergeFi:mainfrom
yggdrasilworld:fix/milestone-multi-issue-578
Open

yggdrasilworld wants to merge 2 commits into
MergeFi:mainfrom
yggdrasilworld:fix/milestone-multi-issue-578

Conversation

@yggdrasilworld

Copy link
Copy Markdown

What

resolveIssue asserted status->IN_PROGRESS on every call — the first resolve moved FUNDED->IN_PROGRESS, so the second hit IN_PROGRESS->IN_PROGRESS (invalid) and threw. A milestone could only ever pay ONE issue.

Fix

Only transition when not already IN_PROGRESS.

Resolves #578

… UI renders

Both list() were bare find() — no relations, so the frontend's
adaptMilestone/adaptMaintenancePool got empty rows (no repository, sponsor,
escrow, issues).

Resolves MergeFi#591
resolveIssue asserted status->IN_PROGRESS on every call — the first resolve
moved FUNDED->IN_PROGRESS, so the second resolve hit IN_PROGRESS->IN_PROGRESS
which isn't a valid transition and threw. Only transition when not already
IN_PROGRESS.

Resolves MergeFi#578
@vercel

vercel Bot commented Oct 14, 2026

Copy link
Copy Markdown

@yggdrasilworld is attempting to deploy a commit to the chonilius' projects Team on Vercel.

A member of the Team first needs to authorize it.

This branch has not been deployed

No deployments
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.

A milestone can only ever pay out one issue — resolveIssue asserts IN_PROGRESS → IN_PROGRESS, which the state machine forbids

1 participant