- [Other notable changes](#other-notable-changes)
- [v1.12.9](#v1129)
  - [Downloads for v1.12.9](#downloads-for-v1129)
    - [Client Binaries](#client-binaries-1)
    - [Server Binaries](#server-binaries-1)
    - [Node Binaries](#node-binaries-1)
  - [Changelog since v1.12.8](#changelog-since-v1128)
    - [Other notable changes](#other-notable-changes-1)
- [v1.12.8](#v1128)

### Minor changes to the library {#minor_library_changes}

#### go/types

The `Var.Kind` method returns an enumeration of type `VarKind` that
classifies the variable (package-level, local, receiver, parameter,
result, or struct field). See issue #70250.

Callers of `NewVar` or `NewParam` are encouraged to call `Var.SetKind`

name: Proposals
description: New external API or other notable changes
title: "proposal: import/path: proposal title"
labels: ["Proposal"]
body:
  - type: markdown
    attributes:
      value: "Our proposal process is documented here: https://go.dev/s/proposal-process"
  - type: textarea
    id: proposal-details
    attributes:
      label: "Proposal Details"
      description: "Please provide the details of your proposal here."
    validations:

import jcifs.internal.smb2.ServerMessageBlock2Response;
import jcifs.internal.util.SMBUtil;
import jcifs.smb.NtStatus;

/**
 * SMB2 Change Notify response message.
 *
 * This response contains information about file system changes
 * that occurred in the monitored directory.
 *
 * @author mbechler
 */
public class Smb2ChangeNotifyResponse extends ServerMessageBlock2Response implements NotifyResponse {

## Changes to the language {#language}...

# limitations under the License.
# ==============================================================================
# This script dumps some information about the environment. It's most useful
# for verifying changes to the TFCI scripts system, and most users won't need
# to interact with it at all.
source "${BASH_SOURCE%/*}/utilities/setup.sh"

echo "==TFCI== env outside of tfrun:"
env
echo "==TFCI== env inside of tfrun:"

// https://github.com/gradle/gradle-private/issues/4528
// Trigger ReadyForNightly and ReadyForRelease for provider-api-migration/public-api-changes branch
// TODO: remove this after the branch is merged
const val PROVIDER_API_MIGRATION_BRANCH = "provider-api-migration/public-api-changes"
const val BOT_DAILY_UPGRADLE_WRAPPER_BRANCH = "devprod/upgrade-to-latest-wrapper"

    ) {
    init {
        id("Promotion_SnapshotFromQuickFeedbackStepUpload")
        name = "Nightly Snapshot (from QuickFeedback) - Upload"
        description = "Builds and uploads the latest successful changes on '${branch.branchName}' from Quick Feedback as a new distribution"

        steps {
            buildStep(
                ******@****.***arameters,

## Creating a hotfix branch

Customers in MinIO are allowed LTS on any release they choose to standardize. Production setups seldom change and require maintenance. Hotfix branches are such maintenance branches that allow customers to operate a production cluster without drastic changes to their deployment.

## Backporting a fix

Developer is advised to clone the MinIO source and checkout the MinIO release tag customer is currently on.

    - [Action Required](#action-required)
    - [Other notable changes](#other-notable-changes)
- [v1.9.10](#v1910)
  - [Downloads for v1.9.10](#downloads-for-v1910)
    - [Client Binaries](#client-binaries-1)
    - [Server Binaries](#server-binaries-1)
    - [Node Binaries](#node-binaries-1)
  - [Changelog since v1.9.9](#changelog-since-v199)
    - [Other notable changes](#other-notable-changes-1)
- [v1.9.9](#v199)