Skip to content
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

Merged
merged 12 commits into from
Jan 25, 2024
Merged

Bug: updated tests #569

merged 12 commits into from
Jan 25, 2024

Conversation

MelSumner
Copy link
Contributor

@MelSumner MelSumner commented Jan 23, 2024

This will end up being a major because we had to bump the node version.

Changes:

  • updated the package.json file so the scripts were sorted alphabetically.
  • consolidated node versions to latest LTS
  • updated specific dependencies
  • removed the 3.25 scenario
  • moved from testdouble to sinon
CleanShot 2024-01-22 at 19 34 56@2x

CleanShot 2024-01-23 at 09 49 48

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.

@MelSumner MelSumner force-pushed the melsumner/minor-release-prep branch 3 times, most recently from fc01f09 to 0185603 Compare January 23, 2024 01:59
@knownasilya
Copy link
Contributor

Would this be a major version change since the node version is being updated?

@MelSumner
Copy link
Contributor Author

@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?

@knownasilya
Copy link
Contributor

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.

@MelSumner
Copy link
Contributor Author

ok I'll look at that too. Do you think it wants a specific version number of Node or is =>16 type of change good enough?

@MelSumner
Copy link
Contributor Author

Yeah, I just looked at it and I have no idea why. It looks like it should be fine?

@MelSumner MelSumner force-pushed the melsumner/minor-release-prep branch from 0185603 to 62fe07a Compare January 23, 2024 15:23
@MelSumner
Copy link
Contributor Author

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.
Would that also mean a major? not sure.

@knownasilya
Copy link
Contributor

Yes a major would be required for that. Probably need to upgrade node for CI too.

Copy link
Contributor

@ef4 ef4 left a 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

@MelSumner MelSumner force-pushed the melsumner/minor-release-prep branch from b8599b5 to 9fa21ef Compare January 23, 2024 22:04
@MelSumner MelSumner requested a review from ef4 January 24, 2024 15:45
@MelSumner MelSumner changed the title Bug: updated dates so tests pass Bug: updated tests Jan 24, 2024
@MelSumner MelSumner force-pushed the melsumner/minor-release-prep branch from 6fbc1ef to c0efad1 Compare January 24, 2024 17:47
@MelSumner MelSumner force-pushed the melsumner/minor-release-prep branch from c0efad1 to 7af62e3 Compare January 24, 2024 17:47
@MelSumner MelSumner requested a review from mansona January 25, 2024 15:29
@knownasilya
Copy link
Contributor

Nice @MelSumner

Copy link
Contributor

@mansona mansona left a 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 🎉

@MelSumner MelSumner merged commit 3c38e1e into master Jan 25, 2024
2 of 6 checks passed
@MelSumner MelSumner deleted the melsumner/minor-release-prep branch January 25, 2024 15:42
@MelSumner MelSumner added bug internal maintenance that comes with software dependencies Pull requests that update a dependency file labels Jan 25, 2024
@github-actions github-actions bot mentioned this pull request Jan 25, 2024
@mansona mansona removed the internal maintenance that comes with software label Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants