Skip to content

chore: remove release-please self-management from org-defaults repo#37

Merged
brodkin merged 1 commit into
mainfrom
chore/remove-release-please-self
May 9, 2026
Merged

chore: remove release-please self-management from org-defaults repo#37
brodkin merged 1 commit into
mainfrom
chore/remove-release-please-self

Conversation

@brodkin

@brodkin brodkin commented May 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Remove the release-please-self machinery added in PR #35 (the DEV-225 smoke test) now that the smoke test has served its purpose.

Why

This repo isn't a versioned product. Consumers pin @v1 rolling, not specific point releases. Every PR merge would open a chore release PR — noise without consumer value. Dog-fooding release-please is better served by an actual product repo when SpiceLabs ships one.

The smoke test proved the Rosemary Releaser App auth chain works end-to-end (release PR authored by rosemary-releaser[bot], tag-push cascade fires under the App identity). Mission accomplished.

Removed

File Why
.github/workflows/release-please-self.yml Caller for self-release. Stops future auto-release proposals.
.github/workflows/release-cascade-check.yml Smoke-test-only workflow. Its own file header says "Safe to delete once the cascade is verified end-to-end." Verified.
release-please-config.json Self-release config.
.release-please-manifest.json Self-release manifest.
version.txt Self-release version file.
CHANGELOG.md One-entry changelog from the smoke test. Not consumer-facing.

Kept

Item Status
.github/workflows/release-please.yml Reusable workflow for other repos. DEV-222 deliverable.
.github/workflows/release-artifacts.yml Reusable workflow for other repos. DEV-223 deliverable.
v1.0.0 tag + GitHub Release Historical record of the smoke test. Permanent.
Rolling v1 tag At its current position (advanced manually post-smoke-test to point at v1.0.0's commit).

Test plan

  • Verify PR diff contains only deletions of the 6 listed files
  • After merge, verify release-please-self.yml does NOT fire on the merge commit (it's deleted; nothing to fire)
  • No auto-release PR opens after this lands

Refs: DEV-225 (closes once merged)

The DEV-225 smoke test served its purpose — proved the Rosemary Releaser
App auth chain works end-to-end (release PR authored by the App, tag
push fires downstream workflows under the App identity).

Going forward we don't want auto-releases on this repo:
- It's not a versioned product. Consumers pin @v1 rolling, not specific
  point releases like @v1.0.3 vs @v1.0.4.
- Every PR merge would open a release PR, doubling the merge ritual for
  what's effectively config maintenance.
- Dog-fooding release-please is better served by an actual product repo
  when SpiceLabs ships one. Org-defaults is an unusual first test bed.

Removed:
- .github/workflows/release-please-self.yml (caller)
- .github/workflows/release-cascade-check.yml (smoke-test only, "safe
  to delete once cascade verified" per its own header)
- release-please-config.json, .release-please-manifest.json,
  version.txt, CHANGELOG.md (all release-please-self artifacts)

Kept:
- .github/workflows/release-please.yml — REUSABLE workflow for other
  repos to call. This was DEV-222's deliverable.
- .github/workflows/release-artifacts.yml — REUSABLE workflow for
  SBOM/SLSA/cosign on consumer-repo tag pushes. DEV-223's deliverable.
- v1.0.0 tag + GitHub Release — historical record of the smoke test.
- Rolling v1 tag at its current position (advanced manually after
  smoke test).

Refs: DEV-225 (closes once merged)
@brodkin brodkin merged commit d1f59c0 into main May 9, 2026
1 check passed
@brodkin brodkin deleted the chore/remove-release-please-self branch May 9, 2026 02:55

@pepper-pr-review pepper-pr-review 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.

Verified against DEV-225 (Linear) — aligned. This PR removes the smoke-test machinery added in PR #35 after successful end-to-end verification of the Rosemary Releaser App auth chain. The six deleted files (five from PR #35 plus the generated CHANGELOG) are legitimate cleanup; the reusable workflows for DEV-222 and DEV-223 remain intact. No test coverage needed for infrastructure removal.

When you're ready for another review pass, just drop a note with @pepper review and I'll take a look!

@pepper-pr-review pepper-pr-review Bot added the pepper-approved Pepper approved this PR label May 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pepper-approved Pepper approved this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant