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.

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

[cascading] from release/11.1 to release/11.2 #2306

Open
wants to merge 16 commits into
base: release/11.2
Choose a base branch
from

Conversation

otter-cascading[bot]
Copy link
Contributor

@otter-cascading otter-cascading bot commented Oct 18, 2024

Cascading from release/11.1 to release/11.2


❗ The pull request is conflicting with the target branch.
You can fix the issue locally with the following commands:

Using gh CLI
gh pr checkout 2306
git pull --ff origin release/11.2

and update this Pull Request with

gh pr push 2306
Using git only
git fetch origin
git checkout origin/cascading/11.1.0-11.2.0
git pull --ff origin release/11.2

and update this Pull Request with

git push origin HEAD:cascading/11.1.0-11.2.0

This Pull Request has been generated with ❤️ by the Otter cascading tool.

cpaulve-1A and others added 15 commits October 8, 2024 11:08
Operators have exposed and supported type.

The first type is what to extract for the CMS and the second at runtime

Left operand runtime type was overriding right operand metadata
## Proposed change
Operators have exposed and supported type.
The first type is what to extract for the CMS and the second is to be
used for type check in the code.
Left operand runtime type was overriding right operand metadata (idx =
2, hence > 1).
Now, only extract "ExposedTypes"

## Related issues

- 🐛 Fixes #(issue)
- 🚀 Feature #(issue)

<!-- Please make sure to follow the contributing guidelines on
https://github.com/amadeus-digital/Otter/blob/main/CONTRIBUTING.md -->
## Proposed change

<!-- Please include a summary of the changes and the related issue.
Please also include relevant motivation and context. List any
dependencies that is required for this change. -->

## Related issues

- 🐛 Fixes #(issue)
- 🚀 Feature #(issue)

<!-- Please make sure to follow the contributing guidelines on
https://github.com/amadeus-digital/Otter/blob/main/CONTRIBUTING.md -->
<!--
{"currentBranch":"release/9.6","targetBranch":"release/10.2","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/9.6 to release/10.2





---

:heavy_exclamation_mark: The pull request is conflicting with the target
branch.
You can fix the issue locally with the following commands:

<details open>
  <summary>Using <b>gh CLI</b></summary>

  ```shell
  gh pr checkout 2289
  git pull --ff origin release/10.2
  ```

  and update this Pull Request with

  ```shell
  gh pr push 2289
  ```
</details>

<details>
  <summary>Using <b>git</b> only</summary>

  ```shell
  git fetch origin
  git checkout origin/cascading/9.6.0-10.2.0
  git pull --ff origin release/10.2
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/9.6.0-10.2.0
  ```
</details>



---

<small>This Pull Request has been generated with :heart: by the
[Otter](https://github.com/AmadeusITGroup/otter) cascading tool.</small>
<!--
{"currentBranch":"release/10.2","targetBranch":"release/10.3","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/10.2 to release/10.3





---

:heavy_exclamation_mark: The pull request is conflicting with the target
branch.
You can fix the issue locally with the following commands:

<details open>
  <summary>Using <b>gh CLI</b></summary>

  ```shell
  gh pr checkout 2293
  git pull --ff origin release/10.3
  ```

  and update this Pull Request with

  ```shell
  gh pr push 2293
  ```
</details>

<details>
  <summary>Using <b>git</b> only</summary>

  ```shell
  git fetch origin
  git checkout origin/cascading/10.2.0-10.3.0
  git pull --ff origin release/10.3
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/10.2.0-10.3.0
  ```
</details>



---

<small>This Pull Request has been generated with :heart: by the
[Otter](https://github.com/AmadeusITGroup/otter) cascading tool.</small>
<!--
{"currentBranch":"release/10.3","targetBranch":"release/10.4","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/10.3 to release/10.4





---

:heavy_exclamation_mark: The pull request is conflicting with the target
branch.
You can fix the issue locally with the following commands:

<details open>
  <summary>Using <b>gh CLI</b></summary>

  ```shell
  gh pr checkout 2294
  git pull --ff origin release/10.4
  ```

  and update this Pull Request with

  ```shell
  gh pr push 2294
  ```
</details>

<details>
  <summary>Using <b>git</b> only</summary>

  ```shell
  git fetch origin
  git checkout origin/cascading/10.3.0-10.4.0
  git pull --ff origin release/10.4
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/10.3.0-10.4.0
  ```
</details>



---

<small>This Pull Request has been generated with :heart: by the
[Otter](https://github.com/AmadeusITGroup/otter) cascading tool.</small>
<!--
{"currentBranch":"release/10.4","targetBranch":"release/11.0","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/10.4 to release/11.0





---

:heavy_exclamation_mark: The pull request is conflicting with the target
branch.
You can fix the issue locally with the following commands:

<details open>
  <summary>Using <b>gh CLI</b></summary>

  ```shell
  gh pr checkout 2300
  git pull --ff origin release/11.0
  ```

  and update this Pull Request with

  ```shell
  gh pr push 2300
  ```
</details>

<details>
  <summary>Using <b>git</b> only</summary>

  ```shell
  git fetch origin
  git checkout origin/cascading/10.4.0-11.0.0
  git pull --ff origin release/11.0
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/10.4.0-11.0.0
  ```
</details>



---

<small>This Pull Request has been generated with :heart: by the
[Otter](https://github.com/AmadeusITGroup/otter) cascading tool.</small>
…0.0-11.1.0

 Conflicts:
	packages/@o3r/components/package.json
	packages/@o3r/rules-engine/package.json
	yarn.lock
<!--
{"currentBranch":"release/11.0","targetBranch":"release/11.1","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/11.0 to release/11.1





---

:heavy_exclamation_mark: The pull request is conflicting with the target
branch.
You can fix the issue locally with the following commands:

<details open>
  <summary>Using <b>gh CLI</b></summary>

  ```shell
  gh pr checkout 2303
  git pull --ff origin release/11.1
  ```

  and update this Pull Request with

  ```shell
  gh pr push 2303
  ```
</details>

<details>
  <summary>Using <b>git</b> only</summary>

  ```shell
  git fetch origin
  git checkout origin/cascading/11.0.0-11.1.0
  git pull --ff origin release/11.1
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/11.0.0-11.1.0
  ```
</details>



---

<small>This Pull Request has been generated with :heart: by the
[Otter](https://github.com/AmadeusITGroup/otter) cascading tool.</small>
@otter-cascading otter-cascading bot requested a review from a team as a code owner October 18, 2024 14:21
@otter-cascading otter-cascading bot added the cascading Cascading from previous release label Oct 18, 2024
Copy link

nx-cloud bot commented Oct 18, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 79c9c27. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cascading Cascading from previous release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants