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/12.0.0-rc to main #2818

Open
wants to merge 28 commits into
base: main
Choose a base branch
from

Conversation

otter-cascading[bot]
Copy link
Contributor

Cascading from release/12.0.0-rc to main


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

matthieu-crouzet and others added 28 commits January 30, 2025 11:24
Italy changed their light saving date time logic several time in the past.

As a result, the offset computation for lightsaving switch prior to 1980 are incorrect.

This result in invalid utils.Date which are serialized to the day before.

Setting utils.Date time to 12:00 avoids this error (12:00 being correctly computed as after the time change).

It also reduces the impact of an incorrect offset.
## Context 

Italy changed their daylight saving logic several time in the past (may
prior 1980, march following then).

As a result, the offset computation for lightsaving switch prior to 1980
are incorrect:

![image](https://github.com/user-attachments/assets/a95259e9-6273-4925-8389-ababc027a4e9)
Here, the timezone offset should be -60 prior to the timechange (2am).
A valid offset would be the following (working example with France
daylight saving switch in 1992):

![image](https://github.com/user-attachments/assets/191edcad-7320-45a8-866d-80f0ad5d7411)

This results in invalid utils.Date which are serialized to the day
before.

## Proposed change

Setting utils.Date time to 12:00 avoids this error (12:00 being
correctly computed as after the time change).
It also reduces the impact of an incorrect offset.

## Related issues

<!--
Please make sure to follow the [contribution
guidelines](https://github.com/amadeus-digital/Otter/blob/main/CONTRIBUTING.md)
-->

*- No issue associated -*

<!-- * 🐛 Fix #issue -->
<!-- * 🐛 Fix resolves #issue -->
<!-- * 🚀 Feature #issue -->
<!-- * 🚀 Feature resolves #issue -->
<!-- * :octocat: Pull Request #issue -->
…into HEAD

# Conflicts:
#	.github/workflows/publish.yml
#	.github/workflows/scorecards.yml
#	apps/showcase/package.json
#	package.json
#	packages/@o3r/testing/package.json
#	yarn.lock
<!--
{"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 2796
  git pull --ff origin release/11.0
  ```

  and update this Pull Request with

  ```shell
  gh pr push 2796
  ```
</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>
…into HEAD

# Conflicts:
#	.github/workflows/documentation.yml
#	.github/workflows/it-tests.yml
#	.github/workflows/publish.yml
#	.github/workflows/scorecards.yml
#	apps/showcase/package.json
#	packages/@o3r/testing/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 2800
  git pull --ff origin release/11.1
  ```

  and update this Pull Request with

  ```shell
  gh pr push 2800
  ```
</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>
…into HEAD

# Conflicts:
#	.github/workflows/documentation.yml
#	.github/workflows/it-tests.yml
#	.github/workflows/publish.yml
#	.github/workflows/scorecards.yml
#	apps/showcase/package.json
#	package.json
#	packages/@o3r/testing/package.json
#	yarn.lock
<!--
{"currentBranch":"release/11.1","targetBranch":"release/11.2","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/11.1 to release/11.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 2802
  git pull --ff origin release/11.2
  ```

  and update this Pull Request with

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

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

  ```shell
  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

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



---

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

# Conflicts:
#	.github/workflows/code-check.yml
#	.github/workflows/documentation.yml
#	.github/workflows/e2e-tests.yml
#	.github/workflows/it-tests.yml
#	.github/workflows/publish.yml
#	.github/workflows/scorecards.yml
#	apps/showcase/package.json
#	package.json
#	packages/@o3r/testing/package.json
#	yarn.lock
<!--
{"currentBranch":"release/11.2","targetBranch":"release/11.3","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/11.2 to release/11.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 2811
  git pull --ff origin release/11.3
  ```

  and update this Pull Request with

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

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

  ```shell
  git fetch origin
  git checkout origin/cascading/11.2.0-11.3.0
  git pull --ff origin release/11.3
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/11.2.0-11.3.0
  ```
</details>



---

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

# Conflicts:
#	.github/workflows/code-check.yml
#	.github/workflows/documentation.yml
#	.github/workflows/e2e-tests.yml
#	.github/workflows/it-tests.yml
#	.github/workflows/publish.yml
#	.github/workflows/scorecards.yml
#	apps/showcase/package.json
#	package.json
#	packages/@o3r/testing/package.json
#	yarn.lock
<!--
{"currentBranch":"release/11.3","targetBranch":"release/11.4","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/11.3 to release/11.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 2812
  git pull --ff origin release/11.4
  ```

  and update this Pull Request with

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

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

  ```shell
  git fetch origin
  git checkout origin/cascading/11.3.0-11.4.0
  git pull --ff origin release/11.4
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/11.3.0-11.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/11.4","targetBranch":"release/11.5","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/11.4 to release/11.5





---

: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 2813
  git pull --ff origin release/11.5
  ```

  and update this Pull Request with

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

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

  ```shell
  git fetch origin
  git checkout origin/cascading/11.4.0-11.5.0
  git pull --ff origin release/11.5
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/11.4.0-11.5.0
  ```
</details>



---

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

# Conflicts:
#	apps/showcase/package.json
#	package.json
#	packages/@ama-sdk/core/src/fwk/date.ts
#	packages/@o3r/testing/package.json
#	yarn.lock
<!--
{"currentBranch":"release/11.5","targetBranch":"release/11.6","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/11.5 to release/11.6





---

: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 2815
  git pull --ff origin release/11.6
  ```

  and update this Pull Request with

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

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

  ```shell
  git fetch origin
  git checkout origin/cascading/11.5.0-11.6.0
  git pull --ff origin release/11.6
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/11.5.0-11.6.0
  ```
</details>



---

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

# Conflicts:
#	.github/workflows/it-tests.yml
#	apps/showcase/package.json
#	packages/@o3r/testing/package.json
#	yarn.lock
…ovided when adding @o3r/core (#2769)

## Related issues

* 🐛 Fix resolves #2758
## Proposed change

<!--
Please include a summary of the changes and the related issue.
Please also include relevant motivation and context.
-->

## Related issues

<!--
Please make sure to follow the [contribution
guidelines](https://github.com/amadeus-digital/Otter/blob/main/CONTRIBUTING.md)
-->

<!-- * 🐛 Fix #issue -->
* 🐛 Fix resolves #2730
<!-- * 🚀 Feature #issue -->
<!-- * 🚀 Feature resolves #issue -->
<!-- * :octocat: Pull Request #issue -->
<!--
{"currentBranch":"release/11.6","targetBranch":"release/12.0.0-rc","bypassReviewers":false,"isConflicting":false}
-->

## Cascading from release/11.6 to release/12.0.0-rc





---

: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 2816
  git pull --ff origin release/12.0.0-rc
  ```

  and update this Pull Request with

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

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

  ```shell
  git fetch origin
  git checkout origin/cascading/11.6.0-12.0.0-rc
  git pull --ff origin release/12.0.0-rc
  ```

  and update this Pull Request with

  ```shell
  git push origin HEAD:cascading/11.6.0-12.0.0-rc
  ```
</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 February 7, 2025 17:37
@otter-cascading otter-cascading bot added the cascading Cascading from previous release label Feb 7, 2025
Copy link

nx-cloud bot commented Feb 7, 2025

View your CI Pipeline Execution ↗ for commit aea5979.

Command Status Duration Result
nx run-many --target=test-int ✅ Succeeded 1h 4m 27s View ↗
nx run-many --target=test-e2e ✅ Succeeded 9m 30s View ↗
nx run-many --target=build --projects=eslint-pl... ✅ Succeeded 2s View ↗
nx run-many --target=publish --nx-bail --userco... ✅ Succeeded 35s View ↗
nx run-many --target=prepare-publish --exclude-... ✅ Succeeded 1m 17s View ↗
nx run-many --target=build,build-swagger ✅ Succeeded 13m 44s View ↗
nx affected --target=test --collectCoverage ✅ Succeeded 2m 20s View ↗
nx run-many --target=documentation ✅ Succeeded 1m 17s View ↗
Additional runs (3) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2025-02-07 19:10:06 UTC

Copy link

codecov bot commented Feb 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.21%. Comparing base (a04eb06) to head (aea5979).
Report is 33 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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