Moved PSL test utils to their own package.49180f65Īlong with improvements to our CI, we have made various improvements to make PSL’s testing more robust and accessible for new contributors: Python versions 3.7, 3.8, and 3.9 are tested.Java versions 8, 11, 16, and 17 are tested.Non-release builds are pushed to the Sonatype snapshot repository (Java artifacts) and.Updated PyPi versioning to create unique identifiers for each build.In addition, many new checks have been added to the PSL CLI, including: CIĬontinuous integration (CI) for PSL has moved from Travis to Github Actions. PSL 2.3.0 comes with various improvements to our infrastructure and software quality. Tags will continue to be used to track releases (major and minor). Going forward, only one branch, main, will be used, which will contain all active development.

Previously, the default branch master tracked the latest stable PSL release, while the develop branch contained all active development. Tags are included in the PSL examples repository that track specific versions of PSL to help you ensure the examples are using the same version of PSL as you.īoth the primary PSL repository as well as the PSL examples repository are changing their branching scheme. PSL 3.0.0 will contain breaking including dropping Java 7 support.įor those of you that learn better by example, check out the PSL examples repository. In this changelog, you will find a list of the major changes in 2.3.0 as well as information on migrating from 2.2.2.Ģ.3.0 is scheduled to be the last minor release before our next major release, PSL 3.0.0. We have made great improvements to PSL in the areas of optimization and infrastructure. We are happy to announce the release of PSL version 2.3.0! TODO: Switch code views from develop to 2.3.0

Non breaking space code