Repository navigation
ci(release): publish on JitPack and format release-please changelog headers - #5
Merged
Merged
Conversation
release-please writes changelog headers as `## [X.Y.Z](compare-url) (yyyy-MM-dd)`, but the CI "Version / Changelog" check expects `## [X.Y.Z] - dd.MM.yyyy.`, so merging release PR #4 as is would fail CI on master. Like HealthKitReporter, the release workflow now rewrites the header on the release PR branch with a `chore: format changelog` commit. Changes: - .github/workflows/release.yml: check out the release PR branch and rewrite CHANGELOG.md headers to the project format; use RELEASE_PLEASE_TOKEN when set so CI runs on release PRs Tests: release.yml parses; the sed expression turns `## [1.0.0](0.0.6...1.0.0) (2026-10-09)` into `## [1.0.0] - 09.10.2026.`
…eaders Automates the JitPack release and makes release-please's changelog pass CI. When the release PR is merged, release-please tags `X.Y.Z` and the release workflow dispatches the new `publish.yml` on that tag, which builds the version on JitPack and fails if JitPack can't build it or doesn't serve the AAR. release-please's changelog headers (`## [X.Y.Z](compare-url) (yyyy-MM-dd)`, `### ⚠ BREAKING CHANGES`) are rewritten on the release PR to the format CI checks (`## [X.Y.Z] - dd.MM.yyyy.`), as in HealthKitReporter and health_kit_reporter. Changes: - .github/workflows/release.yml: format changelog headers on the release PR; dispatch publish.yml on the new tag; use RELEASE_PLEASE_TOKEN when set so CI runs on release PRs - .github/workflows/publish.yml: build the tag on JitPack, poll its build log, verify POM and AAR - README.md, AGENTS.md, docs/arc42/07-deployment-view.md: release flow Tests: both workflows parse; the sed expressions turn `## [1.0.0](0.0.6...1.0.0) (2026-10-09)` into `## [1.0.0] - 09.10.2026.` and `### ⚠ BREAKING CHANGES` into `### BREAKING CHANGES`; JitPack built commit 18b2246 of this repository successfully with the same jitpack.yml.
kvs-coder
changed the title
kvs-coder
added a commit
that referenced
this pull request
Oct 9, 2026
Release PR #4 was merged before the release workflow learned to format release-please's changelog headers (#5), so master's 1.0.0 entry kept release-please's format and CI's changelog check fails on master. This applies the same rewrite the release workflow now does on release PRs. Changes: - CHANGELOG.md: `## [1.0.0](compare-url) (2026-10-09)` → `## [1.0.0] - 09.10.2026.`, `### ⚠ BREAKING CHANGES` → `### BREAKING CHANGES` Tests: the CI release-guard check passes locally against .release-please-manifest.json (1.0.0).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automates the JitPack release and makes release-please's changelog pass CI. When the release PR is merged, release-please tags
X.Y.Zand the release workflow dispatches the newpublish.ymlon that tag, which builds the version on JitPack and fails if JitPack can't build it or doesn't serve the AAR. release-please's changelog headers (## [X.Y.Z](compare-url) (yyyy-MM-dd),### ⚠ BREAKING CHANGES) are rewritten on the release PR to the format CI checks (## [X.Y.Z] - dd.MM.yyyy.), as in HealthKitReporter and health_kit_reporter.Changes:
Tests: both workflows parse; the sed expressions turn
## [1.0.0](https://github.com/kvs-coder/SamsungHealthReporter/compare/0.0.6...1.0.0) (2026-10-09)into## [1.0.0] - 09.10.2026.and### ⚠ BREAKING CHANGESinto### BREAKING CHANGES; JitPack built commit 18b2246 of this repository successfully with the same jitpack.yml.