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

chore: Update changelog after removing legacy filters #1083

Merged
merged 2 commits into from
Sep 12, 2024
Merged

Conversation

vblagoje
Copy link
Member

I ran git-cliff with parameters from github CI runs that failed. Note that most changelogs have this unreleased section while elastic has the actual tag. I wasn't sure what's right here, perhaps you know - I'd guess the actual tag?

@vblagoje vblagoje changed the title Update changelog after removing legacy filters chore: Update changelog after removing legacy filters Sep 12, 2024
@vblagoje
Copy link
Member Author

Yeah, I think we should replace unreleased with actual tag....

@vblagoje vblagoje marked this pull request as ready for review September 12, 2024 14:25
@vblagoje vblagoje requested a review from a team as a code owner September 12, 2024 14:25
@vblagoje vblagoje requested review from davidsbatista and removed request for a team September 12, 2024 14:25
@vblagoje
Copy link
Member Author

Please have a look now @silvanocerza

@vblagoje vblagoje removed the request for review from davidsbatista September 12, 2024 14:26
Copy link
Contributor

@silvanocerza silvanocerza left a comment

Choose a reason for hiding this comment

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

Looks good 👍

@vblagoje vblagoje merged commit ac0c580 into main Sep 12, 2024
21 checks passed
@vblagoje vblagoje deleted the update_changelog branch September 12, 2024 14:50
Amnah199 pushed a commit that referenced this pull request Oct 2, 2024
* Update changelog after removing legacy filters

* Updates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants