unyt-org/datex

Add cargo dry run in commit action

Open

#456 opened on Oct 13, 2025

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Rust (2 forks)github user discovery
cigood first issue

Repository metrics

Stars
 (14 stars)
PR merge metrics
 (Avg merge 53d 4h) (6 merged PRs in 30d)

Description

We should run a cargo publish dry run as a required check to be passed before we create the published packages, as this should never fail then.

Contributor guide

Research direction
Add a cargo publish dry run step in the CI workflow (e.g., GitHub Actions) to ensure the package can be published without errors before creating releases. Modify the commit action to include this check.
Tech stack
rust
Domain
devopsci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
RustCI/CD basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70