Skip to content

Configure branch v1 to get security updates#5864

Open
mstoykov wants to merge 1 commit intomasterfrom
v1BranchSetup
Open

Configure branch v1 to get security updates#5864
mstoykov wants to merge 1 commit intomasterfrom
v1BranchSetup

Conversation

@mstoykov
Copy link
Copy Markdown
Contributor

What?

Configure v1 branch to get security updates only

Why?

We do intend on supporting k6 v1 for a whole year. Not having security updates enabled by default will make this harder.

I am not currently enabling other updates as that likely is going to give us quite a lot more work. And if needed we can do them manually.

Checklist

  • I have performed a self-review of my code.
  • I have commented on my code, particularly in hard-to-understand areas.
  • I have added tests for my changes.
  • I have run linter and tests locally (make check) and all pass.

Checklist: Documentation (only for k6 maintainers and if relevant)

Please do not merge this PR until the following items are filled out.

  • I have added the correct milestone and labels to the PR.
  • I have updated the release notes: link
  • I have updated or added an issue to the k6-documentation: grafana/k6-docs#NUMBER if applicable
  • I have updated or added an issue to the TypeScript definitions: grafana/k6-DefinitelyTyped#NUMBER if applicable

Related PR(s)/Issue(s)

@mstoykov mstoykov requested a review from a team as a code owner April 20, 2026 09:35
@mstoykov mstoykov requested review from ankur22 and codebien and removed request for a team April 20, 2026 09:35
@mstoykov mstoykov temporarily deployed to azure-trusted-signing April 20, 2026 09:40 — with GitHub Actions Inactive
@mstoykov mstoykov temporarily deployed to azure-trusted-signing April 20, 2026 09:42 — with GitHub Actions Inactive
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