Open brannonh opened 2 years ago
@brannonh @jvanz How critical do you think this is? do we need to do this before we push 1.1.1? I am just a little worried about everything exploading when we do...
@jvanz and @brannonh what do you think of moving this tech dept to 1.2.0 so we can push out these bugfixes? This is the only remaining item in 1.1.1 we could also make a 1.1.2
For now I am going to move this to 1.1.2 so we can get 1.1.1 out the door.
I know there are security issue and stuff but it's not like those are not already present in the current version that's deployed.
To me, this seems like at least a minor update (i.e., 1.2.0), since there is a high likelihood of breaking things. It's not really fixing bugs.
do we want to move that and #37 into 1.2.0 and make a 1.3.0 for more features?
I definitely agree with that. Let's keep 1.1.x focused on any future bug fixes, work on updating the code base in 1.2.x, and adding new features in 1.3.x.
👍
We have some outdated dependencies and security vulnerabilities. We need to update and test to make sure nothing is broken.
Report from
ncu
as of 2022/09/09: