jeff-fichtner/Snackbyte Release Flow

Turn an environments.json manifest into a release flow: resolve-env ("is this pushed branch a deployable environment?") and derive-version ("what version tag does this push get?"). Creates a tag only — never a commit or branch push.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jul 6, 2026
License
None

Pinned Snippet

workflow.ymlSHA-pinned
uses: jeff-fichtner/snackbyte-release-flow-action@fe81fdce941402ea39eea7456800dd0b6c641796 # v1.0.0

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
branchThe pushed branch to resolve against the manifest.no${{ github.ref_name }}
manifestPath to the environments manifest (relative to the checkout).no./environments.json
major-minorOverride for the MAJOR.MINOR version line (build-id strategy only). When empty, the Action reads package.json's version and uses its first two components. Ignored when version-strategy is package-json.no""
version-strategyHow the version number is chosen. 'build-id' (default) = global monotonic, tree-reused PATCH, for deployable apps. 'package-json' = tag the package.json version verbatim, for published libraries (intentional SemVer).nobuild-id
namedescription
is-env"true" if the branch is a deployable environment, else "false".
versionThe derived MM.P version (set only for an environment push).
tagThe derived vMM.P<suffix> tag (set only for an environment push).