Skip to content

Releases

ELECTRO-HOBBY-3D-UPDATER 0.1.6 - The pins of the four updaters are their latest releases, the project documents and a register of requirements with their tests, and safer names and workflows

Choose a tag to compare

@JuanenRac JuanenRac released this 21 Nov 04:47
2cc1ab5
  • The dashboard notifier reads the repository, ref and commit from environment variables: the workflow no longer expands them inside the shell script, so the step has nothing to inject into and passes the workflow security scan.

  • A project name that starts with a hyphen or has odd characters is refused before anything runs: install and update stop with exit code 64 instead of passing it to the sub-updater, where it could be read as an option.

  • A pin by an abbreviated commit id is reported, and fails the check before a release: tools/check_pins.py --strict needs the whole 40-character commit.

  • The version read from the repository is limited in size (one mebibyte) like the other network reads.

  • The Real hardware row of Project status is no longer green: it said "not applicable" with a green light, the only hardware row in green; it uses the light the family uses for a row that does not apply (in the eight languages).

  • The validation of the manifest, versions and documents is the shared one of the suite: the CI calls the reusable validation workflow (pinned by commit) instead of carrying its own copy of the steps; the checks of this repository stay as they were.

  • The pins of the four updaters are their latest releases (HYDRA-UMC 0.5.9, URTC 0.3.2, A.R.M.O.R. 0.2.4, EH3D 0.1.1), so a new installation brings the repositories and versions published since.

  • Requirements with identifiers and tests that name them: docs/REQUIREMENTS.md is the register of what the program must do, one row for each capability with an identifier (EHUP-001 on), its state (planned, prototype, implemented or validated), how far it is (done, partial, pending or blocked), its evidence and the test that shows it; a capability that is not written names the test that will show it. tests/test_requirements.py reads the table and fails when a test does not exist, when a state does not agree with the progress or the evidence, when docs/STATUS.md does not say the same numbers, when a README does not link the documents or when a document holds a date or a private reference. The five documents of the family (docs/SCOPE.md, docs/REQUIREMENTS.md, docs/STATUS.md, docs/NOT_YET.md and AGENTS.md) are in the repository and are linked from the eight READMEs.