Bump altcover from 6.1.708 to 6.2.727

[dependabot-preview]

Bumps altcover from 6.1.708 to 6.2.727.

Release notes

Sourced from altcover's releases.

Fukurou series release 7 respin

6.2.727

• [BUGFIX] Issue #74 -- Strip unwanted dependencies from released code.
• Generally, move to .net core 3.0 for build (many other changes in process only)
• With the F# 4.7 compiler, static linking FSharp.Core into the recorder has been fixed, and has been adopted
• In .net core 3.0 release, dotnet build no longer does a dotnet publish to the output directory
• Issues #68 and #73 and their fixes are now moot; in particular, FSharp.Core no longer needs to be auto-excluded from instrumentation in the .net core tool any more than in the Framework tool; nor does that assembly need to be copied if otherwise absent.

[DEPRECATED] Fukurou series release 7

6.2.726

• Generally, move to .net core 3.0 for build (many other changes in process only)
• With the F# 4.7 compiler, static linking FSharp.Core into the recorder has been fixed, and has been adopted
• In .net core 3.0 release, dotnet build no longer does a dotnet publish to the output directory
• Issues #68 and #73 and their fixes are now moot; in particular, FSharp.Core no longer needs to be auto-excluded from instrumentation in the .net core tool any more than in the Framework tool; nor does that assembly need to be copied if otherwise absent.

Fukurou series release 6

6.2.719

• [BUGFIX] #Issue73 In .net core 3.0 preview and RC, dotnet build does a dotnet publish to the output directory, including FSharp.Core in F# projects. Automatically exclude that file from instrumentation by the .net core tool to avoid mutually recursive calls between the recorder assembly and FSharp.Core that cause a stack overflow. This is not required for the Framework/Mono tool as that static links its dependency. I've not found a way to static-link FSharp.Core in the .net core world that doesn't fail with errors.
• [BUGFIX] For --visibleBranches, fix up C# loops, and the path numbering for decompiled switch/match logic

Fukurou series release 5

6.2.714

• [BUGFIX] Finish wiring up /p:AltCoverLocalSource support
• [BUGFIX] Fix failure when input/output directories were specified with a trailing separator character
• [HACK] mitigate Issue #71 by simply ignoring null module identifiers.
• [API] -v|--visibleBranches option (bool VisibleBranches default false in API, -VisibleBranches PowerShell flag) to simplify the reporting of switch or match cases where the compiler produces a tangle of if/else branches that give surprising results in a ReportGenerator output (e.g. null taking a different branch to a default case than a non-null value as per Issue 72)
• Use a leading ? as a negator for filter matches e.g. ?(a|b) means "exclude anything that doesn't match a or match b", or ?MyApp means exclude anything that doesn't contain MyApp; no valid .net regex begins with this so it's backwards compatible. Between this and the previous release's --localSource (now fully supported) option, the need to resort to cumbersome constructs involving negative lookahead regexes should be reduced.

Changelog

Sourced from altcover's changelog.

6.2.727 (Fukurou series release 7 respin)

• [BUGFIX] Issue #74 -- Strip unwanted dependencies from released code.
• Generally, move to .net core 3.0 for build (many other changes in process only)
• With the F# 4.7 compiler, static linking FSharp.Core into the recorder has been fixed, and has been adopted
• In .net core 3.0 release, dotnet build no longer does a dotnet publish to the output directory
• Issues #68 and #73 and their fixes are now moot; in particular, FSharp.Core no longer needs to be auto-excluded from instrumentation in the .net core tool any more than in the Framework tool; nor does that assembly need to be copied if otherwise absent.

6.2.719 (Fukurou series release 6)

• [BUGFIX] #Issue73 In .net core 3.0 preview and RC, dotnet build does a dotnet publish to the output directory, including FSharp.Core in F# projects. Automatically exclude that file from instrumentation by the .net core tool to avoid mutually recursive calls between the recorder assembly and FSharp.Core that cause a stack overflow. This is not required for the Framework/Mono tool as that static links its dependency. I've not found a way to static-link FSharp.Core in the .net core world that doesn't fail with errors.
• [BUGFIX] For --visibleBranches, fix up C# loops, and the path numbering for decompiled switch/match logic

6.2.714 (Fukurou series release 5)

• [BUGFIX] Finish wiring up /p:AltCoverLocalSource support
• [BUGFIX] Fix failure when input/output directories were specified with a trailing separator character
• [HACK] mitigate Issue #71 by simply ignoring null module identifiers.
• [API] -v|--visibleBranches option (bool VisibleBranches default false in API, -VisibleBranches PowerShell flag) to simplify the reporting of switch or match cases where the compiler produces a tangle of if/else branches that give surprising results in a ReportGenerator output (e.g. null taking a different branch to a default case than a non-null value as per Issue 72)
• Use a leading ? as a negator for filter matches e.g. ?(a|b) means "exclude anything that doesn't match a or match b", or ?MyApp means exclude anything that doesn't contain MyApp; no valid .net regex begins with this so it's backwards compatible. Between this and the previous release's --localSource (now fully supported) option, the need to resort to cumbersome constructs involving negative lookahead regexes should be reduced.

Commits

• e83e610 Merge branch 'develop/Fukurou' into release/Fukurou
• 0ca5585 Let's do a re-spin
• 6a9f497 Move this auto-added dependency to where it is needed but is out of the way o...
• e0600de Merge branch 'master' into release/Fukurou
• a06660b [Skip CI] Let's release
• e1e3a9f More rationalization of dependencies
• ebb81d0 Rationalize tool use
• fe1c651 Purge the reference to the old dotnet-cli tool
• a82614f Use FAKE as a local tool too
• 895f874 Take advantage of local tools for reportgenerator
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[codecov]

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #6   +/-   ##
=======================================
  Coverage   36.18%   36.18%           
=======================================
  Files          19       19           
  Lines         152      152           
  Branches        9        9           
=======================================
  Hits           55       55           
  Misses         93       93           
  Partials        4        4

---

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 3135650...9181312. Read the comment docs.

[dependabot-preview]

Superseded by #7.