Skip to content

Tags: utilitywarehouse/patrol

Tags

v1.3.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #9 from utilitywarehouse/allChanges-handle-go-pack…

…ages

All changes -  handle go nested packages

v1.2.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #7 from utilitywarehouse/all-files-flag

Add support for checking for all files.

v1.1.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
 Detect changes in external modules' subpackages (#3)

* Detect changes in external modules' subpackages

Previously patrol would only catch a dependency upgrade in go.mod if a
local package was referring the top-level package in that dependency.
For example if your go.mod looked something like:

```
module github.com/your-org/your-module

go 1.17

require github.com/another-org/their-module v1.8.0
```

And you were to upgrade github.com/another-org/their-module to version
v1.8.1, only the packages in your module relying on
github.com/another-org/their-module would be marked as changed, while
packages depending on other nested package in that dependency wouldn't
(e.g. github.com/another-org/their-module/writer).

v1.0.0

Support references other than commit has

This enables support for flexible references, such as:
HEAD, branch, tag, heads/branch, refs/heads/branch, refs/tags/tag,
refs/remotes/origin/branch, refs/remotes/origin/HEAD, tilde and caret
(HEAD~1, master~^, tag~2, ref/heads/master~1, ...), selection by text
(HEAD^{/fix nasty bug}), hash (prefix and full).