assertArgumentNotNull("out", out);

        final FileOutputStream os = OutputStreamUtil.create(out);
        try {
            final FileChannel channel = os.getChannel();
            final ByteBuffer buffer = ByteBuffer.wrap(in);
            return ChannelUtil.write(channel, buffer);
        } finally {
            CloseableUtil.close(os);
        }
    }

    /**

name: Latest Changes

on:
  pull_request_target:
    branches:
      - master
    types:
      - closed
  workflow_dispatch:
    inputs:
      number:
        description: PR number
        required: true
      debug_enabled:
        description: 'Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'
        required: false
        default: 'false'

jobs:
  latest-changes:

[discrete]
[[breaking-changes-${majorDotMinor}]]
=== Breaking changes

The following changes in {es} ${majorDotMinor} might affect your applications
and prevent them from operating normally.
Before upgrading to ${majorDotMinor} review these changes and take the described steps
to mitigate the impact.

NOTE: Breaking changes introduced in minor versions are
normally limited to security and bug fixes.

* `tf.lite`
    * `Dequantize` op supports `TensorType_INT4`.
        * This change includes per-channel dequantization.
    * Add support for `stablehlo.composite`.
    * `EmbeddingLookup` op supports per-channel quantization and `TensorType_INT4` values.
    * `FullyConnected` op supports `TensorType_INT16` activation and `TensorType_Int4` weight per-channel quantization.

```

### Create your feature branch

Before making code changes, make sure you create a separate branch for these changes

```
git checkout -b my-new-feature
```

### Test MinIO server changes

After your code changes, make sure

- To add test cases for the new code. If you have questions about how to do it, please ask on our [Slack](https://slack.min.io) channel.
- To run `make verifiers`

import static org.junit.jupiter.api.Assertions.assertNull;

import org.junit.jupiter.api.Test;

class AvChannelBindingsTest {

    /**
     * Test that the constructor correctly initializes with a valid channel binding hash.
     */
    @Test
    void testConstructorWithValidHash() {
        byte[] testHash = { 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08 };

Making and Submitting Changes
--------------

We accept Pull Requests via GitHub. The [developer mailing list][dev-ml-list] is the
main channel of communication for contributors.  
There are some guidelines which will make applying PRs easier for us:
+ Create a topic branch from where you want to base your work (this is usually the master branch).
  Push your changes to a topic branch in your fork of the repository.

ppc64 require // 16 byte alignment of the data. To avoid that // requirement, data is loaded using LXVD2X and // STXVD2X with VPERM to reorder bytes correctly. // I have identified some areas where I believe // changes would be needed to make this work for big // endian; however additional changes beyond what I // have noted are most likely needed to make it work. // - The string used with VPERM to swap the byte order // for loads and stores. // - The constants that are loaded from CPOOL. // // The following...

ppc64 require // 16 byte alignment of the data. To avoid that // requirement, data is loaded using LXVD2X and // STXVD2X with VPERM to reorder bytes correctly. // I have identified some areas where I believe // changes would be needed to make this work for big // endian; however additional changes beyond what I // have noted are most likely needed to make it work. // - The string used with VPERM to swap the byte order // for loads and stores. // - The constants that are loaded from CPOOL. // // The following...

2. Accept the changes.\
If you are sure that the changes are intentional, follow the steps described in the report.
This includes adding the description of the changes to the `accepted-public-api-changes.json` file, and providing a reason for each change.
You can add the changes to any place in the file, e.g. at the top.

3. Make sure the file with accepted changes is sorted.\