feat(manifest): add support for releasing root module

[bcoe]

Add support for a special "." path which indicates that a root module should be released.

This is for the googleapis use-case.

CC: @joeldodge79

[codecov]

Codecov Report

Merging #833 (f866610) into master (f06894c) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #833   +/-   ##
=======================================
  Coverage   93.73%   93.73%           
=======================================
  Files          64       64           
  Lines        9148     9152    +4     
  Branches      980      930   -50     
=======================================
+ Hits         8575     8579    +4     
  Misses        570      570           
  Partials        3        3           

Impacted Files	Coverage Δ
src/manifest.ts	100.00% <100.00%> (ø)
src/release-pr.ts	94.47% <100.00%> (+0.02%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f06894c...f866610. Read the comment docs.

[joeldodge79]

I'm a little surprised this worked as smoothly as it did! but it does seem like we're missing a changelog entry for @node/pkg1 in the root changelog ?

[joeldodge79]

random question: how do you setup interactive debugging on this project? I've been cherry-picking this commit to use vscode debugging

[joeldodge79]

also, I think we should add a test under the describe('githubRelease' section. I'd be curious to see what the tag creation looks like for the root package.

also maybe a note somewhere in docs/manifest-releaser.md about this root pkg ability?

[bcoe]

Done 👍

[joeldodge79]

minor test typo/nits but phew! glad the overwritten changelog was just a test bug

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.