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

Reorganize sourcegen from crate to submodule in oq3_syntax #27

Merged
merged 2 commits into from
Jan 13, 2024

Conversation

jlapeyre
Copy link
Collaborator

The sourcegen crate was published by rust-analyzer. But it was broken, I pointed this out and they said publishing at all was a mistake and removed it (or stopped publishing it).

So we copied the crate into our workspace. But in fact it is one file, used in one crate (oq3_syntax). So we move the code to a module (a file) in oq3_syntax and deleted the crate.

The sourcegen crate was published by rust-analyzer. But it was
broken, I pointed this out and they said publishing at all
was a mistake and removed it.

So we copied the crate into our workspace. But in fact it is
one file, used in one crate (oq3_syntax). So we move the
code to a module (a file) in oq3_syntax.
@jlapeyre jlapeyre merged commit 6d8fb5e into main Jan 13, 2024
2 checks passed
@jlapeyre jlapeyre deleted the sourcegen-crate-to-mod branch January 13, 2024 07:11
jlapeyre added a commit to mtreinish/openqasm3_parser that referenced this pull request Jan 13, 2024
jlapeyre added a commit that referenced this pull request Jan 21, 2024
* Add CI workflow to publish crates on tag/release

This commit adds a new github actions work to publish the package's
crates to crates.io. This new CI job run cargo publish on the respective
crates in the correct order to publish the entire workspace.

* Update package dirs after #13 and #15

* Update package dirs after #27

* Choose names that better describe actions taken

* Put list of crates to release (publish on crates.io) in topo order

---------

Co-authored-by: John Lapeyre <jlapeyre@users.noreply.github.com>
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

Successfully merging this pull request may close these issues.

None yet

1 participant