-
Notifications
You must be signed in to change notification settings - Fork 113
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
Automatic releases of the GraphQL-CLI #1473
Comments
@ardatan @dotansimha If you have example of the release process that we can follow or any links to how this is setup that will be awesome. |
We are using changesets in GraphQL Codegen, GraphQL Mesh and GraphQL Tools. So you add changelogs in your PRs then it creates a PR for releasing packages when your PRs are merged. |
@ardatan yep. Seen that repo. I was looking into how we can compose changesets from underlying technologies. We will investigate and move to changesets in graphback and then experiment how to get that into the repo here. |
@wtrocki It also helps us to maintain packages seperately by following semver. |
Yep.. Very aware of the famous "React Apollo" update :D and how nicely codegen managed to get around it. |
@ardatan in more recent matters. Could you try if you can release v4.1.0-beta2 orsomething using current scripts. |
@ardatan Update. We cannot use current script so going to use lerna for releases. |
@wtrocki We could have helped you switching to changesets instead of lerna because we removed lerna on purpose a while ago. |
Agree with @ardatan on that. We decided to drop Lerna since Yarn Workspaces manages deps linking for us, and there is no reason to use Lerna for releases only. |
@ardatan yep. There is short term plan and long term plan.
I have seen changesets being used but did not seen how to use it. Any link will help us to add it here. |
We simply want to release cli for now- there was no release for 4 months and local release fails with 404. For changesets we actually have added lerna chanelog recently (Moving to changesets will require us to do some investigation and do graphback first and document the process). Then we can move that to cli by exposing changelogs. |
TL;DR - We will do changesets 100% but I do not feel comfortable to drop it in hurry without understanding the process (especially on graphback where we have it perfected), but in timeframe of couple weeks we will be ok to move. |
Releases are done currently from master, but it will be great to be able to release things from releases tab etc. Current release script were failing to me (Were getting 404 for npm when trying to publish packages)
https://github.com/Urigo/graphql-cli/blob/master/scripts/release.js
The text was updated successfully, but these errors were encountered: