Repository navigation
ci(release): adopt releasaurus with CalVer and the phenix-apps contribution workflow - #3
Open
adamsrnmsu wants to merge 1 commit into
Open
adamsrnmsu wants to merge 1 commit into
adamsrnmsu wants to merge 1 commit into
Conversation
…bution workflow Align Parseus with the release and contribution conventions of sandialabs/sceptre-phenix-apps. Release: releasaurus.toml uses CalVer (version_type %Y.%m.%d), links each changelog entry to its PR, and keeps the python release type so the version in pyproject.toml is bumped directly. release.yml follows the apps layout (push to main plus a dry-run workflow_dispatch, fork guard, pinned action). Tags made with GITHUB_TOKEN do not trigger ci.yml, so the job that records the new tag and a verify job running the verify-version and verify-release-compose checks on it are kept (skipped on dry runs). CHANGELOG.md is now generated: the Keep a Changelog preamble and the empty [Unreleased] heading are dropped and 1.0.0 keeps its content under a releasaurus-style heading. Contribution workflow: add commits.yml (Conventional Commit subject check), codespell.yml and .codespellrc, a PR template, issue templates (bug form fitted to Parseus), and CONTRIBUTING.md (type-description branch names, rebase-merged PRs, generated changelog, GPLv3). Fix the typos codespell found. docs/DEVELOPMENT.md and docs/MANAGEMENT.md now describe CalVer releases. PEP 440 normalizes 2026.11.02 to 2026.11.2 in package metadata (parseus.__version__) only; the tag check, compose image tags, bundle name, manifest and upgrade comparison all read the raw pyproject string and were verified with a leading-zero date version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 12, 2026
Merged
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.
Description
Aligns Parseus with the release and contribution conventions of sandialabs/sceptre-phenix-apps. This supersedes #1 (branch renamed to the
type-descriptionconvention).version_type = "%Y.%m.%d", tags likev2026.11.02) and PR links in the changelog.release_type = "python"is kept: a dry run confirmed it bumps[project].versioninpyproject.tomlto a date version.release.ymlfollows the apps layout (push tomainplus aworkflow_dispatchdry-run input, fork guard, pinned action SHA, concurrency group, named steps,DRY_RUNon both commands). The Parseus-specific part stays: tags created withGITHUB_TOKENdo not triggerci.yml, so one step records the new tag and averifyjob runs theverify-versionandverify-release-composechecks on it (skipped on dry runs).CHANGELOG.mdis now generated and not hand-edited. The Keep a Changelog preamble and the empty[Unreleased]heading are dropped; 1.0.0 keeps its content under a releasaurus-style heading.commits.yml(Conventional Commit subjects),codespell.yml+.codespellrc, a PR template, issue templates (bug form fitted to Parseus: host OS, Docker/Compose version, browser, Parseus version, install method), and.github/CONTRIBUTING.md(GPLv3,type-descriptionbranches, rebase-merge, generated changelog).otand four precise words (thur,earch,tabel,unparseable) are ignored.docs/DEVELOPMENT.mdanddocs/MANAGEMENT.mdnow describe CalVer/releasaurus releases instead of manual SemVer tagging.Related Issues/PRs
Type of Change
fix)feat)docs)refactor)chore)Checklist
Testing
actionlint(rhysd/actionlint) clean on the new/changed workflows (it reports one pre-existing shellcheck note inci.yml, untouched);zizmor --offlineclean onrelease.yml,commits.yml,codespell.yml.codespell(2.4.3, same as the pinned action) passes on the repo.releasaurus release-pr --dry-run --local-path(rgonnella/releasaurusimage, local clone plus onefeat:commit):release_type = "python"accepts CalVer; next version computed as2026.11.12(the UTC date of the run), updatingpyproject.tomlandCHANGELOG.md.version = "2026.11.02",parseus.__version__reads2026.11.2(pip normalizes package metadata), but nothing depends on it matching:tests/test_version.pyandtests/test_manage_parseus_lib.pypass (113 pass;test_build_paths_uses_var_lib_for_manifest_statefails on macOS because/varresolves to/private/var, and fails the same way without the version change). Theverify-versionshell snippet passes for tagv2026.11.02; theverify-release-composesnippet passes with compose renderingparseus:2026.11.02in both compose files; the upgrade downgrade guard parses02as 2, so2026.11.02vs2026.11.10compare correctly. The tag, image tags, bundle name and install manifest all use the rawpyproject.tomlstring.Additional Notes
v1.0.0already exists onmain. No release PR appears until there are commits after it; this PR is one (acicommit), so the next push tomainopens a release PR for the date of that push, e.g.v2026.11.12, which is a plain jump from1.0.0to a date version (CalVer sorts above1.0.0). Hold or close that release PR if you do not want a release yet. The changelog heading is a plain tag link for 1.0.0 since there is no earlier release to compare..github/CODEOWNERSis not included. Maintainers may want one, and then a CODEOWNERS step and checklist line in the contributing guide and PR template.commits.ymlcheck requires Conventional Commit subjects on every PR commit.🤖 Generated with Claude Code