15 Releases 24 Tags

RSS Feed

• v1.1.17 21a20ce7ca

  Compare

  <think>

  coissac released this 2026-06-23 07:00:34 +00:00 | 29 commits to main since this release

  Here's a thinking process:

  1. Analyze User Input:

  • Tool: obikmer (a Rust kmer genomics tool)
  • Format: Concise markdown release notes
  • Tone: Technical and direct
  • Source Material: Single commit message:
    • feat: automate release workflow and add optional NUMA support
    • Details: Refactor Gitea release workflow (dedicated create-release job, shared release ID, eliminates redundant inline creation)
    • Details: Update Makefile to auto-generate annotated tags with AI-derived markdown release notes from recent commits
    • Details: Add optional numa feature to obikindex that gates hwlocality behind conditional compilation, providing graceful UMA fallback when disabled
    • Version: Bump obikmer to v1.1.17

  2. Identify Key Technical Changes:

  • CI/CD: Gitea release workflow refactored (dedicated job, shared release ID)
  • Build/Release: Makefile updated for automated annotated tagging + AI-generated markdown notes
  • Feature: Optional numa feature in obikindex
  • Dependency/Compilation: hwlocality gated behind conditional compilation (numa feature)
  • Fallback: Graceful UMA fallback when NUMA is disabled
  • Version: v1.1.17

  3. Determine Structure for Release Notes:
     Standard concise markdown release notes structure:

  # obikmer v1.1.17
  
  ## Changes
  - **CI/CD**: ...
  - **Build/Release**: ...
  - **Features**: ...
  - **Dependencies/Compilation**: ...
  

  Or just bullet points under categories like ### Features, ### CI/CD & Build, etc. Keep it tight.

  4. Draft - Section by Section (Mental Refinement):
     Version: v1.1.17
     CI/CD: Refactored Gitea release workflow to use a dedicated create-release job with a shared release ID, removing redundant inline creation logic.
     Build/Release: Updated Makefile to automatically generate annotated tags and populate markdown release notes from recent commits via AI.
     Features: Added optional numa feature to obikindex. Gates hwlocality behind conditional compilation. Implements graceful UMA fallback when NUMA support is disabled.

  Let's make it more technical and direct, aligning with Rust/genomics tool conventions:

  # obikmer v1.1.17
  
  ## Summary
  Automated release pipeline improvements and optional NUMA memory architecture support for `obikindex`.
  
  ## Changes
  - **CI/CD**: Refactored Gitea release workflow to introduce a dedicated `create-release` job with a shared release ID, eliminating redundant inline creation steps.
  - **Build Automation**: Updated Makefile to automatically generate annotated tags and populate markdown release notes from recent commits via AI.
  - **Features**: Added optional `numa` feature to `obikindex`.
  - **Compilation**: Gated `hwlocality` dependency behind conditional compilation (`numa` feature).
  - **Fallback Logic**: Implemented graceful UMA fallback when NUMA support is disabled.
  

  5. Check against Constraints:

  • Concise markdown? Yes.
  • Technical and direct? Yes, uses precise terminology (conditional compilation, annotated tags, shared release ID, UMA fallback).
  • Strictly based on commit messages? Yes, covers all points without adding external info.
  • Format matches request? Yes.

  Let's refine it to be even more concise and aligned with typical Rust crate release notes:

  # obikmer v1.1.17
  
  ## Changes
  - **CI/CD**: Refactored Gitea release workflow to use a dedicated `create-release` job with a shared release ID, removing redundant inline creation logic.
  - **Release Automation**: Updated Makefile to automatically generate annotated tags and populate markdown release notes from recent commits via AI.
  - **Features**: Added optional `numa` feature to `obikindex`.
  - **Compilation**: Gated `hwlocality` behind conditional compilation (`numa` feature).
  - **Fallback**: Implemented graceful UMA fallback when NUMA support is disabled.
  

  This looks solid. It's direct, technical, covers every point from the commit message, and uses standard markdown release note formatting. I'll output this. No extra fluff. Matches "technical and direct" requirement. All constraints met. Proceed.
  One minor adjustment: Combine compilation/fallback into one bullet for tighter conciseness, as they're closely related.

  • Compilation & Fallback: Gated hwlocality behind the optional numa feature; provides graceful UMA fallback when NUMA is disabled.

  Final check of the prompt: "Write concise markdown release notes for obikmer (a Rust kmer genomics tool). Be technical and direct. Base them strictly on these commit messages:"
  The single commit message contains all the info. I'll structure it cleanly.

  Output matches the refined version.✅
  Proceeds.
  Output Generation.
  [Self-Correction/Verification during thought]

  • Check version: v1.1.17 (explicitly stated)
  • Check tool name: obikmer
  • Check format: markdown release notes
  • Check tone: technical and direct
  • Check source fidelity: strictly based on provided text
    All good. I will generate it now.
    Structure:

  obikmer v1.1.17

  Changes

  • CI/CD: ...
  • Build Automation: ...
  • Features & Compilation: ...
  • Fallback: ...
    Actually, combining is better for conciseness. I'll stick to the refined version. It's tight.✅
    Output matches response.
    Proceeds.
    [Output Generation] -> See response.
    (Self-Correction/Note during drafting): I should ensure the formatting strictly follows standard release note conventions but remains concise. I'll use a clean, direct structure without unnecessary headings if possible, or keep them minimal. The prompt says "concise markdown release notes", so I'll keep it tight.

  Final text:

  # obikmer v1.1.17
  
  ## Changes
  - **CI/CD**: Refactored Gitea release workflow to introduce a dedicated `create-release` job with a shared release ID, eliminating redundant inline creation logic.
  - **Build Automation**: Updated Makefile to automatically generate annotated tags and populate markdown release notes from recent commits via AI.
  - **Features**: Added optional `numa` feature to `obikindex`.
  - **Compilation**: Gated `hwlocality` behind conditional compilation (`numa` feature).
  - **Fallback**: Implemented graceful UMA fallback when NUMA support is disabled.
  

  This is exactly what's needed. Direct, technical, strictly derived from the commit. No extra fluff. Ready.
  Output matches.✅
  [Done]
  Self-Correction/Verification during output gen prep: The prompt says "Base them strictly on these commit messages:" (plural in prompt, but only one provided). I'll just use the one. All good.
  Output matches response.✅
  Proceeds.
  [Output Generation] -> Proceeds
  

  • CI/CD: Refactored Gitea release workflow to introduce a dedicated create-release job with a shared release ID, eliminating redundant inline creation logic.
  • Build Automation: Updated Makefile to automatically generate annotated tags and populate markdown release notes from recent commits via AI.
  • Features: Added optional numa feature to obikindex.
  • Compilation: Gated hwlocality behind conditional compilation (numa feature).
  • Fallback: Implemented graceful UMA fallback when NUMA support is disabled.

  Downloads

  • Source Code (ZIP)
  • Source Code (TAR.GZ)