equisoft-actions/Resolve nodejs application metadata
Resolve common application metadata like the application version or whether it is publishable (by our standards). Git "history" must be available for this action to perform well. A typical usage will look like so: ```yaml steps: - name: Checkout uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7 with: fetch-depth: 0 - name: Find application metadata id: metadata uses: .github/actions/nodejs-application-metadata ```
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| release-branch | Branch allowed for release. Default to the repository default branch. | no | — |
| hotfix-branch-prefix | Branch prefix allowed for hotfix. Tags on this branch will set is_hotfix to true. Make sure the branch is available with git fetch (if fetch-depth is unset or > 0) ```yaml - name: Fetch hotfix branch (for action-metadata commit check) run: | git fetch --no-tags --prune --depth=1000 origin '+refs/heads/release/*:refs/remotes/origin/release/*' ``` | no | — |
Outputs
| name | description |
|---|---|
| publishable | 'true' if this build can publish artifacts. Only builds from the default branch can be published. 'false' if this build should not publish its artifacts. |
| is-hotfix | 'true' if this build is a hotfix |
| is-release | 'true' if this build should create a full release. Only 'publishable' builds can be released. A release is typically triggered from a tag matching the 'v1.2.3', semver format. 'false' if this build should not create a full release. |
| version | The resolved version that the current build can use. The version will usually be semver compliant only for releases. |
| npm-tag | NPM tag to publish package with. Defined on only if publishable Released semver tag are qualified as 'latest' Default branch is qualified 'snapshot' |