Skip to content

Prepare 1.5.1 with the catalog descriptions and a more exact README - #14

Merged
stefan-azentrius merged 1 commit into
mainfrom
prepare-1.5.1
Oct 23, 2026
Merged

stefan-azentrius merged 1 commit into
mainfrom
prepare-1.5.1

Conversation

@stefan-azentrius

Copy link
Copy Markdown
Contributor

The catalog changes of #12 and #13 reach the servers only with a release; this prepares 1.5.1 (VERSION, CHANGELOG.md).

README:

  • Update Gaps and Security Monitor release only a .deb so far.
  • The digest GitHub reports for an asset is compared when GitHub reports one.
  • The signing key has no passphrase and does not expire; only file permissions protect it.
  • azentrius-packages add puts packages in without the checks: a way out for root on the server, not the normal way in.
  • A new add-on also needs server/setup.sh run again on the server, since the hourly sync runs the copy of the tool that setup.sh installed.

The catalog changes of #12 and #13 reach the servers only with a release; this prepares 1.5.1 (`VERSION`, `CHANGELOG.md`).

README:
- Update Gaps and Security Monitor release only a `.deb` so far.
- The digest GitHub reports for an asset is compared when GitHub reports one.
- The signing key has no passphrase and does not expire; only file permissions protect it.
- `azentrius-packages add` puts packages in without the checks: a way out for root on the server, not the normal way in.
- A new add-on also needs `server/setup.sh` run again on the server, since the hourly sync runs the copy of the tool that `setup.sh` installed.
@stefan-azentrius
stefan-azentrius merged commit 629c6d0 into main Oct 23, 2026
5 checks passed
@stefan-azentrius
stefan-azentrius deleted the prepare-1.5.1 branch October 23, 2026 14:25
stefan-azentrius added a commit that referenced this pull request Oct 23, 2026
## What and why

Host Settings 0.1.0 is released ([Azentrius/cockpit-host-settings
v0.1.0](https://github.com/Azentrius/cockpit-host-settings/releases/tag/v0.1.0):
`.deb` and `.rpm`, `SHA256SUMS`, build provenance from its own release
workflow). This lists it the way #11 listed Security Monitor:

- `server/azentrius-packages.py`: `Azentrius/cockpit-host-settings` in
`REPOS`, so the sync takes its releases with the same checks as every
add-on.
- `repository/azentrius.xml`: a component in step with the add-on's
metainfo (`de.azentrius.host_settings`, `cockpit-host-settings`,
launchable `host-settings`; name, summaries and descriptions word for
word).
- README table and `server/index.html`: "on each server that should send
messages". Its releases carry an `.rpm`, so no "Debian and Ubuntu only".
- `VERSION` 1.6.0 and its `CHANGELOG.md` section.

#14 (1.5.1) was merged while this was open; `main` is merged in:
`VERSION` 1.6.0, the changelog has 1.6.0 above 1.5.1, the README keeps
#14's changes.

After the merge, for servers: a release of `azentrius-repository` 1.6.0
(the catalog ships in that package) and `server/setup.sh` again on
public-host, since the hourly sync runs the copy of the tool that
`setup.sh` installed.

## How tested

- [x] `tools/check-catalog.py repository/azentrius.xml`: catalog ok, six
add-ons
- [x] The new component against
`packaging/de.azentrius.host_settings.metainfo.xml` of Host Settings:
name, summaries, descriptions and launchable equal
- [x] `server/azentrius-packages.py` parses
- [x] Job `test` and CodeQL green in CI (push and pull request, after
`main` was merged in)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant