Commit graph

8 commits

Author SHA1 Message Date
Brian Flad
aa7ea2f4b9
.github/workflows: Add GitHub Release title to workflow (#312)
Reference: https://github.com/hashicorp/ghaction-terraform-provider-release/issues/44

```console
$ gh release create --help
Create a new GitHub Release for a repository.

A list of asset files may be given to upload to the new release. To define a
display label for an asset, append text starting with `#` after the file name.

If a matching git tag does not yet exist, one will automatically get created
from the latest state of the default branch.
Use `--target` to point to a different branch or commit for the automatic tag creation.
Use `--verify-tag` to abort the release if the tag doesn't already exist.
To fetch the new tag locally after the release, do `git fetch --tags origin`.

To create a release from an annotated git tag, first create one locally with
git, push the tag to GitHub, then run this command.

When using automatically generated release notes, a release title will also be automatically
generated unless a title was explicitly passed. Additional release notes can be prepended to
automatically generated notes by using the notes parameter.

USAGE
  gh release create [<tag>] [<files>...]

FLAGS
      --discussion-category string   Start a discussion in the specified category
  -d, --draft                        Save the release as a draft instead of publishing it
      --generate-notes               Automatically generate title and notes for the release
      --latest                       Mark this release as "Latest" (default: automatic based on date and version)
  -n, --notes string                 Release notes
  -F, --notes-file file              Read release notes from file (use "-" to read from standard input)
      --notes-start-tag string       Tag to use as the starting point for generating release notes
  -p, --prerelease                   Mark the release as a prerelease
      --target branch                Target branch or full commit SHA (default: main branch)
  -t, --title string                 Release title
      --verify-tag                   Abort in case the git tag doesn't already exist in the remote repository
```
2023-02-28 14:25:15 -05:00
dependabot[bot]
525ec9dce5
Bump miniscruff/changie-action from 1.0.0 to 1.0.1 (#311)
Bumps [miniscruff/changie-action](https://github.com/miniscruff/changie-action) from 1.0.0 to 1.0.1.
- [Release notes](https://github.com/miniscruff/changie-action/releases)
- [Changelog](https://github.com/miniscruff/changie-action/blob/main/CHANGELOG.md)
- [Commits](7d8e4c245d...b6d52c80de)

---
updated-dependencies:
- dependency-name: miniscruff/changie-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-27 15:24:43 -05:00
SBGoods
08e201aa90 Checkout the latest commit instead of pulling for remote changes 2023-02-21 15:15:48 -05:00
Selena Goods
0d0e1dd31e
Pin setup-node action to SHA instead of major version
Co-authored-by: Brian Flad <bflad417@gmail.com>
2023-02-21 12:07:05 -05:00
SBGoods
8972b88921 Add job to update package version 2023-02-09 16:48:43 -05:00
SBGoods
a0b152b5df Add steps to update major version tag 2023-02-09 16:39:54 -05:00
SBGoods
eed2545295 Switch to Changie for changelog automation 2023-02-08 15:32:40 -05:00
James Pogran
3672145e4b
Add GitHub automatic release (#173)
This automatically creates a GitHub release when a matching tag is created in this repository.
2022-04-04 09:38:08 -04:00