Skip to content

Clarify the minimum npm versions supporting v1.0 @-prefixed component envelope fields #4223

Open

Description

@AndrewXiGua

The current upstream source supports @CatalogId, @accessibility, @metadata, and @Checks, but the published @a2ui/[email protected] package still uses bare component envelope keys.

Could you clarify the release status and minimum supported npm versions for these changes?

As of November 13, 2026:

  • The latest npm version is 0.15.0, published on November 2.
  • PR #4037, merged on November 11, added dual-read support for prefixed and legacy bare v1.0 component envelope keys.
  • PR #4044 subsequently updated the specification, schemas, and emitted output to use the prefixed keys.
  • I compared the installed message processor, payload validator, and common schema files against the official npm 0.15.0 tarball; they match.

Activity

  1. added
    status: needs-triageauto-managed: https://github.com/a2ui-project/a2ui/blob/main/scripts/triage.mjs
    on Nov 13, 2026
  2. added
    P2The team intends to work on this in the near future, or at a lower priority.
    and removed
    status: needs-triageauto-managed: https://github.com/a2ui-project/a2ui/blob/main/scripts/triage.mjs
    on Nov 13, 2026
  3. self-assigned this
    on Nov 13, 2026
  4. Varun-S10 commented on Nov 13, 2026

    @Varun-S10
    Collaborator

    Hi @AndrewXiGua, Thank you for raising the issue. We appreciate you taking the time to share your thoughts with us.
    Hi @gspencergoog, could you please take a look?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions