-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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.
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
Hotfix 4.1.7 #5556
Hotfix 4.1.7 #5556
Conversation
docs: add Security advisory in CHANGELOG.md
docs: minor addition to changelogs/v4.1.6.rst and upgrade_416.rst
Update modified Kint files in `ThirdParty`
fix: BaseConnection::getConnectDuration() number_format(): Passing null to parameter
Fix: Debug toolbar selectors
docs: improve upgrade instructions
docs: add upgrade instruction in upgrade_416.rst
Fix: Toolbar. ciDebugBar.showTab() context.
Refactor Database Collector display
Replaced with FILTER_SANITIZE_FULL_SPECIAL_CHARS. Equivalent to calling htmlspecialchars() with ENT_QUOTES set.
Replaced with FILTER_SANITIZE_FULL_SPECIAL_CHARS. Equivalent to calling htmlspecialchars() with ENT_QUOTES set.
fix: replace deprecated FILTER_SANITIZE_STRING
What I did:
Pick up the merge commits. 67d00b3 #5553
Create #5555 and merge. Gereate CHANGELOG.md from Note: This work flow is not good for changelog auto-generation. Cherry-picked PRs is not included generated changelog for |
#5531 We have a GitHub Action that watches for a new release. It runs a deployment script: CodeIgniter4/.github/workflows/deploy-framework.yml Lines 35 to 36 in 8449d13
That script (https://github.com/codeigniter4/CodeIgniter4/blob/develop/.github/scripts/deploy-framework) copies all the files from the main repo to framework, but then overwrites a few files with the versions in admin/framework/
|
This work flow is not good for changelog auto-generation. Cherry-picked PRs is not included generated changelog for And at the next release, the cherry-picked PRs included in v4.1.7 would probably be included again in auto-generated changelog for |
Since we reformat the changelog manually anyways I don't think that will be a problem, we just need to remember to pull any duplicates! |
@MGatner When we need to release a hotfix, we should create the hotfix branch as soon as possible and merge all the fixes into it. I think it is the better work flow. |
This is for hotfix release. Will be merged into
master
.TODO
After merging
master
) intodevelop
See User Guide, Website, Announcement
https://github.com/codeigniter4/CodeIgniter4/blob/develop/admin/RELEASE.md#user-guide