aguacero7/rkik

Packaging & CI Setup

Open

#4 opened on Jun 30, 2025

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Rust (6 forks)auto 404
CI/CDenhancementgood first issue

Repository metrics

Stars
 (57 stars)
PR merge metrics
 (PR metrics pending)

Description

Packaging & CI Setup

Goal

Automate build/lint/test checks and prepare rkik for clean publishing and installation via cargo install.

Tasks

  • Enhance Cargo.toml with:
    • license
    • repository, homepage
    • keywords, categories
  • Optionally publish the crate to crates.io
  • Enforce semantic versioning (semver)
  • Add binary section in [package.metadata] if needed
  • Build packages using sync feature with permissions (CAP_SYS_TIME)

Expected Outcome

  • Fully automated quality pipeline
  • Clean packaging for Rust ecosystem
  • Easy installation via cargo install rkik

Contributor guide

Research direction
Review the remaining task about enforcing semantic versioning, then examine existing Cargo.toml and CI configuration (if any) to understand how to add a semver check. Look into tools like cargo semver checks or a GitHub Action for versioning.
Tech stack
rust
Domain
devopstoolingcli
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCargoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75