Merge pull request #1454 from isuruh15/isolated-fix

Make TCP Client functions isolated

Author: MohamedSabthar

ballerina/client.bal

@@ -38,7 +38,7 @@ public isolated client class Client {
     #
     # + data - The data that need to be sent to the connected remote host
     # + return - `()` or else a `tcp:Error` if the given data cannot be sent
-    remote function writeBytes(byte[] data) returns Error? = @java:Method {
+    isolated remote function writeBytes(byte[] data) returns Error? = @java:Method {
         name: "externWriteBytes",
         'class: "io.ballerina.stdlib.tcp.nativeclient.Client"
     } external;
@@ -51,7 +51,7 @@ public isolated client class Client {
     # ```
     #
     # + return - The `readonly & byte[]` or else a `tcp:Error` if the data cannot be read from the remote host
-    remote function readBytes() returns (readonly & byte[])|Error = @java:Method {
+    isolated remote function readBytes() returns (readonly & byte[])|Error = @java:Method {
         name: "externReadBytes",
         'class: "io.ballerina.stdlib.tcp.nativeclient.Client"
     } external;

changelog.md

@@ -3,6 +3,11 @@ This file contains all the notable changes done to the Ballerina TCP package thr
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## Unreleased
+
+### Changed
+- [Mark `writeBytes` and `readBytes` methods in the client as `isolated`](https://github.com/ballerina-platform/ballerina-library/issues/7609)
+
 ## [1.12.1] - 2025-02-11
 
 ### Fixed