1
1
Fork
You've already forked ecformat
0

Rust crate on crates.io #27

Manually merged
BaumiCoder merged 11 commits from feature/11-Rust-crate-on-crates.io into main 2026年01月03日 11:35:01 +01:00

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 (a1f314a290 and b03def4413).
Furthermore, there seems to be no option to add --build to the cargo add ecformat entry 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).

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 (a1f314a29041ad52ac21acb213d1484a82b53933 and b03def441322a162a8db01fc0be1864384d8f10a). Furthermore, there seems to be no option to add `--build` to the `cargo add ecformat` entry 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](https://doc.rust-lang.org/cargo/reference/manifest.html#the-documentation-field)). 
To publish with newest version
To publish with newest versions
It is a CLI tool to use (before /) at build time
Use similar keywords as similar crate (e.g., taplo-cli and ec4rs)
They are not necessary for cargo build|test|doc
Within cargo package the build.rs is executed in a different directory.
Therefore, environment variables are needed to handle paths
correctly in all cases.
Excluding .gitignore and .editorconfig from crate breaks some tests
as this files are considered by ecformat itself.
Document Rust Crate in README
Some checks failed
/ changes (pull_request) Successful in 53s
/ lint_reuse (pull_request) Successful in 1m5s
/ lint_cargo_deny (pull_request) Waiting to run
/ lint_clippy (pull_request) Waiting to run
/ lint_rustfmt (pull_request) Waiting to run
/ lint_codespell (pull_request) Successful in 1m8s
/ lint_taplo (pull_request) Waiting to run
/ lint_yamllint (pull_request) Waiting to run
/ lint_cargo_udeps (pull_request) Waiting to run
/ lint_ecformat (pull_request) Successful in 8m33s
/ test (pull_request) Has been cancelled
6796adebb1
Fix copy & past mistake in URL
All checks were successful
/ test (pull_request) Successful in 4m16s
/ changes (pull_request) Successful in 50s
/ lint_reuse (pull_request) Successful in 1m5s
/ lint_cargo_deny (pull_request) Successful in 3m28s
/ lint_clippy (pull_request) Successful in 3m45s
/ lint_rustfmt (pull_request) Successful in 1m59s
/ lint_codespell (pull_request) Successful in 1m8s
/ lint_taplo (pull_request) Successful in 1m50s
/ lint_yamllint (pull_request) Has been skipped
/ lint_cargo_udeps (pull_request) Successful in 21m53s
/ lint_ecformat (pull_request) Successful in 2m48s
e5ff21d7a4
Author
Owner
Copy link

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

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
Author
Owner
Copy link

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)

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)
BaumiCoder manually merged commit 1732e8bd00 into main 2026年01月03日 11:35:01 +01:00
Author
Owner
Copy link

Some bugs from this PR were fixed in follow-up commits, which are linked in the issue #11.

Some bugs from this PR were fixed in follow-up commits, which are linked in the issue #11.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
EditorConfig
0.17.2
 Issues to support version 0.17.2 of the EditorConfig specification
Kind
Bug
 Something is not working
Kind
Chore
 Some tasks maintainig tasks
Kind
Documentation
 Documentation changes
Kind
Enhancement
 Improve existing functionality
Kind
Feature
 New functionality
Kind
Testing
 Issue or pull request related to testing
Packaging
About packaging the project for some platform
Priority
Critical
 The priority is critical
Priority
High
 The priority is high
Priority
Low
 The priority is low
Priority
Medium
 The priority is medium
Reviewed
Confirmed
 Issue has been confirmed
Reviewed
Duplicate
 This issue or pull request already exists
Reviewed
Invalid
 Invalid issue
Reviewed
Won't Fix
 This issue won't be fixed
Status
Abandoned
 Somebody has started to work on this but abandoned work
Status
Blocked
 Something is blocking this issue or pull request
Status
Need More Info
 Feedback is required to reproduce issue or to continue work
WIP
Work in progress (Assignee is working on this issue)
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
BaumiCoder/ecformat!27
Reference in a new issue
BaumiCoder/ecformat
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?