-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: updated tests #569
Bug: updated tests #569
Conversation
fc01f09
to
0185603
Compare
Would this be a major version change since the node version is being updated? |
@knownasilya we might need to make it one. I'm trying to get the tests to pass and only upgrading what I need to do, in order to make that happen. WDYT? |
I'm fine with bumping a major, plenty of numbers to go around. It'll be an easy upgrade if that's the only change. Looks like the GH actions workflow is busted too. |
ok I'll look at that too. Do you think it wants a specific version number of Node or is |
Yeah, I just looked at it and I have no idea why. It looks like it should be fine? |
0185603
to
62fe07a
Compare
ok reverting the node change worked, but it looks like it is trying to test against 3.25 which I think we should just make it 3.28 or higher for this one. |
Yes a major would be required for that. Probably need to upgrade node for CI too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also don't see why these tests were passing before, but I think the fix here won't last. Once the month rolls over they would start failing again.
Here is an alternative solution that I think will be more permanent: ef4@04437ab
b8599b5
to
9fa21ef
Compare
6fbc1ef
to
c0efad1
Compare
c0efad1
to
7af62e3
Compare
Nice @MelSumner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 🎉
This will end up being a major because we had to bump the node version.
Changes:
Everything is passing locally but not here, so I think we need to figure out what must pass to get the next release out, and then what needs to be fixed after that.