-
Notifications
You must be signed in to change notification settings - Fork 12
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
build(release): merge main into dev #38
Conversation
the helm chart release action must be run before tag creation, but release please is still useful for automated changelog creation
Release-As: 0.1.0-rc-2
…--v0.1.0-rc.2 chore(v0.1.0-rc.2): release 0.1.0-rc-2
chore(v0.1.0-rc.2): merge release into main
- helm chart: don't change postgres secret from dependency at helm upgrade - helm-test: enable upgradeability check and set check-version-increment for ct lint to false
Reviewed-By: Evelyn Gurschler <[email protected]>
for release workflow to be triggered
bump version update readme
Release-As: 0.1.0-rc.3
* chore(v0.1.0-rc.3): release 0.1.0-rc.3 * chore: fix changelog --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Evelyn Gurschler <[email protected]>
chore(v0.1.0-rc.3): merge release into main
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. |
Quality Gate passedIssues Measures |
Description
Merge the latest changes to the dev branch
Why
To have the latest changes available in the dev branch