-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add explanation for order of actions when adding a new SDK / module #85
base: master
Are you sure you want to change the base?
Conversation
It was unclear to me whether the files are needed for pre-releases and when the PR has to be merged in relation to performing the release.
At what point should the new module be added to |
1. update `.craft.yml` config to publish new package to your registry and GH | ||
2. cut the release | ||
3. update craft config to publish to release registry | ||
4. PR to this repository to manually add published new package. See steps below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The correct order is:
- release without the craft modules (.craft.yml)
- add the released version to the release registry manually
- add the modules to craft modules (.craft.yml)
- enjoy automatic releases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, will update later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's work in progress to make this easier / unnecessary. So let's wait with this PR.
We're moving CI to GHA, please rebase onto |
It was unclear to me whether the files are needed for pre-releases and when the PR has to be merged in relation to performing the release.