Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release): make releases with with github actions user #15

Merged
merged 1 commit into from
Nov 8, 2024
Merged

chore(release): make releases with with github actions user #15

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .release-please.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,9 @@
"type": "refactor"
}
],
"draft": true,
"draft-pull-request": true,
"include-component-in-tag": false,
"include-v-in-tag": true,
"packages": {
".": {
Expand Down
3 changes: 2 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,8 @@ We use [`release-please`][release-please] to create releases. This will maintain
a draft pull request with the changes needed to bump the version and update the
changelog, updated with the changes since the last release.

Releasing should be as simple as merging that pull request. Check that a GitHub
Releasing should be as simple as undrafting and merging that pull request, then
double-checking the created release and publishing it. Check that a GitHub
release, a tag, and the Docker releases were created.

### Use conventional commit messages
Expand Down
Loading