Pull in updates #28
Pull in updates #28
Conversation
Update README.md
Signed-off-by: Benjamin Perez <benjamin@bexsoft.net>
Bumps [http-proxy-middleware](https://github.com/chimurai/http-proxy-middleware) from 2.0.7 to 2.0.9. - [Release notes](https://github.com/chimurai/http-proxy-middleware/releases) - [Changelog](https://github.com/chimurai/http-proxy-middleware/blob/v2.0.9/CHANGELOG.md) - [Commits](chimurai/http-proxy-middleware@v2.0.7...v2.0.9) --- updated-dependencies: - dependency-name: http-proxy-middleware dependency-version: 2.0.9 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: Benjamin Perez <benjamin@bexsoft.net> Co-authored-by: Benjamin Perez <benjamin@bexsoft.net>
|
One problem I think is having the default branch named I also made a list of feature changes that needs to reverted #19 I would provide the PRs myself but I am waiting until @jnfinitym is ready. |
|
@georgmangold What do you see is the best path forward to getting the right base line in? We can also do the git revert approach like you had mentioned. |
|
what the best approach is I cant tell, that’s why I am asking. But to me, reverting looked cleaner than just skipping. As I wrote, @huncrys already did the work by starting with v1.7.3 and I did the revert thing. |
7 participants
Pull in updates they made to dependecies.
Going foward we should setup something like dependabot to handle this. I don't think it is worth trying to keep in sync with minio as they ripped out so much.
Just like #27 the main branch needs to have commits removed before merging.
The workflows should also be setup, but I think you'll have to do that.