feat: updates

[ponderingdemocritus]

• Updates

Summary by CodeRabbit

• New Features

  • Enhanced release process with a new step for creating GitHub releases.
  • Updated changelog generation method for better consistency.

• Bug Fixes

  • Adjusted CI workflow for improved repository access during the CI process.

• Documentation

  • Streamlined SDK documentation, now directing users to the official documentation for guidance.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications to GitHub Actions workflow files, specifically .github/workflows/ci.yaml and .github/workflows/release.yaml, as well as significant content reduction in packages/sdk/readme.md. The CI workflow has removed the ssh-key specification for repository access, while the release workflow has updated steps for tagging, changelog generation, and added a new GitHub release creation step. The readme file has been streamlined, removing extensive SDK usage details and leaving only a reference to official documentation.

Changes

File	Change Summary
.github/workflows/ci.yaml	Removed with block for ssh-key in actions/checkout@v4; commented-out Codecov section retained.
.github/workflows/release.yaml	Added id: tag_publish to Tag and Publish Packages; renamed Generate Changelog to Generate Changelog with standard-version; added Create GitHub Release step with relevant parameters.
packages/sdk/readme.md	Removed detailed sections on SDK features, usage, examples, and truncated the "Table of Contents"; only a brief reference to official documentation remains.

Possibly related PRs

• fix: entity sync #252: Modifies the .github/workflows/ci.yaml file by updating the version of the dojoup command, relevant to the CI workflow changes.
• feat: Torii upgrade #303: Similar to fix: entity sync #252, this PR also updates the version of the dojoup command in the .github/workflows/ci.yaml file.

Poem

🐰 In the garden of code, changes bloom,
CI flows smoother, dispelling the gloom.
Releases now sparkle with tags that gleam,
While the readme whispers, "Follow the dream."
A hop and a skip, through updates we race,
In the world of our code, we find our place! 🌼

---

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.

CodeRabbit Configuration 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.