Skip to content

chore(master): release 1.7.0 - #26

Merged
non7top merged 1 commit into
masterfrom
release-please--branches--master
Oct 8, 2026
Merged

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

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.7.0 (2026-10-08)

Features

  • mark already-pending entries when a PR also adds to the pending release (e7d576f)
  • mark already-pending entries when a PR also adds to the pending release (9cf1b69)
  • warn when a PR changes the bump of an already-pending release (f161202)

Bug Fixes

  • read the version from release-please headings without a compare link (8bd7547)
  • read the version from release-please headings without a compare link (288f408)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--master branch from 484496a to 671c252 Compare October 8, 2026 01:38
@github-actions

github-actions Bot commented Oct 8, 2026

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.7.0 — a minor bump from 1.6.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 671c252 merged into master at 8bd7547, with the PR title read as chore(master): release 1.7.0 · Full run

@non7top
non7top merged commit e3afa0d into master Oct 8, 2026
2 checks passed
@github-actions

github-actions Bot commented Oct 8, 2026

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