binaries
No definition
The passages, in corpus order
4 files.
TermLinter1
- line 6
…safe fixes with --fix, and runs the same way as an npm package, a standalone binary, a GitHub action, a GitLab component, the container image or a pre-commit ho…
TermRelease1
- line 6
…y published package is packed and attached to a release with the standalone binaries of the linter, the checksums and the licence inventory, and the same tarbal…
DecisionMinHash for twin resources1
- line 8
… helps recognise the forms of one document works on extracted text, never on binary content, and never compares every pair. Each text goes to its comparison for…
ProcessRelease4
- line 7
… the changelog entries with the tarball of every package and the standalone binaries as assets, and the mirrors of the GitHub action and the GitLab component at…
- line 14
The release workflow tags the merge commit v<x.y.z>, builds the standalone binaries on three platforms, packs every published package, verifies the licence inve…
2 other passages
- line 14
…from the tag with the changelog entries of the version as its notes and the binaries, the tarballs, the checksums and the inventory as its assets; the manifest …
- line 16
…; it then lints the faulty corpus through the published command line from an empty folder and through the binary of the release, and the two reports must match.
What we know
- Occurrences
- 7
- Files
- 4
- Spaces
- Glossary, Specifications
No declared property: there is no file for this word.
See the neighbourhood map6 pages6Neighbourhood mapbinaries
Neighbourhood map binaries
Distance1 hop
50 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- ReleaseTerm4
- commitKeyword4
- npmKeyword4
- packageKeyword4
- standaloneKeyword4
- standalone binariesKeyword4
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.