ci: update release process#27
Conversation
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
|
Thank you for contributing to this project with this PR, welcome to the community and the amazing world of open source! |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughThis PR standardizes Conventional Commits patterns, expands release tooling and documentation for multi-target releases (Gradle, Rust, npm, Docker, native binaries, GHCR), updates publish workflows (native build matrix, release-assets job, cross-job outputs), and enhances version-sync and git-hook installation scripts. Changes
Sequence DiagramsequenceDiagram
actor User
participant GitHub as "GitHub Actions"
participant Publish as "publish job"
participant BuildNative as "build-native-binaries (matrix)"
participant ReleaseAssets as "release-assets job"
participant GHRelease as "GitHub Release API"
User->>GitHub: Push release tag
activate GitHub
GitHub->>Publish: Trigger publish job
activate Publish
Publish->>Publish: Validate versions (Gradle/Rust/npm)
Publish->>Publish: Publish ecosystem artifacts (Maven/crates.io/npm/Docker)
Publish-->>GitHub: Expose changelog output
deactivate Publish
par Native builds
GitHub->>BuildNative: Run matrix builds for targets
activate BuildNative
BuildNative->>BuildNative: Compile & package per target
BuildNative-->>GitHub: Upload per-target artifacts
deactivate BuildNative
end
GitHub->>ReleaseAssets: Trigger when needs satisfied
activate ReleaseAssets
ReleaseAssets->>ReleaseAssets: Download all artifacts
ReleaseAssets->>ReleaseAssets: Generate SHA256 checksums
ReleaseAssets->>GHRelease: Create release with changelog and assets
deactivate ReleaseAssets
deactivate GitHub
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Suggested labels
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
✅ Contributor ReportUser: @yacosta738
Contributor Report evaluates based on public GitHub activity. Analysis period: 2025-02-18 to 2026-02-18 |
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
1 similar comment
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
# Conflicts: # .github/CODEOWNERS
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
1 similar comment
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
|
It seems you edited the limitation files. These files aren't open for contributions. If you think they should be, feel free to reply here. |
This pull request introduces significant improvements to the release process, commit message enforcement, and documentation. The main changes expand the Conventional Commits specification for this repository, enhance release automation to support a multi-language/multi-platform project, and update documentation and validation scripts to match the new standards.
Conventional Commits and Commit Message Enforcement:
build,ci,release,style, andwip, updated regex patterns, and clarified documentation and PR templates to reflect these changes. This ensures more granular categorization and automation for commit messages and PR titles. [1] [2] [3] [4] [5] [6] [7] [8] [9]Release Process and Automation Enhancements:
release/SKILL.md) to cover multi-language (Gradle/KMP, Rust, npm, Docker) publishing, required secrets, and detailed versioning steps for all targets. [1] [2] [3] [4] [5] [6] [7] [8] [9]_publish.yml) to:Documentation and Skill Additions:
These changes collectively modernize and standardize the project's release and commit practices, making it easier to maintain, automate, and onboard contributors.
Summary by CodeRabbit
New Features
Documentation
Chores