Skip to content

docs(changelog): draft v3.4.0 release notes and version bump#272

Merged
rjan90 merged 2 commits into
mainfrom
phi/prep-PDPverifier-upgrade-v3.4.0
May 22, 2026
Merged

docs(changelog): draft v3.4.0 release notes and version bump#272
rjan90 merged 2 commits into
mainfrom
phi/prep-PDPverifier-upgrade-v3.4.0

Conversation

@rjan90
Copy link
Copy Markdown
Contributor

@rjan90 rjan90 commented May 22, 2026

Summary

  • Draft v3.4.0 release notes in CHANGELOG.md with date and deployment fields left as TBD until rollout execution.
  • Bump PDPVerifier.VERSION to 3.4.0 so the eventual implementation bytecode reports the intended release version.

Notes

  • This intentionally excludes the local pdpverifier-upgrade.md process/template edits; those are still being iterated separately.
  • Deployment addresses, verification links, and release date should be finalized after Calibration and Mainnet rollout execution.

Validation

  • forge test (179 tests passing)

@FilOzzy FilOzzy added this to FOC May 22, 2026
@github-project-automation github-project-automation Bot moved this to 📌 Triage in FOC May 22, 2026
@rjan90 rjan90 self-assigned this May 22, 2026
@rjan90 rjan90 moved this from 📌 Triage to 🔎 Awaiting review in FOC May 22, 2026
@rjan90 rjan90 moved this to 🔎 Awaiting review in PDP May 22, 2026
@rjan90 rjan90 added this to the M4.2: mainnet GA milestone May 22, 2026
@rjan90 rjan90 marked this pull request as ready for review May 22, 2026 07:33
@rjan90 rjan90 requested a review from BigLep May 22, 2026 07:33
Comment thread src/PDPVerifier.sol
feeStatus.nextFeePerTiB = PDPFees.DEFAULT_FEE_PER_TIB;
}

string public constant VERSION = "3.3.0";
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The previous change (#270) bumped it to 3.3.0. I don't have a strong opinion on this though. But we didn't deploy any 3.3.0.

Copy link
Copy Markdown
Contributor Author

@rjan90 rjan90 May 22, 2026

Choose a reason for hiding this comment

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

The reason for the fast-forward here is that we shipped v3.3.0 release https://github.com/FilOzone/pdp/releases/tag/v3.3.0 which only had the library changes.

So the fast-forward from v3.2.0 to v3.4.0 in the deployed bytecode is to align them

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Added a changelog note explaining the version fast-forward: the live proxies still report 3.2.0, v3.3.0 was library-only with no PDPVerifier deployment, and this rollout intentionally moves deployed VERSION() from 3.2.0 to 3.4.0.

@github-project-automation github-project-automation Bot moved this from 🔎 Awaiting review to ✔️ Approved by reviewer in FOC May 22, 2026
@rjan90 rjan90 merged commit a0ba1b0 into main May 22, 2026
3 checks passed
@rjan90 rjan90 deleted the phi/prep-PDPverifier-upgrade-v3.4.0 branch May 22, 2026 11:07
@github-project-automation github-project-automation Bot moved this from ✔️ Approved by reviewer to 🎉 Done in FOC May 22, 2026
@github-project-automation github-project-automation Bot moved this from 🔎 Awaiting review to 🎉 Done in PDP May 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🎉 Done
Status: 🎉 Done

Development

Successfully merging this pull request may close these issues.

4 participants