Skip to content
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.

Sign up for GitHub

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

Replace <= and >= with single chars #4576

Merged
merged 2 commits into from
Nov 6, 2024
Merged

Replace <= and >= with single chars #4576

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2b32661
replace with ≤
akeller Nov 5, 2024
77740d5
add both chars
akeller Nov 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/apis-tools/spring-zeebe-sdk/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,10 @@ This project allows you to leverage Zeebe APIs ([gRPC](/apis-tools/zeebe-api/grp

## Version compatibility

| Camunda Spring SDK version | JDK | Camunda version | Bundled Spring Boot version |
| -------------------------- | ------ | --------------- | --------------------------- |
| 8.5.x | \>= 17 | 8.5.x | 3.2.x |
| 8.6.x | \>= 17 | 8.6.x | 3.2.x |
| Camunda Spring SDK version | JDK | Camunda version | Bundled Spring Boot version |
| -------------------------- | ---- | --------------- | --------------------------- |
| 8.5.x | ≥ 17 | 8.5.x | 3.2.x |
| 8.6.x | ≥ 17 | 8.6.x | 3.2.x |

## Add the Spring Zeebe SDK to your project

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/getting-started-orchestrate-microservices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ You must have access to a Camunda 8 SaaS account.

Additionally, you need the following:

- Java >= 8
- Java ≥ 8
- Maven
- IDE (IntelliJ, VSCode, or similar)
- Download and unzip or clone the [repo](https://github.com/camunda/camunda-platform-tutorials), then `cd` into `camunda-platform-tutorials/orchestrate-microservices/worker-java`
Expand Down
20 changes: 10 additions & 10 deletions docs/reference/notices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ At this point, Camunda is not aware of any specific attack vector in Tasklist al

#### How to determine if the installation is affected

You are Tasklist version (8.0.3 >= version <= 8.0.7) or <= 8.1.2
You are Tasklist version (8.0.3 ≥ version ≤ 8.0.7) or ≤ 8.1.2

#### Solution

Expand All @@ -142,7 +142,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper

#### How to determine if the installation is affected

You are using Zeebe, Operate or Tasklist version <= 1.2.11 or <= 1.3.6
You are using Zeebe, Operate or Tasklist version ≤ 1.2.11 or ≤ 1.3.6

#### Solution

Expand All @@ -168,7 +168,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper

#### How to determine if the installation is affected

You are using Zeebe, Operate or Tasklist version <= 1.2.8 or <= 1.1.9
You are using Zeebe, Operate or Tasklist version ≤ 1.2.8 or ≤ 1.1.9

#### Solution

Expand All @@ -194,7 +194,7 @@ Specifically, IAM bundles log4j-api and log4j-to-slf4j. However, IAM does not bu

#### How to determine if the installation is affected

You are using IAM version <= 1.2.8
You are using IAM version ≤ 1.2.8

#### Solution

Expand All @@ -219,7 +219,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper

#### How to determine if the installation is affected

You are using Zeebe, Operate or Tasklist version <= 1.2.7 or <= 1.1.8
You are using Zeebe, Operate or Tasklist version ≤ 1.2.7 or ≤ 1.1.8

#### Solution

Expand Down Expand Up @@ -248,7 +248,7 @@ At this point, Camunda is not aware of any specific attack vector in IAM allowin

#### How to determine if the installation is affected

You are using IAM version <= 1.2.7
You are using IAM version ≤ 1.2.7

#### Solution

Expand All @@ -273,7 +273,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper

#### How to determine if the installation is affected

You are using Zeebe, Operate or Tasklist version <= 1.2.6 or <= 1.1.7
You are using Zeebe, Operate or Tasklist version ≤ 1.2.6 or ≤ 1.1.7

#### Solution

Expand Down Expand Up @@ -302,7 +302,7 @@ At this point, Camunda is not aware of any specific attack vector in IAM allowin

#### How to determine if the installation is affected

You are using IAM version <= 1.2.6
You are using IAM version ≤ 1.2.6

#### Solution

Expand All @@ -327,7 +327,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper

#### How to determine if the installation is affected

You are using Zeebe, Operate or Tasklist version <= 1.2.5 or <= 1.1.6
You are using Zeebe, Operate or Tasklist version ≤ 1.2.5 or ≤ 1.1.6

#### Solution

Expand Down Expand Up @@ -357,7 +357,7 @@ Still, Camunda recommends applying fixes as mentioned in the Solution section be

#### How to determine if the installation is affected

You are using IAM version <= 1.2.5
You are using IAM version ≤ 1.2.5

#### Solution

Expand Down
2 changes: 1 addition & 1 deletion docs/self-managed/operate-deployment/importer-and-archiver.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ You can further parallelize archiver and/or importer within one node using the f
| camunda.operate.importer.threadsCount | Number of threads in which data will be imported. | 3 |

:::note
Parallelization of import and archiving within one node will also happen based on Zeebe partitions, meaning only configurations with (number of nodes) \* (threadsCount) <= (total number of Zeebe partitions) will make sense. Too many threads and nodes will still work, but some of them will be idle.
Parallelization of import and archiving within one node will also happen based on Zeebe partitions, meaning only configurations with (number of nodes) \* (threadsCount) ≤ (total number of Zeebe partitions) will make sense. Too many threads and nodes will still work, but some of them will be idle.
:::

## Archive period
Expand Down
2 changes: 1 addition & 1 deletion docs/self-managed/tasklist-deployment/importer-and-archiver.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ You can further parallelize archiver and/or importer within one node using the f
| camunda.tasklist.importer.threadsCount | Number of threads in which data will be imported. | 3 |

:::note
Parallelization of import and archiving within one node will also happen based on Zeebe partitions, meaning only configurations with (number of nodes) \* (threadsCount) <= (total number of Zeebe partitions) will make sense. Too many threads and nodes will still work, but some of them will be idle.
Parallelization of import and archiving within one node will also happen based on Zeebe partitions, meaning only configurations with (number of nodes) \* (threadsCount) ≤ (total number of Zeebe partitions) will make sense. Too many threads and nodes will still work, but some of them will be idle.
:::

## Archive period
Expand Down
Loading
Loading