Skip to content

Update workflows on release 1.8 #3870

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 24, 2025

Conversation

jharvey10
Copy link
Contributor

@jharvey10 jharvey10 commented Jun 18, 2025

  • Sync workflows with main branch
  • Hold back kafka integration test image to not be latest

Almost all of the workflows are copy/paste from main, however the golangci-lint is kept back on v1 so that the config file (and associated code changes) don't need to be backported as well.

This comment has been minimized.

@jharvey10 jharvey10 marked this pull request as ready for review June 20, 2025 02:37
@jharvey10 jharvey10 requested review from jdbaldry and a team as code owners June 20, 2025 02:37
Copy link
Contributor

@jdbaldry jdbaldry left a comment

Choose a reason for hiding this comment

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

Looked at the workflows for which I'm CODEOWNER and they look good to me with some nits regarding the comments

Copy link
Contributor

@ptodev ptodev left a comment

Choose a reason for hiding this comment

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

It's hard to double check everything, bot on a high level it looks ok to me.

Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
@jharvey10 jharvey10 enabled auto-merge (squash) June 20, 2025 14:11
@jharvey10 jharvey10 merged commit 3c9e753 into release/v1.8 Jun 24, 2025
51 of 56 checks passed
@jharvey10 jharvey10 deleted the update-workflows-on-release-1.8 branch June 24, 2025 14:17
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.

3 participants