Skip to content
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

ci: let updates of production dependencies trigger a release #45

Merged
merged 2 commits into from
Jul 9, 2024

Conversation

basti1302
Copy link
Member

No description provided.

Make dependabot use a "fix" prefix when updating production
dependencies, so that semantic-release/commit-analyzer creates a new
release when production dependencies have been updated on main.
@basti1302 basti1302 requested a review from a team as a code owner July 9, 2024 09:35
@basti1302 basti1302 enabled auto-merge (rebase) July 9, 2024 09:35
This is mostly because a release is triggered potentially with every
push to the main branch, and we do not want to push individual releases
everytime we merge a dependabot PR for one single dependency.
@basti1302 basti1302 force-pushed the dependency-updates-should-trigger-a-release branch from f4179b1 to b0b9d3d Compare July 9, 2024 09:37
Copy link

sonarqubecloud bot commented Jul 9, 2024

@basti1302 basti1302 merged commit 79ef4bc into main Jul 9, 2024
9 checks passed
@basti1302 basti1302 deleted the dependency-updates-should-trigger-a-release branch July 9, 2024 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant