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

Jump to bottom

docs: bump versions in DEVELOPMENT.md #650

Merged
merged 1 commit into from Dec 9, 2022
Merged

docs: bump versions in DEVELOPMENT.md #650

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 6 additions & 6 deletions DEVELOPMENT.md
View file
Open in desktop
Expand Up @@ -20,9 +20,9 @@ name: End-to-end tests
on: [push]
jobs:
cypress-run:
runs-on: ubuntu-20.04
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/checkout@v3
# use specific commit pushed to GitHub
- uses: cypress-io/github-action@2a1baeb
```
Expand All @@ -34,22 +34,22 @@ You can use [cypress-gh-action-example](https://github.com/bahmutov/cypress-gh-a
**For pull request reviewers:**

1. When merging a pull request, squash all commits into one.
1. Make sure the commit subject and body follow [semantic commit convention](https://semantic-release.gitbook.io/semantic-release/#commit-message-format). I prefer simplicity:
1. Make sure the commit subject and body follow [semantic commit convention](https://semantic-release.gitbook.io/semantic-release/#commit-message-format). For instance, keeping it simple:

```text
feat: added new parameter
fix: fixed a bug
```

If you need to bump major version, mark it as breaking change in the body of the commit's message like:
If you need to bump the major version, mark it as breaking change in the body of the commit's message like:

```text
fix: upgrade dependency X

BREAKING CHANGE: requires Node 8 to run
BREAKING CHANGE: requires minimum Node.js 14 to run
```

3. New versions of this action will be released automatically by the CI, see [.github/workflows/main.yml](.github/workflows/main.yml). This will create a new [GitHub release](https://github.com/cypress-io/github-action/releases) and will update the current `/v1` branch. Thus every user that use `- uses: cypress-io/github-action@v2` will be using the new version automatically.
3. New versions of this action will be released automatically by the CI, see [.github/workflows/main.yml](.github/workflows/main.yml). This will create a new [GitHub release](https://github.com/cypress-io/github-action/releases) and will update the current `/v5` branch. Thus specifying `- uses: cypress-io/github-action@v5` selects the new version automatically.

## Updating the latest version in GitHub Marketplace

Expand Down