Skip to content

chore(master): release 1.5.1 - #18

Merged
non7top merged 1 commit into
masterfrom
release-please--branches--master
Sep 26, 2026
Merged

non7top merged 1 commit into
masterfrom
release-please--branches--master

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 6, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.5.1 (2026-09-26)

Bug Fixes

  • name the simulated merge commit in the previewed changelog (1709a26)
  • name the simulated merge commit in the previewed changelog (5a41269)
  • stop hardcoding manifest's "." key; dedupe linked-versions changelog repeats (cd4b1b0)
  • stop hardcoding the manifest's "." key, dedupe linked-versions changelog repeats (f305bc0)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--master branch from 779bcf4 to b1e0072 Compare September 26, 2026 07:52
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 release-please PREVIEW

What merging this PR into master would trigger:

Merging release-please's own release PR (release-please--branches--master) publishes v1.5.1 — a patch bump from 1.5.0 — and creates the matching tag and GitHub release.

The changelog it would publish is this PR's own description, so there's nothing to dry-run here.

Predicted from b1e0072 merged into master at cd4b1b0, with the PR title read as chore(master): release 1.5.1 · Full run

@non7top
non7top merged commit cf2e67f into master Sep 26, 2026
2 checks passed
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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