Repository navigation
Release 1.0.0, the first stable release - #91
Merged
Merged
Conversation
Users ran 1.0.0-rc2 on Fedora 45 beta, Ubuntu 26.10, Bazzite, Arch Linux and CachyOS and found it stable, so 1.0.0 is that code with the new About window. The version, the package metadata (the metainfo release is stable), the release notes, the README, the roadmap and the decision log move to 1.0.0. The release becomes the repository's latest release, and the release workflow also tests the packages on Ubuntu 26.10 and Fedora 45. The landing page uses Forum for headings, callouts and highlights and Inter for the text, and links each file of the 1.0.0 release and the add-ons installer for direct download. The README links the same files and the add-ons AppImage. GitHub Packages has no registry for plain files, so the add-ons workflow also publishes the AppImage itself in its Maven registry, where the package page lists the file, beside the OCI artifact and the addons release. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ATdR4yNUHcELGaDGS9BCG9
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Brahm · project thread
Users tested 1.0.0-rc2 on Fedora 45 beta, Ubuntu 26.10, Bazzite, Arch Linux and CachyOS, and it worked. This PR turns it into 1.0.0, the final release.
Version and packages
Cargo.tomlandCargo.lockgo to1.0.0. The.deb,.rpmand pacman package are plain1.0.0, so they replace1.0.0~rc2/1.0.0rc2on update.1.0.0release of typestable, which the About window shows as What's New, and the "release candidate" sentence is gone. The rpm changelog, PKGBUILD andpackaging/release-notes.md(the release body) are updated too.release.yml: a release without a suffix is markedmake_latest, and the package tests also run onubuntu:26.10andfedora:45, the systems users tested on.ubuntu:latestis 26.04 andfedora:latestis 44.README and landing page
docs/roadmap.mdanddocs/decisions.md(P13, P14).Add-ons on GitHub Packages
GitHub Packages has no registry for plain files. Its container registry already holds the AppImage, but as an OCI artifact. The addons workflow now also publishes the AppImage itself in GitHub's Maven registry as
io.github.brahm:corerules-community-addons:VERSION:x86_64@AppImage. That package's page listscorerules-community-addons-VERSION-x86_64.AppImagefor download. The workflow checks the uploaded file against the build. A Maven version can't be replaced, so a version is published once. The OCI artifact and theaddonsrelease stay as they are, and the release stays the direct download link.After merge
v1.0.0to publish the release.addons.ymlchanged. It publishes add-ons 1.0.0 on ghcr.io, on the Maven registry and on theaddonsrelease.Generated by Claude Code