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.

Sign up for GitHub

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

Jump to bottom

build: release on main branch #1907

Merged
merged 1 commit into from
Dec 19, 2022
Merged

build: release on main branch #1907

merged 1 commit into from
Dec 19, 2022

Conversation

markov00
Copy link
Member

@markov00 markov00 commented Dec 19, 2022 •
edited

Summary

Semantic-release doesn't have main in their default branches rule. Adding to allow releasing on this branch.
Solves the following error on release:

This test run was triggered on the branch main, while semantic-release is configured to only publish from 38.0.x, 39.x, 40.0.x, 40.1.x, 40.x, 46.0.x, 49.x, 50.2.x, next, alpha, therefore a new version won’t be published.

See https://semantic-release.gitbook.io/semantic-release/usage/configuration and semantic-release/semantic-release#1581

@markov00 markov00 added :ci :build Build tools / dependencies ci:skip Skip all build checks labels Dec 19, 2022
nickofthyme
nickofthyme approved these changes Dec 19, 2022
View reviewed changes
Copy link
Collaborator

@nickofthyme nickofthyme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@markov00 markov00 merged commit f70676a into elastic:main Dec 19, 2022
@markov00 markov00 deleted the 2022_12_19-release_on_main branch December 19, 2022 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@nickofthyme nickofthyme nickofthyme approved these changes

Assignees
No one assigned
Labels
:build Build tools / dependencies ci:skip Skip all build checks :ci
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@markov00 @nickofthyme