Skip to content

chore: require aleph-message 1.3.0 for V-PROGRAM support - #291

Merged
odesenfans merged 2 commits into
mainfrom
chore/aleph-message-1.3
Aug 25, 2026
Merged

chore: require aleph-message 1.3.0 for V-PROGRAM support#291
odesenfans merged 2 commits into
mainfrom
chore/aleph-message-1.3

Conversation

@odesenfans

Copy link
Copy Markdown
Contributor

Summary

  • Bump the aleph-message floor from >=1.1.1 to >=1.3.0. 1.3.0 adds MessageType.v_program, VerifiableProgramMessage and the registers.launch measurement shape; without it, MessageType.v_program is an AttributeError and V-PROGRAM messages fail to parse in get_messages / get_message / watch_messages.
  • Add unit tests covering listing and fetching a V-PROGRAM message and the msgTypes=V-PROGRAM filter parameter.

No SDK code changes are needed for read-side support: everything goes through aleph_message.parse_message.

Test plan

  • pytest tests/unit with aleph-message 1.3.0 (238 passed)
  • Manual: get_messages(MessageFilter(message_types=[MessageType.v_program])) against api2/api3 (0 results today, parses fine)

🤖 Generated with Claude Code

https://claude.ai/code/session_018hGRkZE1a3i19yrf2uBasD

aleph-message 1.3.0 adds MessageType.v_program and VerifiableProgramMessage.
Bump the floor so listing and fetching V-PROGRAM messages is guaranteed to
parse, and cover it with unit tests.
foxpatch-aleph
foxpatch-aleph previously approved these changes Aug 25, 2026

@foxpatch-aleph foxpatch-aleph 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.

A clean, minimal PR that bumps the aleph-message floor from >=1.1.1 to >=1.3.0 to gain V-PROGRAM support (MessageType.v_program, VerifiableProgramMessage, registers.launch measurement shape). No SDK code changes are needed since read-side parsing goes through aleph_message.parse_message. The three new tests cover listing V-PROGRAM messages, fetching a single V-PROGRAM message by hash with type validation, and HTTP param serialization for the msgTypes filter — all following existing test patterns (make_mock_get_session, async with, MessageFilter). The mock V-PROGRAM message payload includes all required fields and uses ignore_invalid_messages=False to ensure the fixture actually parses. No correctness, security, or quality concerns.

@github-actions

Copy link
Copy Markdown

Failed to retrieve llama text: POST 502: Bad Gateway

@foxpatch-aleph foxpatch-aleph 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.

This PR correctly bumps the aleph-message dependency floor from >=1.1.1 to >=1.3 (equivalent to >=1.3.0 per PEP 440) to enable V-PROGRAM message support via MessageType.v_program, VerifiableProgramMessage, and the registers.launch measurement shape. No SDK code changes are needed since read-side parsing goes through aleph_message.parse_message. The three new tests are well-structured and cover listing V-PROGRAM messages, fetching a single V-PROGRAM message, and the msgTypes=V-PROGRAM HTTP filter parameter serialization. The mock data includes all required V-PROGRAM fields with a realistic SEV-SNP verification configuration. All new tests pass, and pre-existing failures in the suite are unrelated (missing optional secp256k1 dependency).

@odesenfans
odesenfans merged commit 5409a03 into main Aug 25, 2026
5 checks passed
@odesenfans
odesenfans deleted the chore/aleph-message-1.3 branch August 25, 2026 13:39
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.

2 participants