Skip to content

Conversation

adinauer
Copy link
Member

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.

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.
@adinauer
Copy link
Member Author

At what point should the new module be added to .craft.yml? Before running any release or before going stable?

Comment on lines +33 to +36
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The correct order is:

  1. release without the craft modules (.craft.yml)
  2. add the released version to the release registry manually
  3. add the modules to craft modules (.craft.yml)
  4. enjoy automatic releases

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, will update later

Copy link
Member Author

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.

@jan-auer
Copy link
Member

jan-auer commented Dec 1, 2022

We're moving CI to GHA, please rebase onto master.

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.

3 participants