Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish on crates.io #67

Closed
samanpa opened this issue May 22, 2023 · 8 comments
Closed

Publish on crates.io #67

samanpa opened this issue May 22, 2023 · 8 comments

Comments

@samanpa
Copy link

samanpa commented May 22, 2023

Is there a plan to periodically publish updates of this crate to crates.io? Will like to use it externally without depending on git.

If this is not planned please feel free to close this issue.

@youknowone
Copy link
Member

Though the API is very unstable and quickly being changed, I want to publish parser related crates to crates.io.
Could you share which APIs do you use? It will be helpful to freeze APIs with priority.

@DimitrisJim
Copy link
Member

Could you share which APIs do you use? It will be helpful to freeze APIs with priority.

yeah, this discussion should also be made with other people who use the parser. Probably an RFC would be good to come to a consensus.

@mtshiba
Copy link

mtshiba commented Jun 11, 2023

If your reason for hesitating to publish this crate is that it is unstable and you want people to use the stable version as much as possible, you can publish a "nightly version" as follows:

[package]
name = "mtshiba-dummycrate-1"
version = "0.0.0-unstable.0" # The `unstable` part can be any other string. For example, alpha, beta, nightly, etc.
edition = "2021"
description = "A dummy crate for testing"
license = "MIT"

[dependencies]

https://stackoverflow.com/questions/46373028/how-to-release-a-beta-version-of-a-crate-for-limited-public-testing

You cannot install this crate with cargo install mtshiba-dummycrate-1, but you can install it by specifying the version explicitly like cargo install [email protected]. The same applies to adding dependencies to Cargo.toml.

Even if several versions have already been released, unstable versions cannot be used unless explicitly specified.

(If there is some other reason why a new version cannot be released right now, please ignore it.)

@youknowone
Copy link
Member

Parse trait seems very counterintuitive without #81. Other issues doesn't look like blocker for release.

@youknowone
Copy link
Member

#74 is another wishlist because it breaks API

@youknowone youknowone mentioned this issue Jul 2, 2023
@youknowone
Copy link
Member

I will publish 0.3.0 as current version

@youknowone
Copy link
Member

Working on this issue again. It will be done as soon as I resolve crate ownership problems.

@youknowone
Copy link
Member

Thank you all for patient! 0.3.0 is now published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants