You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All notable changes to Docker and Docker Compose resources for WSO2 API Management version `4.2.x` in each resource release, will be documented in this file.
3
+
All notable changes to Docker and Docker Compose resources for WSO2 API Management version `4.3.x` in each resource release, will be documented in this file.
4
4
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
6
6
7
-
## [v4.3.0.1] - 2023-03-21
7
+
## [v4.3.0.1] - 2024-04-26
8
8
9
9
### Changed
10
10
- Update all Docker resources to support WSO2 API Manager version `4.3.0`.
11
11
- Update all Docker Compose resources to supprt WSO2 API Manager version `4.3.0`.
12
12
- Update Docker Compose resources for the deployment of WSO2 APIM with MI to support Micro Integrator version `4.3.0.1`.
13
-
- Update IS extentions to the [latest version](https://repo1.maven.org/maven2/org/wso2/km/ext/wso2is/distribution/1.4.2/)`1.4.2` and mount wso2carbon and client-truststore keystores with the latest wso2carbon certificate in Identity Server as Key Manager with Choreo Analytics deployment setup.
13
+
- Update IS extentions to the latest version (`1.7.8`) and mount wso2carbon and client-truststore keystores with the latest wso2carbon certificate in Identity Server as Key Manager with Choreo Analytics deployment setup.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -23,21 +23,21 @@ The issues page on GitHub is for tracking bugs and feature requests. When posing
23
23
24
24
If you like to contribute with a bug fix or a new feature, start by posting an issue and discussing the best way to implement it.
25
25
26
-
Unlike most projects, development for this repository is carried out on the `4.2.x` branch. This is because the `master` branch contains the latest stable release of the project.
27
-
The code in `4.2.x` is merged to the `master` branch after a final review and a round of testing.
26
+
Unlike most projects, development for this repository is carried out on the `4.3.x` branch. This is because the `master` branch contains the latest stable release of the project.
27
+
The code in `4.3.x` is merged to the `master` branch after a final review and a round of testing.
28
28
29
29
Please follow these guidelines when contributing to the code:
30
30
31
31
1. Fork the current repository.
32
-
2. Create a topic branch from the `4.2.x` branch.
32
+
2. Create a topic branch from the `4.3.x` branch.
33
33
3. Make commits in logical units.
34
34
4. Before you send out the pull request, sync your forked repository with a remote repository. This makes your pull request simple and clear.
0 commit comments