sergehuber opened a new pull request, #45: URL: https://github.com/apache/unomi-site/pull/45
## Summary ASF policy requires a project's download page to link to the current source release of each of its products, with its signature, checksum and the KEYS file (https://infra.apache.org/release-download-pages.html), and release announcements must link to that page. The download page did not list any Apache Unomi tracker release. - `_data/unomi.yml`: a `tracker` entry with the current release: 1.5.0, 2024-09-06, and its JIRA version. - `download.html`: an "Apache Unomi tracker" card, below the Unomi one: - the source package through `closer.lua`; - its PGP signature and SHA512 checksum, and `KEYS`, on `https://downloads.apache.org` (as the policy asks for new links); - the npm package, described as built from that source release; - the release notes, and the archive for older releases. - The verification section shows the tracker commands too (`gpg --verify`, `shasum -a 512 -c`). When tracker 2.0.0 (and 1.6.0 on the 1.x line) are released, only `unomi.yml` needs to change, as described in the tracker's RELEASE.md. ## Test plan - [x] Built with `docker run --rm --volume="$PWD:/site" bretfisher/jekyll build`: the page shows "Apache Unomi tracker 1.5.0" with its links - [x] Every link answers 200 (closer.lua, `.asc`, `.sha512`), and the `.sha512` file works with `shasum -a 512 -c` 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
