@@ -15,30 +15,13 @@ Thank you for wanting to contribute to this project. With your help we can ensur
1515
1616## Deployment
1717
18- ### 1. Publish New Release
19-
20- 1 . Navigate to [ actions's releases] ( https://github.com/2Toad/actions/releases ) .
21- 2 . Click "Draft a new release":
22- - ** Choose a tag** : enter version (e.g., ` v1.1.0 ` ) and click "Create new tag"
23- - ** Target** : ` main `
24- - ** Previous tag** : ` auto `
25- - ** Release title** : (e.g., ` 1.1.0 ` )
26- - ** Description** : click the "Generate release notes"
27- - [x] ** Set as the latest release**
28- 3 . Click "Publish release".
29-
30- 2 . ### Update Major Version Tag
31-
32- After publishing a new release, update the major version tag using the following CLI commands:
33-
34- 1 . Ensure you're on the main branch and have the latest changes:
35- ``` bash
36- git checkout main
37- git pull origin main
38- ```
39- 2 . Update the major version tag:
40- ``` bash
41- git tag -fa v1 -m " Update v1 tag to latest release" v1.1.0
42- git push origin v1 --force
43- ```
44- Replace ` v1 ` with the appropriate major version (e.g., v2) and ` v1.1.0 ` with the newest release (e.g., v2.0.3).
18+ 1 . Navigate to the [ Actions tab] ( https://github.com/2Toad/actions/actions )
19+ 2 . Select the "Deploy to Prod" workflow
20+ 3 . Click "Run workflow".
21+ 4 . Enter a version number using semantic versioning (e.g., ` 1.1.0 ` ).
22+ 5 . Click "Run workflow" to start the process.
23+
24+ This automated workflow will:
25+ - Create a new release with the specified version number
26+ - Generate release notes
27+ - Update the corresponding major version tag (e.g. ` v1 ` will point to v1.x)
0 commit comments