Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Rust crate publishing and versioning

Open
#178 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, rust
Domain
ci-cd, documentation, release

Research direction

Start by locating the manifests for lbr-prelude and lbr-prelude-derive and the repository's CI configuration, then verify the crates.io and GitHub Pages or docs.rs publishing paths. Done means both crates are versioned v1, CI publishes on tag push, documentation has an agreed hosting path, and a git tag is pushed.

Written by the indexing model from the issue text.

Description

Publish lbr-prelude and lbr-prelude-derive to crates.io

TODO

  • bump version to v1
  • configure CI to publish crates to crates.io on tag push
  • if not to difficult, generate documentation to github pages (otherwise, using docs.rs is also sufficient)
  • push a git tag
Dominant language
Haskell
Stars
32
Forks
1
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mlabs-haskell/lambda-buffers

All issues in mlabs-haskell/lambda-buffers

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.