levibostian / new-deployment-tool / 14219833004

67%

push

github

refactor: update all dependencies and transition to lock file (#46)

## Related GitHub Issues
<!-- Link to any related GitHub issues that this pull request addresses
or closes. -->

## Problem
<!-- A clear description of the problem that this pull request is
solving. -->

Since we just updated to deno v2, I thought it would be nice to update
the dependencies.

## Solution
<!-- Describe the approach you took to solve the problem and the changes
made in this pull request. -->

I figured the easiest way to update the project's dependencies is to
leverage deno's built-in mechanism for updating dependencies by using
the lock file.

An alternative approach is to go into each of the source code files and
update the `http:...` import statements to a new version. So tedious.
So, this PR moves over to the use of the `deno.lock` file so we can let
deno update all our dependencies for us while still enforcing strict
versioning for the whole project.

## Testing
<!-- Choose one of the below options for how you tested the code change.
Include any specific setup or instructions for testing. -->
- [ ] Added automated tests. 
- [ ] Manually tested. If you check this box, provide instructions for
others to test, too.

The CI test suite. If it runs as expected, we consider it working. 

## Notes for reviewers 
<!-- If there is any additional information you would like to share with
the person reviewing this pull request, please provide it here. -->

1. This PR found a bug in the tool. [Fixed in another
PR](https://github.com/levibostian/new-deployment-tool/pull/47).
2. This PR introduced the idea of compiling the tool into a binary and
then running the binary instead of doing `deno run...`. [See commit
description](https://github.com/levibostian/new-deployment-tool/pull/46/commits/5f6db04b0)
to learn more. This was done because the CI test suite failed after we
[switched to the
lockfile](https://github.com/levibostian/new-deployment-tool/p... (continued)

110 of 123 branches covered (89.43%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 5 files covered. (100.0%)

712 of 1001 relevant lines covered (71.13%)

10.38 hits per line