-
Notifications
You must be signed in to change notification settings - Fork 200
doc(self-managed): rework the references of camunda release and namespaces #5626
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
base: main
Are you sure you want to change the base?
Conversation
👋 🤖 🤔 Hello, @leiicamundi! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.7/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
@camunda/tech-writers could you please proceed to the review and release a doc version as some files requires updates on stable 8.7 of the doc |
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.
Would you consider this name change a breaking change? I would likely add this to https://docs.camunda.io/docs/reference/announcements-release-notes/overview/.
Also, you checked the box that this is part of a scheduled alpha or minor, but I don't see a label attached to this PR. What alpha or minor is this specific to?
Hi @christinaausley, We don't consider it as a breaking change as the user was not relying on that specific variable previously. |
The preview environment relating to the commit 8ac3b1c has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-5626/ |
Description
Following camunda/camunda-deployment-references#250, we have reworked our usage of the
namespace
andhelm release name
across our documentation and script.This PR apply this update by extracting some hard coded namespace values and release names
I've also reverted the reference of rosa-8.8 as we should now use
main
branch of https://github.com/camunda/camunda-deployment-references for any 8.8 targetWhen should this change go live?
bug
orsupport
label)available & undocumented
label)hold
label)low prio
label)PR Checklist
/docs
directory (version 8.8)./versioned_docs
directory.@camunda/tech-writers
unless working with an embedded writer.