Skip to content

Release/v1.8.2#2060

Merged
iasonrovis merged 15 commits into
mainfrom
release/v1.8.2
Jul 3, 2026
Merged

Release/v1.8.2#2060
iasonrovis merged 15 commits into
mainfrom
release/v1.8.2

Conversation

@iasonrovis

Copy link
Copy Markdown
Contributor

Proposed changes

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

atepem and others added 15 commits July 1, 2026 13:20
Point each agent's defaultStakingProgramId at the cheapest new
(decoupled-activity) staking contract re-enabled in #2039:
- PredictTrader: PearlBetaMechMarketplace3 -> OmenstratIII (40 OLAS)
- Optimus: OptimusAlpha2 -> OptimusI (100 OLAS)
- Polystrat: PolygonBeta1 -> PolystratI (100 OLAS)
Basius already defaults to BasiusI (cheapest new).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Service CID -> bafybeif4r7ftadt5wz6k3abniud245yiazbmrivd4wr7mrqt2znudwgxpy
(carries the polymarket_trader max_edge 0.15 -> 0.30 change, trader#1004).
Polymarket template only; Omen (Trader Agent) untouched. Based on latest staging.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Mark the PettAi agent as terminally retired via `isPhasedOut: true`,
reusing the same phase-out mechanism as Agents.fun. Existing PettBro
instances can no longer run (Start disabled, excluded from auto-run, no
new-epoch nudges) and surface the phased-out alert prompting withdrawal.
`isAgentEnabled` stays true so the sidebar entry and withdraw/unstake
flow remain reachable — funds are not locked.

Update config and FundingRequirementStep tests to reflect PettAi's new
phased-out state (swap the blocked-but-not-phased-out case to Optimus).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…tracts

feat(staking): [OPE-1815] default new staking contracts for agents
…transitive subtree

dayjs@1.11.16 was published with semantic-release + @semantic-release/*
declared as runtime dependencies (legit dayjs has zero runtime deps),
pulling in sigstore <=4.1.0 and tripping the yarn audit gate on the new
HIGH advisory GHSA-52v5-jr5w-gjxr.

The root package.json already pins "dayjs": "1.11.13"; the frontend
resolutions block was missing it, so the frontend tree floated to the
compromised 1.11.16. Mirror the root pin and regenerate the lockfile,
removing the accidental semantic-release/sigstore/npm subtree.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
fix(deps): pin dayjs to 1.11.13 in frontend tree (CI yarn audit)
feat(agents): [OPE-1759] fully decommission PettBro (Pett.ai)
…-v0.40.0-rc6

chore: bump Polymarket trader to v0.40.0-rc6
@iasonrovis
iasonrovis merged commit 0055526 into main Jul 3, 2026
18 checks passed
@iasonrovis
iasonrovis deleted the release/v1.8.2 branch July 3, 2026 10:05
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.

5 participants