8000 chore: release next by morellodev · Pull Request #317 · awesome-reveal/awesome-reveal · GitHub
[go: up one dir, main page]

Skip to content

chore: release next - #317

Merged
morellodev merged 1 commit into
nextfrom
release-please--branches--next
Oct 15, 2026
Merged

morellodev merged 1 commit into
nextfrom
release-please--branches--next

Conversation

@morellodev
Copy link
Copy Markdown
Collaborator

🤖 I have created a release beep boop

react-awesome-reveal: 5.0.0-next.10

5.0.0-next.10 (2026-10-15)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @awesome-reveal/react bumped to 1.0.0-next.10
@awesome-reveal/astro: 1.0.0-next.10

1.0.0-next.10 (2026-10-15)

⚠ BREAKING CHANGES

  • the generated entrance replaces the element's own values of the properties that the start state sets (translate, scale, rotate, filter, opacity) while the element waits and during the entrance, and ends at their neutral values, so a fade now ends at opacity 1. The element's own transform still applies. To keep one of these values during the entrance, put it on an inner element or use native keyframes.

Performance Improvements

  • run the generated entrance on the compositor (#316) (2264119)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @awesome-reveal/core bumped to 1.0.0-next.10
@awesome-reveal/core: 1.0.0-next.10

1.0.0-next.10 (2026-10-15)

⚠ BREAKING CHANGES

  • the generated entrance replaces the element's own values of the properties that the start state sets (translate, scale, rotate, filter, opacity) while the element waits and during the entrance, and ends at their neutral values, so a fade now ends at opacity 1. The element's own transform still applies. To keep one of these values during the entrance, put it on an inner element or use native keyframes.

Performance Improvements

  • run the generated entrance on the compositor (#316) (2264119)
@awesome-reveal/react: 1.0.0-next.10

1.0.0-next.10 (2026-10-15)

⚠ BREAKING CHANGES

  • the generated entrance replaces the element's own values of the properties that the start state sets (translate, scale, rotate, filter, opacity) while the element waits and during the entrance, and ends at their neutral values, so a fade now ends at opacity 1. The element's own transform still applies. To keep one of these values during the entrance, put it on an inner element or use native keyframes.

Performance Improvements

  • run the generated entrance on the compositor (#316) (2264119)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @awesome-reveal/core bumped to 1.0.0-next.10
@awesome-reveal/vue: 1.0.0-next.10

1.0.0-next.10 (2026-10-15)

⚠ BREAKING CHANGES

  • the generated entrance replaces the element's own values of the properties that the start state sets (translate, scale, rotate, filter, opacity) while the element waits and during the entrance, and ends at their neutral values, so a fade now ends at opacity 1. The element's own transform still applies. To keep one of these values during the entrance, put it on an inner element or use native keyframes.

Performance Improvements

  • run the generated entrance on the compositor (#316) (2264119)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @awesome-reveal/core bumped to 1.0.0-next.10

This PR was generated with Release Please. See documentation.

@morellodev
morellodev merged commit e3d5c92 into next Oct 15, 2026
18 checks passed
@morellodev
morellodev deleted the release-please--branches--next branch October 15, 2026 11:30
@morellodev
Copy link
Copy Markdown
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0