Rust crate on crates.io #27
No reviewers
Labels
No labels
Compat/Breaking
EditorConfig
0.17.2
Kind
Bug
Kind
Chore
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Testing
Packaging
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
WIP
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
BaumiCoder/ecformat!27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/11-Rust-crate-on-crates.io"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Resolves #11
User perspective
This Pull Request contains all changes to release ecformat also as Crate
(on crates.io and on Codeberg.org) within the CI workflow.
Developer perspective
Some small changes were also necessary to fix the Crate packaging (
a1f314a290andb03def4413).Furthermore, there seems to be no option to add
--buildto thecargo add ecformatentry on the righthand sight on crates.io. The option is at least mentioned in the README.The doc comments seem to be sufficient, and the Crate should be usable as lib. I did not add a link to docs.rs in the
Cargo.toml, as this is the default (see documentation).Currently, the cargo-deny fails (only in the CI) due to a bug in the Action: https://github.com/EmbarkStudios/cargo-deny-action/issues/103
Reason for this fail was a bug in the Forgejo Runner: https://code.forgejo.org/forgejo/runner/issues/1233
(Could be fixed with a workaround on the runner)
Some bugs from this PR were fixed in follow-up commits, which are linked in the issue #11.