Releasing
=========

### Prerequisite: Sonatype (Maven Central) Account

Create an account on the [Sonatype issues site][sonatype_issues]. Ask an existing publisher to open
an issue requesting publishing permissions for `com.squareup` projects.


Cutting a Release
-----------------

1. Update `CHANGELOG.md`.

2. Set versions:

    ```
    export RELEASE_VERSION=X.Y.Z
    export NEXT_VERSION=X.Y.Z-SNAPSHOT
    ```

    validations:
      required: true
  - type: textarea
    id: retraction-reason
    attributes:
      label: "What is the reason that you could not retract this package instead?"
      description: |
        Requesting we remove a module here only hides the generated documentation on pkg.go.dev.
        It does not affect the behaviour of proxy.golang.org or the go command.

     */

    public synchronized static void setDefault(final NtlmAuthenticator a) {
        if (auth != null) {
            return;
        }
        auth = a;
    }

    /**
     * Gets the URL that is requesting authentication.
     * @return the URL requiring authentication
     */
    protected final String getRequestingURL() {
        return url;
    }

    /**

	}

	parts1, errs1 := readAllFileInfo(ctx, erasureDisks, "", bucket, object1, "", false, false)
	parts1SC := globalStorageClass

	// Object for test case 2 - No StorageClass defined, MetaData in PutObject requesting RRS Class
	object2 := "object2"
	metadata2 := make(map[string]string)
	metadata2["x-amz-storage-class"] = storageclass.RRS

     * @return the default authentication credentials provider
     */
    public static NtlmAuthenticator getDefault() {
        return auth;
    }

    /**
     * Gets the URL that is requesting authentication.
     * @return the URL requiring authentication
     */
    protected final String getRequestingURL() {
        return this.url;
    }

    /**

carefully. Because of this, if you're interested in seeing a new feature in
Guava, the best approach is to create an [issue][] (or comment on an existing
issue if there is one) requesting the feature and describing specific use cases
for it.

If the feature has merit, it will go through a thorough process of API design
and review. Any code should come after this.

        ActionResponse result = authenticator.getResponse(null);

        // Verify
        assertNull(result);
    }

    public void test_getResponse_withUnsetType() {
        // Execute - requesting type without setting response
        ActionResponse result = authenticator.getResponse(SsoResponseType.METADATA);

        // Verify
        assertNull(result);
    }

    // Test logout method

        if (!connected) {
            throw new IOException("Witness client not connected");
        }

        try {
            log.debug("Requesting async notifications");

            // Create and populate the RPC message
            WitnessAsyncNotifyMessage message = new WitnessAsyncNotifyMessage();
            message.setContextHandle(contextHandle);

        when(limitedConfig.getLeaseBreakTimeout()).thenReturn(60);

        LeaseManager limitedManager = new LeaseManager(limitedContext);

        try {
            // Request 3 leases (should evict the oldest when requesting the 3rd)
            Smb2LeaseKey key1 = limitedManager.requestLease("/share/file1.txt", Smb2LeaseState.SMB2_LEASE_READ_CACHING);
            Thread.sleep(5); // Small delay to ensure different timestamps

* Review those pull requests, requesting changes or approving them. For the languages I don't speak, I'll wait for several others to review the translation before merging.

/// tip