https://github.com/makstyle119/skills-release-based-workflow
My clone repository
https://github.com/makstyle119/skills-release-based-workflow
Last synced: about 2 months ago
JSON representation
My clone repository
- Host: GitHub
- URL: https://github.com/makstyle119/skills-release-based-workflow
- Owner: makstyle119
- License: mit
- Created: 2023-06-25T15:49:53.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2023-10-01T20:56:53.000Z (over 1 year ago)
- Last Synced: 2025-02-07T16:43:33.514Z (3 months ago)
- Language: JavaScript
- Size: 97.7 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Create a release based workflow
_Create a release based workflow that is built on the foundations of the GitHub flow._
## Step 5: Finalize the release
_Awesome work on the release notes :+1:_
### Finalizing releases
It's important to be aware of the information what will be visible in that release. In the pre-release, the version and commit messages are visible.

### Semantic versioning
Semantic versioning is a formal convention for specifying compatibility. It uses a three-part version number: **major version**; **minor version**; and **patch**. Version numbers convey meaning about the underlying code and what has been modified. For example, versioning could be handled as follows:
| Code status | Stage | Rule | Example version |
| ------------------------------- | ------------- | ---------------------------------------------------------------------- | --------------- |
| First release | New product | Start with 1.0.0 | 1.0.0 |
| Backward compatible fix | Patch release | Increment the third digit | 1.0.1 |
| Backward compatible new feature | Minor release | Increment the middle digit and reset the last digit to zero | 1.1.0 |
| Breaking updates | Major release | Increment the first digit and reset the middle and last digits to zero | 2.0.0 |Check out this article on [Semantic versioning](https://semver.org/) to learn more.
### Finalize the release
Now let's change our recently automated release from _draft_ to _latest release_.
### :keyboard: Activity: Finalize release
1. In a separate tab, go to the **Releases** page for this repository.
- _Tip: To reach this page, click the **Code** tab at the top of your repository. Then, find the navigation bar below the repository description, and click the **Releases** heading link._
1. Click the **Edit** button next to your draft release.
1. Ensure the _Target_ branch is set to `main`.
1. Click **Publish release**.
1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.---
Get help: [Post in our discussion board](https://github.com/skills/.github/discussions) • [Review the GitHub status page](https://www.githubstatus.com/)
© 2023 GitHub • [Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) • [MIT License](https://gh.io/mit)