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.

Sign up for GitHub

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

Jump to bottom

Publish to crates.io #250

Open
sandreim opened this issue Mar 7, 2023 · 3 comments
Open

Publish to crates.io #250

sandreim opened this issue Mar 7, 2023 · 3 comments
Assignees
@AndreiEres

Comments

@sandreim
Copy link
Collaborator

sandreim commented Mar 7, 2023

No description provided.

@AndreiEres
Copy link
Collaborator

I think we can change the deployment scheme to setup publishing and appropriate docker tags (#263):

  1. We deploy only on new tags
  2. We use version tags like v0.1.9
  3. Tags are used for docker images
  4. After deploying we publish the new version to crates.io

@sandreim What do you think?

@AndreiEres AndreiEres self-assigned this Mar 20, 2023
@sandreim
Copy link
Collaborator Author

sounds good to me

@AndreiEres
Copy link
Collaborator

@sandreim @vstakhov
To publish it, we need to publish all packages we have, including common modules in essentials or metadata-checker, which we use only in CI. I think we need to prefix it. A prefix "polkadot-" could not bring the desired level of recognition for essentials but sufficient for kvdb. So my suggestion is to use the prefix "polkadot-" until it's clear, otherwise — "polkadot-introspector-". What do you think about it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AndreiEres AndreiEres

Labels
None yet
Projects
Polkadot Introspection
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AndreiEres @sandreim