docs: changelog 1.1.0

[yiiqii]

Summary by CodeRabbit

• New Features

  • Support for direct parsing and playback of pre-compositions.
  • Unified math library for improved performance.

• Bug Fixes

  • Resolved issues with pre-composition rendering.
  • Fixed errors related to visibility, transformation, hit testing, dragging, and ID/transform configurations.

• Chores

  • Implemented automated bot review for enhanced code quality checks.

• Tests

  • Addressed and corrected plugin unit test and general testing issues.

• Build

  • Integrated CHANGELOG generation script.
  • Added legacy browser support with vite polyfill.

[coderabbitai]

Walkthrough

Version 1.1.0 brings exciting new features like direct parsing and playback of pre-compositions, alongside a unified math library. It also addresses various bug fixes related to pre-composition, hitTest, dragging, and more. The update includes process improvements such as automated bot review for specific branches, a fix for plugin unit tests, and the addition of a CHANGELOG generation script and legacy polyfill support.

Changes

File Path	Change Summary
CHANGELOG.md	Added details for version 1.1.0, including new features, bug fixes, chores, tests, and build updates.
scripts/.../utils.js	Updated the printPR function to use a standard period in the console log statement.

Poem

🐇✨
In the burrow of code, a new update hops,
Bugs squashed, features grow, and progress never stops.
With each leap and bound, the code does refine,
A rabbit's touch, in binary, forever will shine. 🌟
🐇💻

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 6631f66 and ffac305.

Files ignored due to filter (10)

• packages/effects-core/package.json
• packages/effects-helper/package.json
• packages/effects-threejs/package.json
• packages/effects-webgl/package.json
• packages/effects/package.json
• plugin-packages/alipay-downgrade/package.json
• plugin-packages/editor-gizmo/package.json
• plugin-packages/model/package.json
• plugin-packages/orientation-transformer/package.json
• plugin-packages/spine/package.json

Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• scripts/print-changelog/utils.js (1 hunks)

Files skipped from review due to trivial changes (1)

• scripts/print-changelog/utils.js

Additional comments: 1

CHANGELOG.md (1)

• 10-24: The changelog update for version 1.1.0 is well-structured, with clear categorization of changes and proper referencing to pull requests and commits. The inclusion of the release date provides a good historical context. This is a good practice for maintaining clear and traceable project documentation.