Skip to content

chore: revert release 1.5.1 to re-test release-please flow#1976

Merged
zeitlinger merged 2 commits intomainfrom
revert-release-1.5.1
Mar 20, 2026
Merged

chore: revert release 1.5.1 to re-test release-please flow#1976
zeitlinger merged 2 commits intomainfrom
revert-release-1.5.1

Conversation

@zeitlinger
Copy link
Member

Summary

  • Revert the 1.5.1 release merge — release-please didn't create the
    tag/GitHub release after merge, likely because the PR title was
    chore: release main instead of chore(main): release 1.5.1
    (missing version in title prevents release-please from matching)
  • Re-apply the editorconfig fix (pom.xml max line length 210)
  • After merge, close chore: release main #1974 and delete the release-please--branches--main
    branch so release-please creates a fresh PR with the correct title

Test plan

  • After merge, release-please creates a new release PR with title
    chore(main): release 1.5.1
  • Merging that PR creates the v1.5.1 tag and GitHub release

This reverts commit 3524bcf.
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
The `<project xmlns=...>` declaration on line 2 of every pom.xml is
204 characters. The maven release-type in release-please touches all
pom files, triggering the editorconfig line-length check.

Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
@zeitlinger zeitlinger mentioned this pull request Mar 20, 2026
@zeitlinger zeitlinger merged commit 89052fc into main Mar 20, 2026
14 checks passed
@zeitlinger zeitlinger deleted the revert-release-1.5.1 branch March 20, 2026 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant