2
2
3
3
> Documentation guide based on the releases of ` 1.0.0-beta.5 ` on March 17, 2023.
4
4
>
5
+ > Updated for ` 1.0.1 ` on February 15, 2024.
6
+ > Starting with this version, we have stopped using the ` master ` branch.
7
+ >
5
8
> -kenjis
6
9
7
10
## Changelog
@@ -25,8 +28,8 @@ To auto-generate, navigate to the
25
28
[ Releases] ( https://github.com/codeigniter4/shield/releases ) page,
26
29
click the "Draft a new release" button.
27
30
28
- * Tag: " v1.0.0-beta.5" (Create new tag)
29
- * Target: develop
31
+ * Tag: ` v1.x.x ` (Create new tag)
32
+ * Target: ` develop `
30
33
31
34
Click the "Generate release notes" button.
32
35
@@ -50,42 +53,29 @@ the changelog.
50
53
> been included with their PR, so this process assumes you will not be
51
54
> generating much new content.
52
55
53
- * [ ] Create a new branch `release-1.x.x`
54
- * [ ] Update **src/Auth.php** with the new version number:
55
- `const SHIELD_VERSION = '1.x.x';`
56
- * [ ] Commit the changes with "Prep for 1.x.x release" and push to origin
56
+ * [ ] Run `php admin/prepare-release.php 1.x.x` and push to origin
57
+ * The above command does the following:
58
+ * Create a new branch `release-1.x.x`
59
+ * Update **src/Auth.php** with the new version number:
60
+ `const SHIELD_VERSION = '1.x.x';`
61
+ * Commit the changes with "Prep for 1.x.x release" and push to origin
57
62
* [ ] Create a new PR from `release-1.x.x` to `develop`:
58
- * Title: " Prep for 1.x.x release"
59
- * Description: " Updates version references for ` 1.x.x`." (plus checklist)
63
+ * Title: ` Prep for 1.x.x release`
64
+ * Description: ` Updates version references for 1.x.x.` (plus checklist)
60
65
* [ ] Let all tests run, then review and merge the PR
61
- * [ ] Create a new PR from `develop` to `master`:
62
- * Title: "1.x.x Ready code"
63
- * Description: blank
64
66
* [ ] Merge the PR
65
67
* [ ] Create a new Release:
66
- * Version: " v1.x.x"
67
- * Target: master
68
- * Title: " v1.x.x"
68
+ * Version: ` v1.x.x`
69
+ * Target: `develop`
70
+ * Title: ` v1.x.x`
69
71
* Click the "Generate release notes" button
70
- * Remove "### Others (Only for checking. Remove this category)" section
71
- * Add important notes if necessary
72
- * Add link to Upgrade Guide if necessary
73
- * Check "Create a discussion for this release"
72
+ * [ ] Remove "### Others (Only for checking. Remove this category)" section
73
+ * [ ] Add important notes if necessary
74
+ * [ ] Add link to Upgrade Guide if necessary
75
+ * [ ] Check "Create a discussion for this release"
74
76
* Click the "Publish release" button
75
77
* [ ] Watch for the "docs" action and verify that the user guide updated:
76
78
* [docs](https://github.com/codeigniter4/shield/actions/workflows/docs.yml)
77
- * [ ] Fast-forward `develop` branch to catch the merge commit from `master`
78
- (note: pushing to `develop` is restricted to administrators):
79
- ```console
80
- git fetch origin
81
- git checkout develop
82
- git merge origin/develop
83
- git merge origin/master
84
- git push origin HEAD # Only administrators can push to the protected branch.
85
- ```
86
- **At this point, `master` must be merged into `develop`.** Otherwise, the
87
- GitHub-generated release note from `develop` for the next release will not be
88
- generated correctly.
89
79
* [ ] Publish any Security Advisories that were resolved from private forks
90
80
(note: publishing is restricted to administrators)
91
81
* [ ] Announce the release on the forums and Slack channel
0 commit comments