Release/new#14
Merged
clalexander merged 6 commits intomainfrom May 4, 2026
Merged
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v5...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [amannn/action-semantic-pull-request](https://github.com/amannn/action-semantic-pull-request) from 6.1.0 to 6.1.1. - [Release notes](https://github.com/amannn/action-semantic-pull-request/releases) - [Changelog](https://github.com/amannn/action-semantic-pull-request/blob/main/CHANGELOG.md) - [Commits](amannn/action-semantic-pull-request@v6.1.0...v6.1.1) --- updated-dependencies: - dependency-name: amannn/action-semantic-pull-request dependency-version: 6.1.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
chore: sync main into dev
…actions/checkout-6 ci(deps): bump actions/checkout from 5 to 6
…amannn/action-semantic-pull-request-6.1.1 ci(deps): bump amannn/action-semantic-pull-request from 6.1.0 to 6.1.1
When a screen component causes CSS-in-JS (e.g. Emotion/MUI) to inject styles during the same React commit that starts a transition, the browser may resolve the `animation` property before the co-rendered `@keyframes` rule registers in the cascade. During that brief window, `animation-fill-mode: both` has no keyframe to reference, so the entering scene renders at its natural resting position instead of its off-screen start position. Fix by writing the `from` keyframe values (`transform`, `opacity`) as inline style fallbacks on the entering scene div. CSS animations sit above the inline style layer in the cascade, so the running animation always overrides them. The fallbacks are only visible during the single cascade pass before `@keyframes` registers — which is exactly when the displacement occurred. Co-authored-by: Copilot <copilot@github.com>
Contributor
|
🎉 This PR is included in version 0.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Describe the change clearly and concisely.
Why This Change
Explain the problem being solved or the reason for the change.
Type of Change
Branching
Please confirm this pull request follows the repository branching model.
Typical targets:
devfor feature, fix, refactor, docs, and most CI/tooling workmainonly for approved hotfixes or release-related mergesScope and Impact
What areas are affected?
Breaking Changes
If this is breaking, describe the change and required migration steps.
Testing
What did you do to validate this change?
npm run formatnpm run lintnpm run typechecknpm run testnpm run buildDescribe any additional manual or automated testing performed.
Documentation
Related Issues
Link any related issues, discussions, or follow-up work.
Closes #
Screenshots / Output
If applicable, add screenshots, logs, or code snippets that help reviewers.
Reviewer Notes
Anything in particular reviewers should focus on?
Any tradeoffs or known limitations?