Skip to content

ci: commit missing release-please-config.json - #58

Merged
petercorke merged 1 commit into
mainfrom
ci/add-release-please-config
Aug 3, 2026
Merged

ci: commit missing release-please-config.json#58
petercorke merged 1 commit into
mainfrom
ci/add-release-please-config

Conversation

@petercorke

@petercorke petercorke commented Aug 3, 2026

Copy link
Copy Markdown
Owner

Summary

  • `.github/workflows/release-please.yml` requires `release-please-config.json` (`config-file:` input), but it was never actually committed to the repo -- only ever present as an untracked local file. Confirmed the automated release pipeline has been silently non-functional the entire time: zero release-please bot PRs have ever run, despite 39 merged PRs (including real `feat:` commits) since the last tag, `v2.0.1`.
  • Already flagged as a sub-point in tech-debt issue Repo root is full of untracked scratch/junk files #45 ("worth checking before cleanup, not after") -- this addresses that specific sub-point (the rest of Repo root is full of untracked scratch/junk files #45, the untracked scratch/junk files, is unrelated and still open).
  • Content is unchanged from the untracked working-tree copy: `release-type: python`, `version-file: pyproject.toml`, `changelog-path: CHANGELOG.md`, matching the existing (already-tracked) `.release-please-manifest.json` (`"." : "2.0.1"`).
  • Merging this (a push to `main`) should itself trigger `release-please.yml` to run for the first time successfully, which should open its own auto-generated release PR for the next version.

Related to #45 (does not close it -- the untracked-scratch-files part of that issue is still open)

Test plan

  • Merge and confirm release-please's own workflow run succeeds and opens a release PR

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

.github/workflows/release-please.yml has required this file
(config-file: release-please-config.json) since the workflow was
added, but it was never actually committed -- only ever present as an
untracked local file. Confirmed via git history and the complete
absence of any release-please bot PR ever having run: the automated
release pipeline has been silently non-functional this whole time,
despite 39 merged PRs (including real feat: commits) since the last
tag, v2.0.1.

Content unchanged from the untracked working-tree copy -- release-type
python, version-file pyproject.toml, changelog-path CHANGELOG.md,
matching the existing .release-please-manifest.json ("." : "2.0.1").

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@petercorke
petercorke force-pushed the ci/add-release-please-config branch from 30b5b0d to 8a6e46b Compare August 3, 2026 11:43
@petercorke
petercorke merged commit 1b832a1 into main Aug 3, 2026
17 checks passed
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.

1 participant