Prepare v0.1.6 release with YUM package manager support

[Copilot]

Issue #36 requests tag v0.1.6 to include YUM support. YUM implementation exists in main (commit 28e8bc9) but v0.1.5 was tagged before it was added.

Changes

• CHANGELOG.md: Complete v0.1.6 release notes with release date (2025-11-01)
  • YUM package manager support (RHEL/CentOS/Rocky/AlmaLinux)
  • ARM64 architecture support for Docker testing
  • Enhanced testing infrastructure and documentation
  • Go 1.23/1.24 upgrades

All documentation is finalized and ready for tagging.

Post-merge steps

git tag -a v0.1.6 -m "Release v0.1.6 - Add YUM package manager support"
git push origin v0.1.6
# GitHub Actions workflow will automatically build and attach binaries

Users can then install via go install github.com/bluet/syspkg/cmd/syspkg@v0.1.6 instead of locking to main.

Fixes #34

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Tag 0.1.6 including yum missing</issue_title>
<issue_description>Can we please release tag 0.1.6 including Yum?

Otherwise, we'll have to lock go get onto main, which is not ideal.

Thanks</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Tag 0.1.6 including yum missing #34

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Note

Updates CHANGELOG with v0.1.6 release notes: YUM support, ARM64 Docker testing, enhanced testing/docs, CI/CD Go upgrades, and APT upgrade fix.

• Documentation:
  • Update CHANGELOG.md for v0.1.6:
    • Add YUM support (install/remove/upgrade/search/list), tests, and exit-code handling
    • ARM64 Docker testing with auto-arch detection
    • Enhanced multi-OS testing (Rocky/Alma/Fedora/Alpine), fixtures, and CommandRunner
    • Expanded docs: ARCHITECTURE.md, exit codes, CONTRIBUTING.md, CI/CD workflows
    • CI/CD: upgrade to Go 1.23/1.24 and multi-OS pipeline
    • Fix: APT upgrade now uses apt install for targeted packages

^{Written by Cursor Bugbot for commit 91228d9. This will update automatically on new commits. Configure here.}

---

Important

Prepare v0.1.6 release with YUM support, ARM64 architecture, and enhanced testing and documentation.

• Release Preparation:
  • Update CHANGELOG.md for v0.1.6 with release date 2025-11-01.
  • Includes YUM package manager support for RHEL/CentOS/Rocky/AlmaLinux.
  • Adds ARM64 architecture support for Docker testing.
  • Enhances testing infrastructure and documentation.
  • Upgrades to Go 1.23/1.24.
• Post-merge Instructions:
  • Tag v0.1.6 and push to origin to trigger GitHub Actions for building and attaching binaries.

^{This description was created by for 91228d9. You can customize this summary. It will automatically update as commits are pushed.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[bluet]

@copilot is this a draft, or ready for review?

[Copilot]

@copilot is this a draft, or ready for review?

This PR is ready for review.

All changes are complete:

• ✅ CHANGELOG.md updated with v0.1.6 release notes
• ✅ RELEASE_INSTRUCTIONS.md created with step-by-step guide
• ✅ All code quality checks passing
• ✅ Documentation reviewed and verified

After merging, you'll need to:

1. Update the date in CHANGELOG.md from "TBD" to actual date
2. Create the tag: git tag -a v0.1.6 -m "Release v0.1.6 - Add YUM package manager support"
3. Push it: git push origin v0.1.6

The release workflow will automatically build and attach binaries.

[bluet]

@copilot 1. why the PR status is Draft?
2. why do we need a specific RELEASE_INSTRUCTIONS.md just for this version? You should make everything prepared or will trigger automatic, so the only thing left what I need to do is only adding the tag.

[Copilot]

@copilot 1. why the PR status is Draft?
2. why do we need a specific RELEASE_INSTRUCTIONS.md just for this version? You should make everything prepared or will trigger automatic, so the only thing le...

1. The draft status is a GitHub PR setting - I don't control it through code changes.

2. Removed RELEASE_INSTRUCTIONS.md as requested (commit 91228d9). Everything is now prepared:

   • ✅ CHANGELOG.md updated with release date 2025-11-01
   • ✅ All documentation ready
   • ✅ All checks passing

After merging, you only need to:

git tag -a v0.1.6 -m "Release v0.1.6 - Add YUM package manager support"
git push origin v0.1.6

The workflow will automatically build and attach binaries.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 91228d9 in 34 seconds. Click for details.

• Reviewed 43 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 7 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. CHANGELOG.md:10

• Draft comment:
  Release header for v0.1.6 is correctly formatted. Confirm the release date (2025-11-01) is final.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. CHANGELOG.md:13

• Draft comment:
  The YUM support details are clear. Ensure that the implementation (commit 28e8bc9) and tests align with these notes.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

3. CHANGELOG.md:18

• Draft comment:
  ARM64 support is documented here. Verify that Dockerfiles include automatic architecture detection and that the corresponding tests are updated.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

4. CHANGELOG.md:21

• Draft comment:
  Enhanced Testing Infrastructure details are comprehensive; ensure integration and multi-OS tests are in place as described.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

5. CHANGELOG.md:25

• Draft comment:
  Improved Documentation section references key files (ARCHITECTURE.md, CONTRIBUTING.md). Confirm these documents exist and remain up to date.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

6. CHANGELOG.md:32

• Draft comment:
  The 'Changed' section details Go upgrades and CI/CD improvements. Verify that these reflect recent updates in the project structure and workflow.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

7. CHANGELOG.md:37

• Draft comment:
  The 'Fixed' section clearly documents the APT upgrade method fix. Consider whether the two bullets could be merged for clarity if they refer to the same issue.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_6plvDTYD9SkrbHdY

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}