Skip to content

ci: integrate release-please and cut 0.19.1 - #337

Merged
itaihanski merged 3 commits into
mainfrom
chore/release-please
Jul 13, 2026
Merged

ci: integrate release-please and cut 0.19.1#337
itaihanski merged 3 commits into
mainfrom
chore/release-please

Conversation

@itaihanski

Copy link
Copy Markdown
Member

Description

  • Cut 0.19.1 manually — versions pushed by hand (.release-please-manifest.json, Sdk.kt VERSION, CHANGELOG.md); tag 0.19.1 created manually after merge to trigger publish.yml
  • Add release-please (templated from the Flutter and React Native SDKs) to automate subsequent releases; ships dormant and takes over from 0.19.1 on the next feat/fix
  • release-please-config.json: release-type: simple, include-v-in-tag: false to match existing non-v tags; Sdk.kt VERSION annotated with x-release-please-version for auto-bump
  • release-please.yml: runs on push to main, authenticates with a GitHub App token so the release it creates still triggers publish.yml
  • lint-pr.yml: enforce Conventional Commit PR titles
  • publish.yml unchanged — manual and automated releases converge on the same release: created trigger

@shuni-bot

shuni-bot Bot commented Jul 13, 2026

Copy link
Copy Markdown

🐕 Review complete — View session on Shuni Portal 🐾

@shuni-bot

shuni-bot Bot commented Jul 13, 2026

Copy link
Copy Markdown

🐕 Suggested Reviewers

The review assignment focuses on covering different areas affected by the release process, with one reviewer responsible for SDK code changes. Since the other files are related to CI workflows and release configuration, the primary reviewer for code content is shilgapira, ensuring thorough review of SDK-related updates.

Reviewer Reason
shilgapira Shilgapira has made commits in the SDK source code, specifically in 'Sdk.kt,' so they should review changes related to SDK modifications and validate that the implementation aligns with the intended functionality.

Suggested by Shuni based on git history and PR context. Names are not @-mentioned to avoid notifying anyone — request a review from whoever fits best.

@itaihanski
itaihanski requested a review from shilgapira July 13, 2026 13:12
Comment thread .github/workflows/release-please.yml Fixed

@shuni-bot shuni-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐕 Shuni's Review

Cuts 0.19.1 manually and wires up release-please + Conventional-Commit PR-title linting to automate future releases.

No issues found — good bones! The pull_request_target lint job doesn't check out PR code, the release job uses a GitHub App token (so no workflow permissions block needed), and the config/manifest/x-release-please-version annotation all line up. Woof!

Manual 0.19.1 release bundled with release-please setup. Versions pushed
by hand in this PR (manifest, Sdk.kt, CHANGELOG all set to 0.19.1); tag
0.19.1 is created manually after merge to trigger publish.yml.

release-please (templated from the Flutter and React Native SDKs) ships
dormant - it ignores this ci/chore commit and takes over from 0.19.1 on
the next feat/fix:
- release-please-config.json (release-type: simple, include-v-in-tag: false
  to match existing non-v tags) + .release-please-manifest.json
- release-please.yml workflow (GitHub App token so the release it creates
  still triggers publish.yml)
- lint-pr.yml to enforce Conventional Commit PR titles
- Sdk.kt VERSION annotated with x-release-please-version for auto-bump

publish.yml is unchanged - both manual and automated releases converge on
the same release:created trigger.
@itaihanski
itaihanski force-pushed the chore/release-please branch from ee01c8c to 47abf37 Compare July 13, 2026 13:25
@itaihanski
itaihanski merged commit 1dcbf54 into main Jul 13, 2026
9 of 10 checks passed
@itaihanski
itaihanski deleted the chore/release-please branch July 13, 2026 13:33
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.

3 participants