wso2 / wso2/api-platform

[Bug]: Gateway version changes after the gateway is activated

Open
#2,524 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect/API Severity/Critical Type/Bug
Dominant language
Go
Stars
71
Forks
111
Avg merge
1d 14h
Merged PRs (30d)
110

Description

Please select the area the issue is related to

AI Workspace

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)

Description

When a gateway is activated, the gateway version is unexpectedly modified. The version should remain unchanged unless it is explicitly updated.

Image
Expected Behavior

The gateway version should remain the same after the gateway is activated.

Actual Behavior

The gateway version changes unexpectedly after the gateway is activated.

Before Activation
{
  "createdAt": "2026-07-07T17:16:14.455674724Z",
  "createdBy": "admin",
  "displayName": "last",
  "endpoints": [
    "localhost:8443"
  ],
  "functionalityType": "ai",
  "id": "last",
  "isActive": false,
  "isCritical": false,
  "organizationId": "default",
  "updatedAt": "2026-07-07T17:16:51.400968159Z",
  "updatedBy": "admin",
  "version": "1.2"
}
After Activation
        {
            "createdAt": "2026-07-07T17:16:14.455674724Z",
            "createdBy": "admin",
            "displayName": "last",
            "endpoints": [
                "localhost:8443"
            ],
            "functionalityType": "ai",
            "id": "last",
            "isActive": false,
            "isCritical": false,
            "organizationId": "default",
            "updatedAt": "2026-07-07T18:13:22.018022526Z",
            "version": "1.2.0-M1"
        },

Note: The "Before Activation" and "After Activation" JSON payloads in this report are identical. If the issue is that the version actually changes, please replace the second payload with the response that shows the changed version.

Steps to Reproduce
  1. Create a gateway with a specific version (e.g., 1.2).
  2. Activate the gateway.
  3. Retrieve the gateway details using the Get Gateway API.
  4. show different gateway version.
Severity Level of the Issue

Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)

Environment Details (with versions)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by creating a gateway with version 1.2, activating it, and retrieving its details through the Get Gateway API. Compare the version before and after activation, resolving the contradictory payloads in this report; done means the version remains unchanged unless explicitly updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.