-
Notifications
You must be signed in to change notification settings - Fork 571
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
Rename distribution artifact from camunda-cloud-zeebe to camunda-zeebe #8912
Conversation
afd24ce
to
9d97c56
Compare
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.
Reviewed in the sense that I checked that there are no more mentions of camunda-cloud-zeebe
, but really I have no idea what might break because of this 😅
I think renaming the artifact won't break much, as it's pretty self contained. It might break other scripts which expect the name in other repositories, but I'm not really aware of any. |
9d97c56
to
0ec9bc2
Compare
Just fixed merge conflicts, nothing else. bors merge |
8912: Rename distribution artifact from camunda-cloud-zeebe to camunda-zeebe r=npepinpe a=npepinpe ## Description This PR renames the distribution artifact produced by `dist` to `camunda-zeebe`. This aligns the artifact names with other Camunda 8 artifacts in order to avoid confusion between Camunda and Camunda Cloud. NOTE: I haven't tested the release since our release job picks up the scripts from `main`. I will test it once it's merged, but before the release. I anyway need to test the repo move before the release in April, so I would test them both then. ## Related issues closes #8911 Co-authored-by: Nicolas Pepin-Perreault <nicolas.pepin-perreault@camunda.com>
Build failed: |
bors r+ |
Description
This PR renames the distribution artifact produced by
dist
tocamunda-zeebe
. This aligns the artifact names with other Camunda 8 artifacts in order to avoid confusion between Camunda and Camunda Cloud.NOTE: I haven't tested the release since our release job picks up the scripts from
main
. I will test it once it's merged, but before the release. I anyway need to test the repo move before the release in April, so I would test them both then.Related issues
closes #8911
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/1.3
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation: