Skip to content

release(prepare): v1.7.1 - #3355

Merged
glihm merged 1 commit into
mainfrom
prepare-release
Sep 25, 2025
Merged

release(prepare): v1.7.1#3355
glihm merged 1 commit into
mainfrom
prepare-release

Conversation

@tarrencev

@tarrencev tarrencev commented Sep 25, 2025

Copy link
Copy Markdown
Contributor

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Chores
    • Bumped workspace and example package versions to 1.7.1 for a patch release.
    • Aligned internal dependencies to 1.7.1 for consistency across the project.
    • No changes to features, behavior, or public APIs.
    • Build and configuration metadata updated only; runtime behavior unaffected.
    • Ensures smoother publishing and compatibility within the workspace without impacting end-user functionality.

@coderabbitai

coderabbitai Bot commented Sep 25, 2025

Copy link
Copy Markdown
Contributor

ohayo, sensei!

Walkthrough

All changes bump package versions from 1.7.0 to 1.7.1 across Cargo.toml and Scarb.toml manifests, including an internal path dependency update (dojo-types) in the root Cargo.toml. No source code, logic, APIs, or configuration beyond version metadata were modified.

Changes

Cohort / File(s) Change Summary
Rust manifests (Cargo.toml)
Cargo.toml, crates/macros/merge-options/macro_test/Cargo.toml
Version bump 1.7.0 → 1.7.1; root also updates path dependency dojo-types 1.7.0 → 1.7.1.
Dojo Scarb manifests
crates/dojo/core/Scarb.toml, crates/dojo/core-tests/Scarb.toml, crates/dojo/dojo-cairo-test/Scarb.toml, crates/dojo/dojo-snf-test/Scarb.toml
Package version bump 1.7.0 → 1.7.1.
Examples Scarb manifests
examples/game-lib/Scarb.toml, examples/game-lib/armory/Scarb.toml, examples/game-lib/bestiary/Scarb.toml, examples/simple/Scarb.toml, examples/spawn-and-move/Scarb.toml, examples/spawn-and-move/external/Scarb.toml
Package version bump 1.7.0 → 1.7.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed Ohayo sensei, the pull request title follows the conventional commit pattern by specifying a release preparation for version 1.7.1 and directly relates to the only changes made, which are version bumps across project manifests, making it concise and clear to reviewers.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch prepare-release

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 44a4b93 and 694fba8.

⛔ Files ignored due to path filters (6)
  • Cargo.lock is excluded by !**/*.lock
  • crates/dojo/core-tests/Scarb.lock is excluded by !**/*.lock
  • crates/dojo/core/Scarb.lock is excluded by !**/*.lock
  • crates/dojo/macros/Cargo.lock is excluded by !**/*.lock
  • examples/simple/Scarb.lock is excluded by !**/*.lock
  • examples/spawn-and-move/Scarb.lock is excluded by !**/*.lock
📒 Files selected for processing (12)
  • Cargo.toml (2 hunks)
  • crates/dojo/core-tests/Scarb.toml (1 hunks)
  • crates/dojo/core/Scarb.toml (1 hunks)
  • crates/dojo/dojo-cairo-test/Scarb.toml (1 hunks)
  • crates/dojo/dojo-snf-test/Scarb.toml (1 hunks)
  • crates/macros/merge-options/macro_test/Cargo.toml (1 hunks)
  • examples/game-lib/Scarb.toml (1 hunks)
  • examples/game-lib/armory/Scarb.toml (1 hunks)
  • examples/game-lib/bestiary/Scarb.toml (1 hunks)
  • examples/simple/Scarb.toml (1 hunks)
  • examples/spawn-and-move/Scarb.toml (1 hunks)
  • examples/spawn-and-move/external/Scarb.toml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: clippy
🔇 Additional comments (12)
examples/spawn-and-move/external/Scarb.toml (1)

3-3: Version bump is consistent.

ohayo sensei, the 1.7.1 tag lines up with the release prep; all good here.

crates/dojo/core/Scarb.toml (1)

6-6: Core crate version update confirmed.

ohayo sensei, the core package and its macro dependency are synced to 1.7.1, matching the release cadence.

examples/game-lib/bestiary/Scarb.toml (1)

3-3: Bestiary manifest synced.

ohayo sensei, the bestiary crate now reflects 1.7.1 and stays aligned with the workspace.

examples/game-lib/armory/Scarb.toml (1)

3-3: Armory manifest aligned.

ohayo sensei, the version bump to 1.7.1 keeps this example crate in lockstep with the release.

examples/spawn-and-move/Scarb.toml (1)

4-4: Example package version verified.

ohayo sensei, the main spawn-and-move example now tracks 1.7.1 appropriately.

crates/macros/merge-options/macro_test/Cargo.toml (1)

3-3: Macro test crate bumped correctly.

ohayo sensei, the macro test harness reflects 1.7.1 without any stray changes.

crates/dojo/core-tests/Scarb.toml (1)

5-5: Core tests manifest updated.

ohayo sensei, the testing crate mirrors the 1.7.1 release version as expected.

crates/dojo/dojo-cairo-test/Scarb.toml (1)

5-5: Cairo test crate synchronized.

ohayo sensei, the cairo test package now points at 1.7.1, keeping the suite consistent.

crates/dojo/dojo-snf-test/Scarb.toml (1)

5-5: Version alignment looks solid.

ohayo sensei, the crate version bump to 1.7.1 keeps this test package aligned with the release cadence.

Cargo.toml (1)

43-67: Workspace metadata bump is consistent.

ohayo sensei, both the workspace version and the dojo-types dependency now point at 1.7.1, keeping internal consumers in lockstep for the patch release.

examples/simple/Scarb.toml (1)

4-4: Example manifest stays in sync.

ohayo sensei, the example project now reflects 1.7.1, matching the rest of the release train.

examples/game-lib/Scarb.toml (1)

8-8: Workspace version bump confirmed.

ohayo sensei, the example library workspace package version is updated to 1.7.1, so the release prep looks tidy here too.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@glihm
glihm merged commit dc5d22b into main Sep 25, 2025
18 of 19 checks passed
@glihm
glihm deleted the prepare-release branch September 25, 2025 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants