.Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...

        if (contributorsInPullRequestsButNotInReleaseNotes.isNotEmpty()) {
            error(
                """The contributors in the release notes $releaseNotes don't match the contributors in the PRs.
                Release notes:  $contributorsInReleaseNotes
                Pull requests:  $contributorsFromPullRequests
                Missed in notes:$contributorsInPullRequestsButNotInReleaseNotes

    @Test
    @DisplayName("release(): verifies it is invoked exactly once")
    void release_invokedOnce() throws Exception {
        // Arrange: no setup needed; we verify interaction only

        // Act: call release
        handle.release();

        // Assert: verify one invocation and no more
        verify(handle, times(1)).release();
        verifyNoMoreInteractions(handle);
    }

object StartReleaseCycle : BasePromotionBuildType() {
    init {
        id("Promotion_StartReleaseCycle")
        name = "Start Release Cycle"
        description = "Promotes a successful build on master as the start of a new release cycle on the release branch"

        params {
            text(
                "gitUserEmail",
                "",
                label = "Git user.email Configuration",

    init {
        id("Promotion_MergeReleaseIntoMaster")
        name = "Merge Release into Master"
        description = "Merge Release into Master"

        val vcsBranch = VersionedSettingsBranch.fromDslContext()

        steps {
            gradleWrapper {
                name = "Merge Release into Master"
                tasks =
                    listOf(

}} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.{{ .Values.clusterDomain }} To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kub...

data class VersionedSettingsBranch(
    val branchName: String,
) {
    companion object {
        private const val MASTER_BRANCH = "master"

        private const val RELEASE_BRANCH = "release"

        private const val EXPERIMENTAL_BRANCH = "xperimental"

        // master branch of gradle/gradle-promote
        private const val GRADLE_PROMOTE_MASTER_VCS_ROOT_ID = "Gradle_GradlePromoteMaster"

        @Test
        @DisplayName("release should decrement usage count")
        void shouldDecrementUsageCount() {
            transport.acquire();
            long beforeRelease = transport.getUsageCount();
            transport.release();
            assertEquals(beforeRelease - 1, transport.getUsageCount());
        }

        @Test
        @DisplayName("release should throw exception when usage count would go negative")

apiVersion: v1
kind: Service
metadata:
  name: {{ template "minio.fullname" . }}-console
  labels:
    app: {{ template "minio.name" . }}
    chart: {{ template "minio.chart" . }}
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
  {{- if .Values.consoleService.annotations }}
  annotations: {{- toYaml .Values.consoleService.annotations | nindent 4 }}
  {{- end }}
spec:
  type: {{ .Values.consoleService.type }}

it should be imported before running 'go mod vendor'.

Go release cycle considerations
===============================

Applying changes to packages that are vendored follows the considerations
written down at go.dev/s/release.

When the Go tree is open for development, a specific change may be pulled in
at any time that it is needed. During the release freeze, the bar for changes