-
Notifications
You must be signed in to change notification settings - Fork 8
DX | 11-02-2025 | Release #263
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
Conversation
* Added support for nested global fields (#230) * Added support for nested global fields * Added mock file * Fixed PR comments * Added released version and removed duplicate code * Update package-lock.json file * Commeneted nested global fields sanity testcases
Reverted variant types fix and Update node version to 22
DX | 11-02-2025 | Release
We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch. |
Coverage report for commit: fd9e549
Summary - Lines: 89.73% | Methods: 99.49% | Branches: 72.54%
🤖 comment via lucassabreu/comment-coverage-clover |
…ariant added sanity for entry variant
Back merge
We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch. |
…riants feat | dx 1889 api version variants
Development to staging (11-02-2025) Release
We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch. |
We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch. |
No description provided.