Skip to content

Release 1.0.0, the first stable release - #91

Merged
brahm merged 1 commit into
mainfrom
claude/project-thread-b9yw0m
Oct 24, 2026
Merged

brahm merged 1 commit into
mainfrom
claude/project-thread-b9yw0m

Conversation

@brahm

@brahm brahm commented Oct 24, 2026

Copy link
Copy Markdown
Owner

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.toml and Cargo.lock go to 1.0.0. The .deb, .rpm and pacman package are plain 1.0.0, so they replace 1.0.0~rc2 / 1.0.0rc2 on update.
  • The metainfo gets a 1.0.0 release of type stable, which the About window shows as What's New, and the "release candidate" sentence is gone. The rpm changelog, PKGBUILD and packaging/release-notes.md (the release body) are updated too.
  • release.yml: a release without a suffix is marked make_latest, and the package tests also run on ubuntu:26.10 and fedora:45, the systems users tested on. ubuntu:latest is 26.04 and fedora:latest is 44.

README and landing page

  • README: the release candidate notice becomes the 1.0.0 notice, with the distributions it was tested on. The roadmap step moves to 1.0. Installing now has a direct link to every 1.0.0 file, plus the add-ons installer. The Community add-ons section puts the AppImage link first.
  • Landing page: Forum for headings, callouts and highlighted info, Inter for body text. The download section has a direct link and install command for each 1.0.0 package and for the add-ons installer, plus PKGBUILD, SHA256SUMS and a "Tested by players on" callout.
  • docs/roadmap.md and docs/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 lists corerules-community-addons-VERSION-x86_64.AppImage for 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 the addons release stay as they are, and the release stays the direct download link.

After merge

  1. Run the Packages workflow with tag v1.0.0 to publish the release.
  2. The addons workflow runs on the merge, because addons.yml changed. It publishes add-ons 1.0.0 on ghcr.io, on the Maven registry and on the addons release.

Generated by Claude Code

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
@brahm brahm self-assigned this Oct 24, 2026
@brahm
brahm merged commit 5492aab into main Oct 24, 2026
28 checks passed
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.

2 participants