Repository navigation
ci: auto-tag, release and bump Hermes catalog entry - #10
Merged
Merged
Conversation
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.
Every new
plugin.yamlversion onmainnow gets tagged, released, and a catalog bump PR on NousResearch/hermes-agent, debounced so a burst of merges releases once..github/workflows/release.yml: hourly cron plus manualworkflow_dispatch(forceskips the wait). Concurrency grouprelease,contents: write.scripts/release.sh(git, gh, sed, no other deps):already releasedwhen the version has a GitHub release.waitingwhile HEAD is under 3 h old (DEBOUNCE_HOURS), unless forced.check_refs.py, creates the annotated tag, pushes it, runsgh release create --generate-notes --latest.CATALOG_TOKEN: reuses the open Cloeillechore(plugin-catalog): bump pstackPR on upstream if one exists (else creates a branch on the fork), rewrites onlysha:andversion:ofplugin-catalog/pstack.yaml, and creates or edits the PR with the rule 5 / rule 13 body. Without the token it warns and stops.FORCE=trueon a released version reruns only the catalog step.DRY_RUN=1prints every mutating command.plugin.yamlbumped to 0.3.2.Before the catalog step works: add a
CATALOG_TOKENrepo secret (classic PAT from Cloeille,public_repo).Checked with
DRY_RUN=1against the real repos: released version exits cleanly, recent HEAD waits, forced new version prints tag, release, PUT and PR commands and picks NousResearch/hermes-agent#143777 for reuse.bash -n, shellcheck,check_refs.pyand a YAML parse all pass. No tag, release or catalog change was made for real.