Skip to content

Reverse merge main (3.4.0) into staging #772

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

Merged
merged 20 commits into from
Jun 11, 2025
Merged

Reverse merge main (3.4.0) into staging #772

merged 20 commits into from
Jun 11, 2025

Conversation

prudrabhat
Copy link
Contributor

@prudrabhat prudrabhat commented Jun 11, 2025

Looks like an off tree merge from a fork during previous release has caused current staging, dev to be out of sync with main.
We reconciled dev and main. Do the same with staging so that we can propagate dev -> staging -> main linearly for current release.

yangyansong-adbe and others added 20 commits May 23, 2024 16:11
staging -> main (Core 3.0.1/ Lifecycle 3.0.1/ Identity 3.0.1)
staging -> main (Core 3.0.2)
Merge `staging` into `main` for Core v3.1.0
Merge `staging` into `main` for 3.1.1-core release
enabled to keep screen reader
[PLATIR-41103] Added dialog for correct screen reader case
Revert "[PLATIR-41103] Added dialog for correct screen reader case"
Merge `staging` into `main` for Core 3.1.2
staging -> main (core-v3.2.0)
staging -> main (Core 3.3.0) (Identity 3.0.2) (Lifecycle 3.0.2) (Signal 3.0.1)
* Update api-reference.md

* Update api-reference.md
Staging -> main (Core 3.3.1)
@prudrabhat prudrabhat merged commit 38ae671 into staging Jun 11, 2025
82 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants