Repository navigation
chore: release 1.0.0 - #4
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--master
branch
from
October 9, 2026 17:19
4e01cd1 to
dea6b57
Compare
kvs-coder
added a commit
that referenced
this pull request
Oct 9, 2026
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.`
Contributor
Author
|
🤖 Created releases: 🌻 |
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.
🤖 I have created a release beep boop
1.0.0 (2026-10-09)
⚠ BREAKING CHANGES
Code Refactoring
This PR was generated with Release Please. See documentation.