package

No definition

The passages, in corpus order

16 files.

TermVersion1

  • line 6…of the key. The tool itself carries a version too, written in the footer of the site and in the build block of the model, and every published package shares it.

TermGlobal check1

  • line 7…en the two types, or a title shared with an entity of another type. The lint package lists them as GLOBAL_CHECKS (E-LINK-BROKEN, E-META-REL, I-TERM-HOMONYM, W-L…

TermLocal check1

  • line 7…f the model: encoding, frontmatter, identifiers and internal links. The lint package lists them as LOCAL_CHECKS. For these checks the linter and the build produ…

TermLinter1

  • line 6… request, applies the safe fixes with --fix, and runs the same way as an npm package, a standalone binary, a GitHub action, a GitLab component, the container im…

TermRelease1

  • line 6…gesets: the merge commit is tagged v<major>.<minor>.<patch>, every published package is packed and attached to a release with the standalone binaries of the lin…

TermPlugin1

  • line 6A package that contributes to the tool through a versioned API: a reader for a file format, a converter, a source of entities such as a contract importer, an in…
Show the 10 other files

TermPreset1

  • line 7The package named concordance, which depends on the core and on every official plugin and enables them all. It is what an integrator installs; the core alone is…

APICanonical model1

  • line 9…s the sources. It is described by model.schema.json, published with the core package, and holds five blocks plus the two neighbourhoods: build, the only dated b…

APIPlugin API1

  • line 9…a manifest validated by the published schema, plugin.schema.json of the core package, which is a JSON schema and not a contract the build imports, so this note …

DecisionCore, plugins, preset1

  • line 8…rs, importers, viewers and heavy projections are plugins declared in the configuration. The unscoped concordance package is the preset that enables all of them.

DecisionGPL-3.0-or-later1

  • line 8Every package of the tool is published under the GNU General Public License, version 3 or later, and a licence inventory of the dependencies is regenerated and …

ProcessOnboarding a repository1

  • line 11Install the command line: the published package with npm, the container image with a container engine, or a checkout of the repository built once; all three run…

ProcessPublishing the wiki1

  • line 7…, every workflow builds the command line from a checkout of the tool's repository, the interim form of the pipelines the guide gives with the published package.

ProcessRelease8

  • line 7How a version of the tool is cut and what it publishes: the npm packages under one shared version number and the preset, the container image tagged with the ver…
  • line 7…h, a release whose notes are the changelog entries with the tarball of every package and the standalone binaries as assets, and the mirrors of the GitHub action…
6 other passages
  • line 7…same version. Every form of one version names the same commit: the tag, the packages on npm, the image, the action, the component and the pre-commit hook. Versi…
  • line 11Every pull request that changes a published package carries a changeset: the packages it touches, the bump and one sentence for the changelog; the pipeline refu…
  • line 11…very pull request that changes a published package carries a changeset: the packages it touches, the bump and one sentence for the changelog; the pipeline refus…
  • line 14…z>, builds the standalone binaries on three platforms, packs every published package, verifies the licence inventory, writes the checksums and creates the relea…
  • line 14…rballs, the checksums and the inventory as its assets; the manifest of every package has been checked on every change to ship neither its sources, nor its tests…
  • line 17The release notes are completed with the npm page of every package and the digest of the image when it is on the registry; the action repository and the compone…

Business ruleLinter and build parity1

  • line 8…ecks the linter computes in --scope repo, listed as LOCAL_CHECKS by the lint package (E-ENCODING, E-FM-INVALID, E-ID-DUP, E-ID-INVALID, E-LINK-BROKEN), concorda…

ScreenGallery index1

  • line 15The theme comes from the registry the build uses: --theme names a plugin package or the path of its module, repeated at will, the last one winning a slot; witho…

What we know

Occurrences
23
Files
16
Spaces
Glossary, Specifications

No declared property: there is no file for this word.

Maybe the same thing

Expressions close in form and context. A lead, not a claim.

See the neighbourhood map6 pages6Neighbourhood mappackage

Neighbourhood map package

Distance1 hop

Types
existing pageword without a note

50 neighbours in total, more than the map shows.

The 6 neighbourstextual equivalent

Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.