Skip to content

Publish 0.2.0 to crates.io #1

Closed

Description

@olekslitus

loko 0.2.0 goes to crates.io once the first pull request is merged. The loko crate name already belongs to the same owner (0.1.0, 2022, an unrelated task-scripting crate); the other names (loko-clock, loko-random, loko-env, loko-console, loko-store, loko-object-store, loko-macros) are new.

  • Publish in dependency order: loko-macros, the service crates, loko-object-store, then loko (needs the owner's crates.io login).
  • Decide whether to yank loko 0.1.0, so cargo add loko never suggests it.
  • Move lakekit, Timelake, and lakeglass from the git dependency to the published version.

Spec: 0001, milestone 0.2.

Activity

  1. olekslitus commented on Oct 22, 2026

    @olekslitus
    ContributorAuthor

    Published 2026-10-22: loko and loko-clock, loko-random, loko-env, loko-console, loko-store, loko-object-store, and loko-macros at 0.2.0 (release v0.2.0). lakekit 0.1.0 depends on them by version, and Timelake does too in polythings/timelake#186. Still open: whether to yank loko 0.1.0 (the 2022 crate), which is the owner's call, and moving lakeglass over when it uses loko.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions