chore: merge next release#908
Conversation
This pull request refactors the current branching model to improve development and address several challenges associated with using staging as the default base branch for pull requests. With this update, main will serve as the base branch for pull requests, containing active development changes, while releases will be triggered upon merging pull requests into the newly created release branch.
…>=6.21.0,<6.130.9 (#906)
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| run: | | ||
| pip install --upgrade pip wheel | ||
| pip install 'commitizen ==4.1.0' | ||
| pip install 'commitizen ==4.5.0' |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
| run: | | ||
| pip install --upgrade pip wheel | ||
| pip install 'commitizen ==4.1.0' | ||
| pip install 'commitizen ==4.5.0' |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
| run: | | ||
| pip install --upgrade pip wheel | ||
| pip install 'commitizen ==4.1.0' | ||
| pip install 'commitizen ==4.5.0' |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
3 participants
No description provided.