Skip to content

Generated code names a published runtime version (1.0), and vendoring docs until then #115

Open

Description

@Kinflou

Part of ComlineProject/core#227. Proposal: ComlineProject/docs#163, proposals/offline/supply.md#generated-codes-dependencies.

  • When comline-runtime is on crates.io (a 1.0 requirement, see the runtime issue linked from Offline and air-gapped use core#227), generated Cargo.toml names a version instead of RUNTIME_REV's git rev.
  • Until then, document building generated code in a sealed network with cargo vendor.
  • Generated code reaches nothing but its peer.

Activity

  1. added
    1.0-blockerMust be done before the 1.0 announcement (docs conduct/readiness.md)
    on Nov 9, 2026
  2. Kinflou commented on Nov 15, 2026

    @Kinflou
    MemberAuthor

    Overlap with runtime#115: both say 'until published, document vendoring for sealed builds (cargo vendor)'. Proposal: this issue owns the doc for building generated code in a sealed network, since it is about the generated Cargo.toml and RUNTIME_REV; runtime#115 keeps publishing comline-runtime and the no-network rule. The version-naming half (generated Cargo.toml names a version instead of a git rev) is only here.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    1.0-blockerMust be done before the 1.0 announcement (docs conduct/readiness.md)P3Eventually

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions