Skip to content

fix(k6-operator): add to v1.2.x to fix mismatch between next and actual latest #2037

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 1 commit into from
Aug 15, 2025

Conversation

yorugac
Copy link
Contributor

@yorugac yorugac commented Aug 15, 2025

What?

A bit annoying but another PR is needed: latest changed to v1.2.x in-between the opening and review of #2026
So it's published but not seen as "latest" now. Bad timing, in other words.
image
image

Checklist

  • I have used a meaningful title for the PR.
  • I have described the changes I've made in the "What?" section above.
  • I have performed a self-review of my changes.
  • I have run the npm start command locally and verified that the changes look good.
  • I have made my changes in the docs/sources/k6/next folder of the documentation.
  • I have reflected my changes in the docs/sources/k6/v{most_recent_release} folder of the documentation.
  • I have reflected my changes in the relevant folders of the two previous k6 versions of the documentation (if still applicable to previous versions).
  • I have made my changes in the docs/sources/k6/next folder of the documentation.

Related PR(s)/Issue(s)

A follow up to #2026

Copy link
Contributor

github-actions bot commented Aug 15, 2025

💻 Deploy preview deleted.

@yorugac yorugac merged commit 34f5bd4 into main Aug 15, 2025
8 checks passed
@yorugac yorugac deleted the fix/latest-changed-inbetween-pr-reviews branch August 15, 2025 19:33
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.

2 participants