Skip to content

chore: release main - #135

Merged
blafourcade merged 1 commit into
mainfrom
release-please--branches--main
May 22, 2026
Merged

blafourcade merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented May 20, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

4.1.0

4.1.0 (2026-05-21)

Features

Bug Fixes

  • aidd-orchestrator: correct broken link to 02-ask-config action (#142) (256c4f4)
  • aidd-orchestrator: write to-review as a label, not a command (#143) (971fd9d)

Miscellaneous

  • ci: drop aidd-cli from release, ship clean marketplace + plugin zips (59e4e8d)
  • ci: stop using aidd-cli for release assets, ship a clean marketplace bundle (9ecbf68)
  • release-please: drop per-plugin release-as pins after the v4.0.0 cut (48d283e)
  • release-please: drop per-plugin release-as pins after v4.0.0 (ae5d16d)
  • repoint auto-add workflow to AIDD Roadmap project (#8) (#150) (b7f4e8a)

Documentation

  • fix coherence defects in README, docs, and plugin READMEs (7bb04ac)
  • fix coherence defects in README, docs, and plugin READMEs (afcbca3)
aidd-dev: 1.0.1

1.0.1 (2026-05-21)

Documentation

  • fix coherence defects in README, docs, and plugin READMEs (7bb04ac)
  • fix coherence defects in README, docs, and plugin READMEs (afcbca3)
aidd-orchestrator: 1.0.1

1.0.1 (2026-05-21)

Bug Fixes

  • aidd-orchestrator: correct broken link to 02-ask-config action (#142) (256c4f4)
  • aidd-orchestrator: write to-review as a label, not a command (#143) (971fd9d)
aidd-refine: 1.1.0

1.1.0 (2026-05-21)

Features

Documentation

  • fix coherence defects in README, docs, and plugin READMEs (7bb04ac)
  • fix coherence defects in README, docs, and plugin READMEs (afcbca3)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 3 times, most recently from 05b9f17 to 4a6fb76 Compare May 20, 2026 09:01
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 4a6fb76 to 9971a1e Compare May 21, 2026 19:43
@blafourcade
blafourcade merged commit 1919c7c into main May 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

blafourcade added a commit that referenced this pull request Sep 24, 2026
* ci(release): accept only merge commits on main

A squashed promote collapses the week's commits into one hidden `ci:`
subject, so release-please reports no user-facing commits and the
entries vanish from the notes; it also collapses authorship onto whoever
merged. A rebase breaks the merge base the back-merge relies on.

The ruleset file now allows only merge commits on main. A bypass in
pull_request mode does not lift that restriction (proven in a sandbox),
so the Release PR moves from --squash --admin to --merge --admin, which
this repository already released from once (#135). The live ruleset is
left unchanged: it must be applied only after one release has merged
with --merge.

Refs #911

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
AIDD-Session-Id: 3adb1fb2-3894-4e52-afab-424803c7fcad

* feat(release): credit each release line's commit author

Generated GitHub releases never named the people behind a change.
release-please's own include-commit-authors option is a no-op in every
17.x release so far: parseConventionalCommits drops the author before
the changelog notes see it (googleapis/release-please#2761, fix pending
in #2892).

After release-please creates the cycle's releases, a CI step appends
each line's commit author as (@login), or the name when no account
resolves, resolved from the line's commit SHA. Lines already credited
are left alone, so a re-run changes nothing, and a crediting failure
never blocks the build and publish jobs. Delete the step once a fixed
release-please is pinned.

Refs #911

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
AIDD-Session-Id: 3adb1fb2-3894-4e52-afab-424803c7fcad

* docs(release): state the merge-only rule as declared, not live

The live main ruleset still allows squash and rebase until a maintainer
applies .github/rulesets/main.json, which must wait for one release to
merge with --merge. The docs now describe the rule the file declares
instead of claiming it is enforced today.

Refs #911

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
AIDD-Session-Id: 3adb1fb2-3894-4e52-afab-424803c7fcad

* fix(release): make release crediting fail loudly and never block publishing

A missing RELEASE_OUTPUTS made the script credit nothing and exit 0, and
a failing checkout before the credit step would fail the release-please
job and skip every build and publish job. The script now exits non-zero
on missing outputs, both crediting steps carry continue-on-error, and
tests pin the wiring. A second pass no longer re-appends an author name
containing parentheses, and a release is written back only when its
body changed.

Refs #911

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
AIDD-Session-Id: 3adb1fb2-3894-4e52-afab-424803c7fcad

* fix(release): merge into main with an empty commit body

The repository fills a merge commit's body with the PR title, and
release-please splits a message on each conventional line, so a PR
merged into main as a merge commit is parsed twice: the change appears
twice in the notes, the copy credited to whoever merged. No repository
setting yields an empty body with the "Merge pull request" subject.

The Release PR and promote merges now pass --body "", and hotfixes are
documented to merge with an empty description. Proven in a sandbox: a
default-body merge duplicated the line, an empty-body merge did not.

Refs #911

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
AIDD-Session-Id: 3adb1fb2-3894-4e52-afab-424803c7fcad

* fix(release): drop merge-commit duplicates when crediting releases

A hotfix merged with the default body still reaches release-please
twice. When crediting, a line whose commit is a merge commit is removed
if a non-merge line in the same release carries the same text; a lone
merge-commit line is credited to its pull request's author instead of
whoever merged it. CHANGELOG.md keeps the duplicate.

Refs #911

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
AIDD-Session-Id: 3adb1fb2-3894-4e52-afab-424803c7fcad

* refactor(release): shorten the release crediting comments

Refs #911

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
AIDD-Session-Id: 3adb1fb2-3894-4e52-afab-424803c7fcad

---------

Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant