I am in the process of implementing the changes for the [PDS Migrator](https://github.com/pdsinterop/solid-migrator) in our PHP code. There were some minor issues for which I'll open an MR. I noticed we are a bit behind in creating a new release. The latest tag is [v0.5.1](https://github.com/pdsinterop/php-solid-server/releases/tag/v0.5.1) from November last year. In the meantime, [117 commits have been made to `main`](https://github.com/pdsinterop/php-solid-server/compare/v0.5.1...main), mostly fixes from December to February. <sup>The same goes for [`pdsinterop/php-solid-auth#v0.6.1`](https://github.com/pdsinterop/php-solid-auth/compare/v0.6.1...main). Both [`pdsinterop/php-solid-crud#v0.3.0`](https://github.com/pdsinterop/php-solid-crud/compare/v0.3.0...main) and [`pdsinterop/flysystem-rdf#v0.3.0`](https://github.com/pdsinterop/flysystem-rdf/compare/v0.3.0...main) are already up-to-date.</sup> I was thinking of tagging a new release as `v0.6.0`. I'd like to include a fix for #43 and #46 (as they are trivial to add). Any/All changes after that, for the Migrator, would then be tagged as `v0.7.0`. ## Questions - [x] #43 - [x] #46 - [ ] #52 - [x] @ylebre Should #45 also be merged in? Or better to leave that for later? - [x] @michielbdejong Should #50 be merged in? - [x] Is there anything else that needs to be included in this release? - <sup>Maybe #16 ?</sup>
Activity
[-]New release (v0.6.0) ?[/-][+]New release (v0.6.0)[/+]ylebre commentedon Nov 15, 2021
Better to leave that for later, that code is on proof-of-concept level at best and probably insecure.