Repository navigation
release: restore automatic publishing by configuring RELEASE_PLEASE_TOKEN #112
Description
Problem
.github/workflows/release.yml reports success on every push to main, but Release Please is skipped because RELEASE_PLEASE_TOKEN is empty. Run 30298842935 recorded:
RELEASE_PLEASE_TOKEN is not configured. Skipping release-please
As a result, v2.1.0 exists as a tag without a published GitHub Release, and the latest published release remains v2.0.0.
Expected fix
Configure a repository-scoped token with the permissions needed by Release Please, verify the workflow opens or updates its release PR, and confirm the next release creates both the tag and GitHub Release.
Activity
linear-code commentedon Jul 27, 2026
AOJ-1071
AojdevStudio commentedon Sep 2, 2026
RELEASE_PLEASE_TOKEN is now set as a repository Actions secret (fine-grained PAT, contents + pull requests + issues). The Release workflow run on a2e269b ran release-please for the first time and opened #164 (chore(main): release family-office 2.3.0). Merging #164 is the remaining step: it should create the v2.3.0 tag and the GitHub Release, at which point this issue closes. Two harmless warnings appear in the run: older non-conventional merge commits could not be parsed for the changelog, and an existing release tag has no manifest component.
ci(release): match release-please tags to the repo's vX.Y.Z tag format (
AojdevStudio commentedon Sep 2, 2026
Resolved. RELEASE_PLEASE_TOKEN is set, #165 aligned the tag format with the repo's vX.Y.Z tags, and merging #164 created tag v2.3.0 and the published GitHub Release https://github.com/AojdevStudio/Finance-Guru/releases/tag/v2.3.0 in the same workflow run (release-please and the deploy-notes job both succeeded).