docs: changelog 1.1.0

[yiiqii]

Summary by CodeRabbit

• New Features
  • Introduced dynamic video and gyroscope rotation support in scenes.
• Chores
  • Updated app version and dependencies in package.json.

[coderabbitai]

Walkthrough

This update brings a significant version bump in the project, enhancing both the package dependencies and the application's functionality. The package.json has been upgraded, including a major update to the @commitlint/cli dependency. Additionally, the application now supports dynamic video and gyroscope rotation features, as introduced in the new scene JSON format version '2.3'.

Changes

File	Change Summary
package.json	Updated from version 1.0.1 to 1.1.0, updated @commitlint/cli from ^13.2.1 to ^19.2.2
src/scene.ts	Added support for dynamic video and gyroscope rotation; introduced scene JSON format version '2.3'

Poem

🌟✨🐇✨🌟
In the code meadow, under the byte tree,
A version jumps; it's 1.1.0, glee!
Videos swirl and gyros spin,
New scenes unfold, let the magic begin!
Oh, how the digits dance and twirl,
In this ever-updating digital world!
🌟✨🐇✨🌟

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 367c5dd and 1b8b00b.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (1)

• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• package.json

---

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 your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

Tip

Codebase Verification

The version field in src/type.ts is defined simply as a string, which does not enforce the specific version values ('1.0', '1.1', '1.2', '1.3', '1.5', '1.8', '2.0', '2.1', '2.2', '2.3') defined in src/scene.ts. This could potentially lead to the assignment of incorrect or unintended version values in downstream code. It is recommended to review and possibly revise the type definition in src/type.ts to align with the version constraints specified in src/scene.ts to ensure consistent and correct usage across the codebase.

Analysis chain

Ensure the version field is used correctly in downstream code.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Search for usage of the 'version' field in the JSONScene interface to ensure it's handled correctly.
rg --type ts "version" src/

Length of output: 251

---

---

Script:

#!/bin/bash
# Examine the usage of the 'version' field in src/type.ts to ensure it aligns with the defined versions in src/scene.ts
rg --type ts "version" src/type.ts

Length of output: 53