Release a snapshot to local maven repository

[tuan-jason]

Release a snapshot to local maven repository.

Summary by CodeRabbit

• Chores
  • Adjusted the release build settings so that production builds are no longer digitally signed.
  • Updated the distribution workflow to deliver release builds via local channels.

[tuan-jason]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Walkthrough

The changes update two configuration files. In gradle.properties, the property RELEASE_SIGNING_ENABLED has been set from true to false, effectively disabling release signing. In gradle/gradle-mvn-push.gradle, the remote repository publishing configuration has been commented out and replaced by a static declaration of mavenLocal(), thereby shifting the publishing process to use the local Maven repository.

Changes

File(s)	Change Summary
gradle.properties	Updated RELEASE_SIGNING_ENABLED from true to false to disable signing for release builds.
gradle/gradle-mvn-push.gradle	Commented out the dynamic remote maven repository configuration and added mavenLocal() to direct publishing to the local Maven repository.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant Gradle as Gradle Build
    participant Local as Maven Local Repository
    Dev->>Gradle: Trigger artifact publishing
    Note right of Gradle: Previously used remote/snapshot conditionals
    Gradle->>Local: Publish artifact using mavenLocal()

Loading

Poem

In the burrow of code I hop with glee,
No more signing chains—I’m now wild and free.
Remote paths dream as local hops in rhyme,
My bunny heart sings with each build time.
Hop on, dear coder, to a new step in our spree!
🐰✨

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

gradle/gradle-mvn-push.gradle (1)

85-97: Transition to Local Maven Repository Publishing

The remote repository configuration has been completely commented out, and the publishing block now directly uses mavenLocal(). This change meets the PR requirement to release snapshots locally.
Consider cleaning up the commented-out remote publishing code if it will no longer be used in the future, to keep the build script concise and maintainable.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 04bd414 and 02e0ed2.

📒 Files selected for processing (2)

• gradle.properties (1 hunks)
• gradle/gradle-mvn-push.gradle (1 hunks)

🔇 Additional comments (1)

gradle.properties (1)

56-56: Disable Release Signing for Local Publishing

The property RELEASE_SIGNING_ENABLED has been updated from true to false, which aligns with the PR objective of releasing snapshots to the local Maven repository without signing. Ensure that this change is consistent with your build and release processes, and that any tasks expecting signed artifacts are updated accordingly.