Skip to content
This repository was archived by the owner on Aug 13, 2026. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions .github/workflows/release-please.yml
Original file line number Diff line number Diff line change
@@ -1,9 +1,16 @@
name: release-please

# No `push` trigger, deliberately (fleet git/PR-friction sweep, 2026-07-26):
# per-push release PRs self-merged all day and kept moving main's tip, which
# made every open PR go stale between fetch and merge. One daily cron cut
# (plus manual dispatch for urgent releases) keeps versioning identical —
# release-please accumulates the conventional commits since the last release.
# Reverting is one line: put `push: {branches: [main]}` back under `on:`.
# (Template repo: every repo created from this inherits the daily cadence.)
on:
push:
branches: [main]
workflow_dispatch:
schedule:
- cron: '17 6 * * *'
Comment on lines +12 to +13

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Provide recovery when inactivity disables the schedule

For public repositories with no activity for 60 days, GitHub automatically disables scheduled workflows, as documented in the schedule event documentation. Because this diff removes the only push trigger, later repository activity cannot run release-please, and workflow_dispatch remains unavailable until someone explicitly re-enables the disabled workflow; release PRs and tags can therefore silently stop after a dormant repository becomes active again. Provide a non-scheduled recovery mechanism or document and automate re-enablement.

AGENTS.md reference: AGENTS.md:L112-L112

Useful? React with 👍 / 👎.


permissions:
contents: write
Expand Down