snapm: bump release to 0.5.1

[bmr-cymru]

Resolves: #565

Summary by CodeRabbit

• Release
  • Version 0.5.1 released with distribution fixes, test improvements, new features, and various enhancements.

[coderabbitai]

Walkthrough

Version release bump across documentation, packaging, and module metadata files from 0.5.0 to 0.5.1, including addition of changelog entries in the spec file detailing the release scope.

Changes

Cohort / File(s)	Summary
Version bump (release 0.5.1) doc/conf.py, snapm.spec, snapm/__init__.py	Updated version identifiers from 0.5.0 to 0.5.1 across documentation configuration, package specification, and module metadata. Added changelog entries to spec file documenting the release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

This is a straightforward, homogeneous version bump across configuration and metadata files with no functional logic changes.

Possibly related PRs

• PR #357: Performs similar version metadata updates across the same files (doc/conf.py, snapm.spec, snapm/init.py) for a prior release.

Poem

🐰 Hop! The version bumps to point-one,
Through configs, specs, and code—a unified run,
Snapm now wears 0.5.1 with pride,
Changelog records the journey inside! 📝✨

Pre-merge checks and finishing touches

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately summarizes the primary change: bumping the snapm package version from 0.5.0 to 0.5.1. It is concise, specific, and directly reflects the changeset.
Linked Issues check	✅ Passed	The pull request addresses the linked issue #565 (snapm-0.5.1 release planning) by bumping version numbers across all relevant files (doc/conf.py, snapm.spec, snapm/init.py) as part of the release preparation.
Out of Scope Changes check	✅ Passed	All changes are in scope: version bumps in documentation, packaging, and module files are directly related to the v0.5.1 release preparation objective outlined in the linked issue.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bmr-0.5.1-release-prep

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0d9cdc6 and a719f28.

📒 Files selected for processing (3)

• doc/conf.py (2 hunks)
• snapm.spec (2 hunks)
• snapm/__init__.py (1 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: bmr-cymru
Repo: snapshotmanager/snapm PR: 357
File: snapm.spec:132-134
Timestamp: 2025-09-10T23:42:35.992Z
Learning: The snapm project maintainer bmr-cymru prefers scripted version bumping as part of the snapm-x.y.z-release-prep workflow rather than automated regex-based parsing for version synchronization across files.

Learnt from: bmr-cymru
Repo: snapshotmanager/snapm PR: 541
File: snapm/manager/_mounts.py:174-197
Timestamp: 2025-10-22T20:06:54.993Z
Learning: For snapshotmanager/snapm follow-up requests from bmr-cymru, create a GitHub issue with label "enhancement", set/ensure a "type: Task" label, and assign it to bmr-cymru. Include backlinks to the PR and the discussion comment in the issue body.

Learnt from: bmr-cymru
Repo: snapshotmanager/snapm PR: 357
File: snapm.spec:132-134
Timestamp: 2025-09-10T23:42:35.992Z
Learning: In the snapm project, changelog entries in snapm.spec are auto-generated from git log using `git log --oneline v0.4.0..v0.5.0 | sed  -e 's/^[a-f0-9]* /- /' -e 's/%//'` and should not be manually edited to avoid rewriting git history.

📚 Learning: 2025-09-10T23:42:35.992Z

Learnt from: bmr-cymru
Repo: snapshotmanager/snapm PR: 357
File: snapm.spec:132-134
Timestamp: 2025-09-10T23:42:35.992Z
Learning: In the snapm project, changelog entries in snapm.spec are auto-generated from git log using `git log --oneline v0.4.0..v0.5.0 | sed  -e 's/^[a-f0-9]* /- /' -e 's/%//'` and should not be manually edited to avoid rewriting git history.

Applied to files:

• snapm/__init__.py
• snapm.spec
• doc/conf.py

📚 Learning: 2025-09-10T23:42:35.992Z

Learnt from: bmr-cymru
Repo: snapshotmanager/snapm PR: 357
File: snapm.spec:132-134
Timestamp: 2025-09-10T23:42:35.992Z
Learning: The snapm project maintainer bmr-cymru prefers scripted version bumping as part of the snapm-x.y.z-release-prep workflow rather than automated regex-based parsing for version synchronization across files.

Applied to files:

• snapm/__init__.py
• snapm.spec

📚 Learning: 2025-08-27T20:27:47.299Z

Learnt from: bmr-cymru
Repo: snapshotmanager/snapm PR: 0
File: :0-0
Timestamp: 2025-08-27T20:27:47.299Z
Learning: The upstream snapm.spec file in the snapm project only aims to work on centos-stream9 through Fedora rawhide. Downstreams maintain their own copies and adapt as needed.

Applied to files:

• snapm.spec

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (45)

• GitHub Check: rpm-build:centos-stream-9-x86_64
• GitHub Check: rpm-build:fedora-rawhide-x86_64
• GitHub Check: rpm-build:epel-9-x86_64
• GitHub Check: rpm-build:fedora-43-x86_64
• GitHub Check: rpm-build:fedora-41-x86_64
• GitHub Check: rpm-build:centos-stream-10-x86_64
• GitHub Check: rpm-build:fedora-42-x86_64
• GitHub Check: rpm-build:fedora-42-x86_64
• GitHub Check: rpm-build:fedora-rawhide-x86_64
• GitHub Check: rpm-build:epel-9-x86_64
• GitHub Check: rpm-build:fedora-43-x86_64
• GitHub Check: rpm-build:centos-stream-9-x86_64
• GitHub Check: rpm-build:centos-stream-10-x86_64
• GitHub Check: rpm-build:fedora-41-x86_64
• GitHub Check: rpm-build:fedora-rawhide-x86_64
• GitHub Check: rpm-build:centos-stream-10-x86_64
• GitHub Check: rpm-build:fedora-42-x86_64
• GitHub Check: rpm-build:fedora-43-x86_64
• GitHub Check: rpm-build:centos-stream-9-x86_64
• GitHub Check: rpm-build:epel-9-x86_64
• GitHub Check: rpm-build:fedora-41-x86_64
• GitHub Check: rpm-build:fedora-43-x86_64
• GitHub Check: rpm-build:fedora-41-x86_64
• GitHub Check: rpm-build:epel-9-x86_64
• GitHub Check: rpm-build:centos-stream-10-x86_64
• GitHub Check: rpm-build:centos-stream-9-x86_64
• GitHub Check: rpm-build:fedora-42-x86_64
• GitHub Check: rpm-build:fedora-rawhide-x86_64
• GitHub Check: virt_tests (uefi, lvm, fedora41)
• GitHub Check: virt_tests (bios, lvm, fedora41)
• GitHub Check: virt_tests (bios, lvm-thin, centos-stream10)
• GitHub Check: virt_tests (uefi, lvm-thin, centos-stream10)
• GitHub Check: virt_tests (uefi, lvm-thin, fedora42)
• GitHub Check: virt_tests (uefi, lvm-thin, centos-stream9)
• GitHub Check: virt_tests (uefi, lvm, centos-stream10)
• GitHub Check: virt_tests (uefi, lvm, fedora42)
• GitHub Check: virt_tests (uefi, lvm-thin, fedora41)
• GitHub Check: virt_tests (bios, lvm-thin, fedora41)
• GitHub Check: virt_tests (bios, lvm-thin, centos-stream9)
• GitHub Check: virt_tests (bios, lvm, fedora42)
• GitHub Check: virt_tests (uefi, lvm, centos-stream9)
• GitHub Check: virt_tests (bios, lvm-thin, fedora42)
• GitHub Check: virt_tests (bios, lvm, centos-stream10)
• GitHub Check: virt_tests (bios, lvm, centos-stream9)
• GitHub Check: python-basic-tests

🔇 Additional comments (5)

doc/conf.py (1)

76-76: LGTM: Version updated consistently in documentation configuration.

The release variable and commented html_title reference have been correctly updated to reflect version 0.5.1.

Also applies to: 150-150

snapm/__init__.py (1)

14-14: LGTM: Package version correctly bumped to 0.5.1.

The __version__ string has been properly updated and is consistent with the version changes in other files.

snapm.spec (3)

4-4: LGTM: RPM spec version correctly updated to 0.5.1.

The version field is consistent with the version bumps in doc/conf.py and snapm/__init__.py.

---

144-171: LGTM: Changelog entries added for 0.5.1 release.

The changelog follows the project's standard format and appears to be auto-generated from git commit history as per the established workflow. The date and release version are correct.

Based on learnings

---

4-4: All version references successfully updated to 0.5.1 — no further action required.

Verification confirms the version string updates are complete and consistent:

• snapm/__init__.py: __version__ = "0.5.1" ✓
• setup.cfg and pyproject.toml: Both correctly reference the module's dynamic version attribute ✓
• snapm.spec: Version set to 0.5.1 on line 4 ✓

No stale 0.5.0 references remain in active code. The only occurrences of "0.5.0" are in the snapm.spec changelog section, which appropriately documents the historical 0.5.0 release and is correct.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo yum install -y dnf-plugins-core on RHEL 8
• sudo dnf install -y dnf-plugins-core on Fedora
• dnf copr enable packit/snapshotmanager-snapm-585
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.