Skip to content

Release v0.1.6 with pinned Nim dependency metadata for downstream builds - #2

Draft
hortinstein with Copilot wants to merge 2 commits into
masterfrom
copilot/fix-error-compiling
Draft

Release v0.1.6 with pinned Nim dependency metadata for downstream builds#2
hortinstein with Copilot wants to merge 2 commits into
masterfrom
copilot/fix-error-compiling

Conversation

Copilot AI commented May 23, 2026

Copy link
Copy Markdown

Downstream builds were resolving enkodo@0.1.5, which did not enforce the dependency constraints needed by current consumers and led to a compile failure (undeclared identifier: crypto_key_exchange). This PR publishes a new package version carrying the pinned dependency metadata and aligns docs to that release.

  • Package release metadata

    • Bumped /enkodo.nimble version from 0.1.5 to 0.1.6 so dependents can resolve a release with explicit dependency pins.
    • Keeps dependency constraints explicit in package metadata (flatty == 0.3.4, monocypher == 0.2.1) for deterministic resolution.
  • Documentation alignment

    • Updated README Deno import example to reference v0.1.6 instead of v0.1.5.
# enkodo.nimble
version = "0.1.6"
requires "flatty == 0.3.4"
requires "monocypher == 0.2.1"

Copilot AI linked an issue May 23, 2026 that may be closed by this pull request
Copilot AI changed the title [WIP] Fix error compiling the Nim build artifacts Release v0.1.6 with pinned Nim dependency metadata for downstream builds May 23, 2026
Copilot AI requested a review from hortinstein May 23, 2026 11:42
@hortinstein

Copy link
Copy Markdown
Owner

@claude can you ensure that monocypher == 0.2.1

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.

error compiling

2 participants