Skip to content

Conversation

@ludwig-mueller
Copy link
Member

Description

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@ludwig-mueller
Copy link
Member Author

/run pipeline

@ludwig-mueller
Copy link
Member Author

ludwig-mueller commented Oct 31, 2025

Requires force merging. Branch example finished successfully. Main example will fail since workspace v4.0.8 doesn't exist

@surajsbharadwaj surajsbharadwaj merged commit f0c7c66 into main Nov 3, 2025
@surajsbharadwaj surajsbharadwaj deleted the no_proxy_suffix branch November 3, 2025 12:07
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