Skip to content

Request for release #18

Description

@zkfrov

Summary

Could the maintainers cut a tagged release (e.g. v0.1.0)? The repo has no tags or releases today, and since Nargo only supports tag or branch for git deps (no commit-SHA pinning), Noir consumers are forced to pin to a branch name — which can move or disappear at any time.

Context — how we use it

We depend on noir-lang/sha512 in defi-wonderland/aztec-standards for the escrow contract's key derivation path. Specifically, src/escrow_contract/src/key_derivation.nr calls sha512::digest inside sha512_to_grumpkin_scalar to derive the four master keys (nhk_m, ivsk_m, ovsk_m, tsk_m) for an escrow account.

Escrow's Nargo.toml is pinned to a feature branch:

sha512 = { git = "https://github.com/noir-lang/sha512", tag = "mv/use-bool-over-u1" }

We'd much rather pin to a stable, versioned tag.

Ask

We noticed #2 ("chore: Release 0.1.0") has been open since February 2025. Is there a plan to merge it and cut v0.1.0? If not, could one of the maintainers tag a release?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions