NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #3059 by repository stars
Latest stable
v0.11.1
Last release 9 months ago
22 Feb 2026
Release timing varies
gaps range from 8 days to 6 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
127 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
Patch release fixing a connection pool exhaustion bug that affects deployments using plugins with the Terminate action (e.g. gatewayd-plugin-cache).
Patch release fixing a connection pool exhaustion bug that affects deployments using plugins with the Terminate action (e.g. gatewayd-plugin-cache).
PassThroughToClient (#731)When a plugin returned the Terminate action (e.g. cache hit), the client-to-server goroutine would set a backend read deadline and exit. The server-to-client goroutine then called receiveTrafficFromServer, which returned received == 0 with a deadline-exceeded error. However, PassThroughToClient silently discarded the error when received == 0 and returned nil, causing the goroutine to spin in an infinite loop:
Received data from database function=proxy.passthrough length=0
Because the goroutine never exited, OnTraffic never returned, Disconnect never ran, and the backend connection was permanently leaked. Under sustained traffic this exhausted the entire connection pool.
Fix: Propagate the error when received == 0 && err != nil so the goroutine exits cleanly and the connection is properly recycled.
OnTrafficFromServer where the v1.Struct response pointer was shared between gRPC serialization and the UpdateCache goroutine, causing corrupted responsesFull Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.11.0...v0.11.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →
After more than 6 months since v0.10.3, we're excited to ship GatewayD v0.11.0, a significant releases in the project's history. The highlight is pre-
After more than 6 months since v0.10.3, we're excited to ship GatewayD v0.11.0, a significant releases in the project's history. The highlight is pre-authenticated backend pool connections, a foundational capability that transforms how GatewayD manages PostgreSQL connections and unlocks critical use cases like identity brokering via the auth plugin.
This is the most important change in v0.11.0. Previously, backend connections in the pool were raw TCP sockets. They had no PostgreSQL session state until a client connected and the startup handshake was forwarded through. With pre-auth, GatewayD now performs the full PostgreSQL startup handshake (including authentication) immediately after establishing each backend TCP connection, so pool connections are ready for queries before any client arrives.
Why pre-auth matters:
DISCARD ALL to reset the backend session state instead of tearing down and re-establishing the TCP connection. This is significantly faster and reduces load on the PostgreSQL server.Configure it via the new startupParams block in the client config:
clients:
default:
writes:
startupParams:
user: postgres
database: postgres
password: postgres
The traffic handling model in OnTraffic has been redesigned. Instead of using channels to coordinate the client-to-server and server-to-client goroutines, both goroutines now participate in a sync.WaitGroup. OnTraffic blocks until both goroutines have fully exited, guaranteeing the backend connection is idle before attempting session reset or recycling. This eliminates a class of race conditions where DISCARD ALL could collide with a still-active reader.
Additionally, the shutdown sequence has been improved: the server status is now set to "stopped" before proxies are shut down, so OnClose hooks can detect the shutdown-in-progress state and avoid spurious error logs. Expected shutdown errors (e.g. ErrClientNotFound during cleanup) are now logged at DEBUG level instead of ERROR.
A new StandardLogWriter captures Go stdlib log output (used internally by raft-boltdb) and redirects it through zerolog with proper formatting and the "component": "raftboltdb" tag. Raft TCP transport output is now discarded instead of writing to stderr. This ensures all log output flows through GatewayD's structured logging pipeline.
Fixed a bug where hclog.Format values (used by hashicorp/go-plugin) were not rendered correctly in the hclog-to-zerolog adapter. Format strings are now properly interpolated via fmt.Sprintf.
Close() calls.ExpireBackendReadDeadline() and ClearBackendDeadline() allow precise control over backend connection deadlines during goroutine teardown.ErrCodePgStartupFailed and ErrCodePgResetSessionFailed for pre-auth error handling.zerolog.Logger{} and zerolog.New(nil) with zerolog.Nop() across all test files for correctness.test-postgres-up and test-postgres-down targets for running local PostgreSQL containers during development.Major dependency bumps include:
| Dependency | Old | New |
|---|---|---|
| gatewayd-plugin-sdk | v0.4.3 | v0.4.4 |
| OpenTelemetry | v1.37.0 | v1.40.0 |
| gRPC | v1.74.2 | v1.79.1 |
| jackc/pgx | v5.7.5 | v5.8.0 |
| redis/go-redis | v9.12.0 | v9.18.0 |
| hashicorp/go-plugin | v1.6.3 | v1.7.0 |
| sentry-go | v0.35.0 | v0.42.0 |
| protobuf | v1.36.7 | v1.36.11 |
| testcontainers-go | v0.38.0 | v0.40.0 |
New dependency: xdg-go/scram v1.2.0 for SCRAM-SHA-256 authentication support.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.10.3...v0.11.0
Update deps by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/685
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.10.2...v0.10.3
Add Raft State Management for Load Balancers by @sinadarbouy in https://github.com/gatewayd-io/gatewayd/pull/641
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.10.1...v0.10.2
Nothing published for this version
OpenSSL Update: Upgraded to 3.3.2-r1 to address CVE-2024-9143.
This release introduces Raft-based state management for GatewayD to ensure efficient and consistent coordination between multiple instances. By leveraging HashiCorp’s Raft implementation, GatewayD now maintains a unified state for parameters like connection pools and load-balancer strategies across all instances in a cluster, ensuring high availability, consistency, scalability, and efficiency.
High Availability: Ensures the system remains operational even if individual instances fail. Raft provides fault tolerance by replicating state across multiple nodes, enabling consistent state retrieval and updates during failover scenarios.
Consistency: Guarantees that all instances in the cluster share the same view of stateful parameters, such as connection pools and load-balancer strategies, maintaining synchronized operations across distributed instances.
Scalability: Simplifies state coordination in clusters, enabling seamless scaling of GatewayD instances without introducing inconsistencies or requiring manual intervention.
Efficiency: Propagates updates to stateful parameters in real-time, ensuring optimal load balancing and resource utilization across instances.
This update resolves inconsistencies in the previous per-instance state management approach, ensuring scalable and robust operation for GatewayD clusters. A huge thanks to @sinadarbouy for his excellent work on this implementation! 🎉
This release also includes several critical updates and fixes to enhance security, improve performance, and maintain compatibility:
3.3.2-r1 to address CVE-2024-9143.golang.org/x/crypto to the latest version.softprops/action-gh-release to v2 for enhanced functionality and compatibility.Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.10.0...v0.10.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Get status of TLS from server service by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/629
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.10...v0.10.0
Nothing published for this version
This release marks the culmination of the v0.9.x milestone, packed with significant new features, fixes, and enhancements that have made GatewayD more
This release marks the culmination of the v0.9.x milestone, packed with significant new features, fixes, and enhancements that have made GatewayD more robust, stable, and scalable. Key highlights include the introduction of the policy engine, aka. the Act system, in v0.9.0, the plugin scaffold feature in v0.9.5, and the load balancing feature in v0.9.7, among many others.
Over the course of this milestone, we merged 89 squashed commits into the main branch, resolved 30 issues, reviewed numerous PRs and published 11 releases — thanks to the perseverance and contributions of our amazing community. None of this would have been possible without their dedication.
Looking ahead, there's even more in store, and we invite you to get involved. Whether you're a user or a tester, your participation is crucial. If you're ready to contribute, @mostafa is here to support you every step of the way.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.9...v0.9.10
Nothing published for this version
Nothing published for this version
Add metric labels by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/612
plugin scaffold command by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/613interface{} to any by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/614proxy.shouldTerminate function and move the functionality to Act.Registry by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/615Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.8...v0.9.9
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release introduces several key enhancements and fixes. A significant improvement is the integration of PostgreSQL test containers for seamless in
This release introduces several key enhancements and fixes. A significant improvement is the integration of PostgreSQL test containers for seamless integration testing, replacing hardcoded addresses with dynamic test container addresses. This ensures a consistent test environment across various packages such as api, cmd, and network, and centralizes the setup in a reusable function. Additionally, dependency updates were made, including the latest GatewayD SDK, and the gomoddirectives linter was disabled to streamline development. The plugin configuration was updated to utilize the cache plugin version 0.4.0. A major bug has been fixed that improved handling of PostgreSQL's COPY command, as explained here, plus other bugfixes and improvements.
This wouldn't be possible without @sinadarbouy's contributions. 🙏
COPY command and a few others by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/610Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.7...v0.9.8
Nothing published for this version
Bugfix/workflow vulnerability comparison by @sinadarbouy in https://github.com/gatewayd-io/gatewayd/pull/569
This release contain a major change, where each tenant can now connect to multiple databases, contrary to the previous one-tenant-one-database approach, and use server load balancing strategies to distribute the load among these databases. Random, round robin and weighted RR strategies with consistent hashing are supported, thanks to @sinadarbouy and @eabasir for their contributions.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.6...v0.9.7
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
In this release of GatewayD, several updates and fixes have been made. Support for queueing asynchronous actions in the background was added (thanks t
In this release of GatewayD, several updates and fixes have been made. Support for queueing asynchronous actions in the background was added (thanks to @Hamsajj :pray:). This feature allows the output of policy evaluation by Act to be published to a Pub/Sub queue on Redis and plugin and external consumers can consume and run arbitrary actions based on that.
Provenance attestation and SBOM features were added, along with an Alpine update. Setup issues were resolved. The REDIS_URL environment variable can be used to setup the cache plugin. The policy input has been enriched to include plugin parameters and its result for better policy evaluation. Dependencies were updated, including a bump of grpc-gateway to version 2.20.0. The Dockerfile linting was added to the CI workflow.
Additionally, an issue with IP address binding that prevented external access to the containers from the host machine was fixed (thanks to @sinadarbouy 🙏).
REDIS_URL to set up the cache plugin by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/539Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.5...v0.9.6
Nothing published for this version
Nothing published for this version
New security policy: @ChrisD-Git contributed the security policy and guidelines, which should be followed when reporting vulnerabilities.
This release contains a lot of improvements to the overall reliability and stability of GatewayD and a very nice feature contributed by @zeina1i (thank you 🙏). This release also has two first-time contributors: @ChrisD-Git and @smnmna99, which we are really grateful for (thank you🙏).
Plugin scaffolding feature: Previously the plugin template for Go was the go-to method for developing new plugins for GatewayD. @zeina1i integrated the template into the GatewayD CLI, so that you can create a new plugin scaffold and be able to test it in one place using the following command.
$ gatewayd plugin scaffold -h
Scaffold a plugin and store the files into a directory
Usage:
gatewayd plugin scaffold [flags]
Flags:
-h, --help help for scaffold
-i, --input-file string Plugin scaffold input file (default "input.yaml")
-o, --output-dir string Output directory for the scaffold (default "./plugins")
An example input file is as follows. Note that the repository name defines the plugin name.
remote_url: https://github.com/gatewayd/test-gatewayd-plugin
version: 0.1.0
description: This is test plugin
license: MIT
authors:
- Author 1 <author1@example.com>
For more information, please refer to the updated Plugin Developers' Guide in the docs.
New security policy: @ChrisD-Git contributed the security policy and guidelines, which should be followed when reporting vulnerabilities.
@smnmna99 added OpenTelemetry tracing to the API, which means that almost everything in GatewayD can now be traced using OTLP gRPC.
gatewayd plugin scaffold CLI docs by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/528Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.4...v0.9.5
Nothing published for this version
This is a maintenance release and it contains a lot of fixes and improvements to linting, dependency updates, build process and fixes for issues found
This is a maintenance release and it contains a lot of fixes and improvements to linting, dependency updates, build process and fixes for issues found during code inspection. The last piece of the puzzle is contributed by @likecodingloveproblems (thank you! :pray:) in #503, where he went through all the code and updated the signature of all the constructor function to receive structs, instead of individual parameters. This helps ensure code quality is on par with the latest best practices in Go ecosystem.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.3...v0.9.4
Nothing published for this version
Dependency updates: the dependency updates ensure GatewayD stays compatible with other packages and secure from vulnerabilities found in older version…
This release introduces several updates and improvements, marking a collaborative effort among multiple contributors. Key changes in this release include:
gatewayd command: this enhancement allows for automatic generation of markdown docs from command help texts.The release is a good example of the collaborative effort of the community, thanks to @Hamsajj and @zeina1i for their contributions.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.2...v0.9.3
Nothing published for this version
Nothing published for this version
Improvements to the gatewayd plugin install command, now featuring a new option, --skip-path-slip-verification. This allows bypassing Tar and Zip Slip
This release includes:
gatewayd plugin install command, now featuring a new option, --skip-path-slip-verification. This allows bypassing Tar and Zip Slip verification, facilitating the extraction and installation of plugins into absolute paths in isolated environments such as Docker.install_plugins that utilizes an Alpine image. This service executes the setup.sh script to download and install GatewayD and its plugins. Additionally, a Redis image has been used to ensure the cache plugin functions correctly. The GatewayD ports have been made accessible to the host system.Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.1...v0.9.2
Nothing published for this version
The `pgx/v5` package was updated to prevent CVE-2024-27304. This CVE has little to no impact on GatewayD and plugins, yet it was better to upgrade. Th…
This releases contains updates to dependencies and a feature contributed by @Hamsajj. The pgx/v5 package was updated to prevent CVE-2024-27304. This CVE has little to no impact on GatewayD and plugins, yet it was better to upgrade. The SDK, the plugin template for Go and all the plugins are updated as well.
[!IMPORTANT]
Update GatewayD and all the plugins to their latest versions.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.9.0...v0.9.1
Nothing published for this version
…and control within GatewayD. It involves breaking changes as the old termination requests method has been refactored, necessitating updates to all plu…
This release introduces the Act system based on this proposal, which offers significant enhancements over the old signaling method which was limited to a single signal: terminate. This new system supports multiple signals, offers easily controllable policies by users, and allows actions to be executed in both synchronous and asynchronous modes.
The Act system comprises several components including Act registry, signals, policies, actions, and changes to the plugin registry, aimed at improving flexibility and control within GatewayD. It involves breaking changes as the old termination requests method has been refactored, necessitating updates to all plugins to accommodate these changes. For more detailed information, please visit this pull request and the Act docs.
This release lays the foundation for this proposal by moving away from the old signaling methods. In future releases the proposal will be developed and implemented to its full extent, enabling extensibility, distributed action execution, and many other features.
[!IMPORTANT] This version of GatewayD is backward-incompatible with older versions of the plugins. So, please update all the plugins to their latest version to use the new features.
Feel free to test GatewayD and provide feedback via issues or on the proposal.
cmd/utils.go by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/474Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.13...v0.9.0
This is the last release of the milestone v0.8.x and so far the functionality is improved, more tests are added and there were many cleanups. The chan
This is the last release of the milestone v0.8.x and so far the functionality is improved, more tests are added and there were many cleanups. The changelog for v0.8.x of GatewayD includes several significant changes and enhancements:
gnet/v2 with Go net stdlib package.For detailed information on each update, please visit the releases page.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.12...v0.8.13
Nothing published for this version
This is a maintenance release and contains dependency updates and minor fixes suggested by different linters.
This is a maintenance release and contains dependency updates and minor fixes suggested by different linters.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.11...v0.8.12
Nothing published for this version
Nothing published for this version
This release contains a few important changes:
This release contains a few important changes:
gatewayd_plugins.yaml file that also contains url of the plugin plus the version. This helps containerized environments to have run GatewayD in an stateless way. The gatewayd plugin install command will download and install all the plugins and you can choose to prevent config file from being overwritten, for example, when you pass it as a configmap in k8s. Please refer to the CLI docs for more information.api_requests_total and the api_requests_errors_total are counter metrics that also include these labels: method, endpoint and error.Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.10...v0.8.11
Nothing published for this version
This release contains two updates:
This release contains two updates:
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.9...v0.8.10
This release includes several enhancements and fixes:
This release includes several enhancements and fixes:
golang.org/x/crypto package in response to a security advisory. Although we don't use the specific algorithms highlighted in the report, we opted for caution.Engine object with the Server code, courtesy of @snowAvocado.Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.8...v0.8.9
This release contains builds upgrades to the GitHub Actions used in build and publish process and we now have builds for linux/arm64, which means that
This release contains builds upgrades to the GitHub Actions used in build and publish process and we now have builds for linux/arm64, which means that the Docker image can be used on the (not so) new Apple chipsets (M1/M2) and (possibly — untested) all other 64bit ARM chipsets, thanks to @hamedsalim1999! :rocket:
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.7...v0.8.8
This release is a maintenance release and includes these changes:
This release is a maintenance release and includes these changes:
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.6...v0.8.7
Nothing published for this version
This release contains many fixes, features and enhancements.
This release contains many fixes, features and enhancements.
dialTimeout: A new timeout duration is added to the client object that will set a timeout on the connection dialing (initiation) function. It will stop the client from blocking forever, if it cannot connect to the database server.startTimeout: Previously the start timeout for the plugins were a constant default of 60s, which is now configurable from the plugins config file.Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.5...v0.8.6
This release adds the TLS termination for incoming Postgres clients, enabling various SSL modes. From now on, GatewayD will act as a TLS server when n
This release adds the TLS termination for incoming Postgres clients, enabling various SSL modes. From now on, GatewayD will act as a TLS server when new clients are trying to connect via any supported SSL mode. For now, the traffic between GatewayD and Postgres will still be in plaintext, yet the traffic between GatewayD and the clients, e.g. psql, will be encrypted.
TLS works differently in Postgres than other databases. In Postgres, the first message is a SSLRequest, instead of TLS handshake request, which the server should either reply with an S to acknowledge that the server supports TLS and the client can initiate TLS handshake or an N to reject SSL request altogether (and possibly continue with plaintext communication). Postgres clients have six SSL modes:
disable: client tries to connect with SSL disabled, and the first request will be a StartupMessage.allow: client authenticates with SSL if server enforces it (GatewayD doesn't enforce SSL at the moment).prefer: tries to connect with an SSLRequest, and if server returns either of the following responses:
S: continue with TLS handshake, because the server supports it (GatewayD returns this if TLS is enabled).N: continue with a StartupMessage, because the server doesn't support TLS (GatewayD return this if TLS is disabled).require: requires SSL and fails if the server doesn't support it, which results in these scenarios:
N and will get disconnected.verify-ca and verify-full: verifies server certificates and chain of trust (See: https://github.com/gatewayd-io/gatewayd/issues/365#issuecomment-1796395674).Note All the SSL modes are tested and supported. Also, GatewayD doesn't enforce TLS, unless the client requests it.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.4...v0.8.5
This release contains a few features and fixes and a breaking change:
This release contains a few features and fixes and a breaking change:
$ curl http://localhost:18080/healthz
{"status":"SERVING"}
$ grpc-client-cli health localhost:19090
{
"status": "SERVING"
}
plugin install has undergone some changes:
--no-prompt=false flag.plugin install command, users can now choose whether they want to create a backup of the current plugins config file (if it exists) before proceeding with the installation. This can be achieved by using the --backup=true flag.plugin install command will replace the plugin configuration of the newly installed plugin with any existing configuration for a plugin in the plugins list that shares the same name. You can enable this behavior using the --update=true flag.Warning Important Change in
plugin installCommand Starting with this release, there is a breaking change in theplugin installcommand. By default, the interactive prompt is now disabled (--no-prompt=true) when installing a new plugin. If an existing plugin with the same name is detected during installation, the process will be aborted, and any downloaded files will be automatically deleted, unless you pass the--cleanup=falseflag.To override this default behavior and have more control:
- Enable the interactive prompt to be notified of the changes and have the option to approve or deny them.
- Pass the appropriate flags to enable the update and backup features.
These changes are aimed at enhancing your control over the installation process and minimizing any unexpected actions when dealing with plugins. Please adjust your installation process accordingly to accommodate these modifications.
plugin install by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/349log.Panic by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/351Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.3...v0.8.4
Nothing published for this version
Nothing published for this version
This release contains a significant update in GatewayD with #344. In this PR, substantial enhancements have been made to the GatewayD server by removi
This release contains a significant update in GatewayD with #344. In this PR, substantial enhancements have been made to the GatewayD server by removing the gnet/v2 library used for serving incoming client connections and replacing it with the net package from the Go standard library. These changes are aimed at improving performance, reliability, and fixing various race conditions within the codebase.
This change introduced bidirectional communication between the server and clients. Previously, GatewayD used to wait for the client to initiate a query and then waited for the server to send a response, which created a dependency on the client to trigger the server's response. With the new system, the server and clients are polled independently, enabling features such as LISTEN and NOTIFY from PostgreSQL. Query cancellation also works as expected now (#209).
Warning The changes in this PR are backward-incompatible with previous version of GatewayD.
The following configuration parameters have been removed from the server configuration, as they are no longer applicable:
multiCore: True
lockOSThread: False
loadBalancer: roundrobin
readBufferCap: 134217728
writeBufferCap: 134217728
socketRecvBuffer: 134217728
socketSendBuffer: 134217728
reuseAddress: True
reusePort: True
tcpKeepAlive: 3s # duration
tcpNoDelay: True
A small timing benchmark was conducted using psql, where a query involving a table with 158369 records across 17 columns was executed that resulted in 67736218 bytes (~67.73 MB) data transfer from server to the client. The results showed a significant improvement in data transfer speed. Specifically, data transfer time was increased by approximately 41% compared to direct connection to database, and an impressive 91% reduction in comparison to version 0.8.2 (with the original overhead of 132%). More performance benchmarks will be conducted later (#342).
gnet/v2 by @mostafa in https://github.com/gatewayd-io/gatewayd/pull/344Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.2...v0.8.3
> The next release will be backward incompatible with all the releases up to this point, since the server and the proxy are going to be heavily refact…
This release adds a tiny feature for cleaning up after installing a plugin and a configuration and test for multi-tenancy.
Note The next release will be backward incompatible with all the releases up to this point, since the server and the proxy are going to be heavily refactored.
Full Changelog: https://github.com/gatewayd-io/gatewayd/compare/v0.8.1...v0.8.2
One column per quarter.