chore(web): update package version to 1.0.0-beta.1.0

[airslice]

Overview

Update package version to 1.0.0-beta.1.0

What I've done

What I haven't done

How I tested

Which point I want you to review particularly

Memo

Summary by CodeRabbit

• New Features
  • Transitioned the project version from alpha to beta, indicating readiness for broader testing.
• Chores
  • Maintained existing structure of scripts and dependencies without changes.

[coderabbitai]

Walkthrough

The pull request updates the package.json file for the @reearth/visualizer project, changing the version from 1.0.0-alpha.8 to 1.0.0-beta.1.0. This indicates a transition from an alpha to a beta release. The structure of scripts, dependencies, and devDependencies remains unchanged, and the engines field continues to require Node.js version >=20.11.0. The lint-staged configuration for linting file types using ESLint is also preserved.

Changes

File	Change Summary
web/package.json	Updated version from 1.0.0-alpha.8 to 1.0.0-beta.1.0.

Possibly related PRs

• chore(web): Update package version #1166: This PR updates the package.json version from 1.0.0-alpha.5 to 1.0.0-alpha.6, which is related to the versioning changes in the main PR.
• chore(web): update package version to 1.0.0-alpha.8 #1218: This PR updates the package.json version from 1.0.0-alpha.7 to 1.0.0-alpha.8, which is also related to the versioning changes in the main PR.
• feat(web): update @reearth/core #1145: This PR updates the version of the @reearth/core package in the package.json, indicating a version change that is relevant to the overall package management context of the main PR.
• chore(web): update core version #1281: This PR updates the @reearth/core dependency version in the package.json, which is relevant to the versioning aspect discussed in the main PR.

Suggested reviewers

• mkumbobeaty
• pyshx

Poem

In the meadow, we hop and play,
A new version brightens the day.
From alpha to beta, we cheer with glee,
As the project grows, just wait and see!
With every change, we dance and prance,
In the world of code, we take our chance! 🐇✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 12fa64f and 03981cc.

📒 Files selected for processing (1)

• web/package.json (1 hunks)

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

• web/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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[netlify]

✅ Deploy Preview for reearth-web ready!

Name	Link
🔨 Latest commit	03981cc
🔍 Latest deploy log	https://app.netlify.com/sites/reearth-web/deploys/67497b2264b06200087f2d6e
😎 Deploy Preview	https://deploy-preview-1287--reearth-web.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.