Skip to content

Bump SDK pin to 3.4.11#1

Open
peektism wants to merge 1 commit into
OpenZeppelin:mainfrom
peektism:bump-sdk-3.4.11
Open

Bump SDK pin to 3.4.11#1
peektism wants to merge 1 commit into
OpenZeppelin:mainfrom
peektism:bump-sdk-3.4.11

Conversation

@peektism
Copy link
Copy Markdown
Collaborator

@peektism peektism commented May 18, 2026

Summary

  • daml.yaml: sdk-version: 3.4.10 → 3.4.11
  • README.md: requirements lines updated to match (Installation block and Requirements list)
  • DAR target (LF 2.1) is unchanged, so consumers built against 3.4.10 or 3.4.11 both keep working

PUBLIC_AUDITS.md is intentionally left at SDK 3.4.10 — it records what the 2026-03-04 audit pass actually ran on, and would be inaccurate if bumped.

Verification

Built and tested locally on 2026-05-18 with OpenJDK 21.0.11 / DPM SDK 3.4.11:

  • dpm build — clean
  • dpm test — 4/4 ok, 0 failures

Test plan

  • CI build passes on 3.4.11
  • CI tests pass on 3.4.11
  • Downstream consumers (canton-stablecoin, canton-token-template) keep building when they ingest a fresh DAR built from this branch

🤖 Generated with Claude Code

daml.yaml sdk-version 3.4.10 → 3.4.11. README requirements lines updated to
match. DAR target (LF 2.1) is unchanged, so consumers built against 3.4.10
or 3.4.11 keep working.

Verified 2026-05-18: dpm build clean, dpm test 4/4 ok on OpenJDK 21.0.11 /
DPM SDK 3.4.11. PUBLIC_AUDITS.md is left at SDK 3.4.10 because that is the
audit record from 2026-03-04 and reflects what was actually run.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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