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

feat!: Remove deprecated execution message (#54) #56

Merged
merged 2 commits into from
Oct 10, 2024

Conversation

primeapple
Copy link
Collaborator

This is the feature branch of the first breaking changes. All commits here are already approved.

Do NOT squash merge this PR.

Also wait for #48

This removes the execution message and adds a comment to the README on
how to readd them via Autocommands.

Also I implemented a function to handle breaking changes. It can later
be used for #48

This merges in a feature branch. I would like to collect all potential
breaking changes there until we can release it all together in a version
1.0.0

---------

Co-authored-by: okuuva <[email protected]>
@primeapple primeapple self-assigned this May 18, 2024
Copied over from #48

---------

Co-authored-by: Sergey Kochetkov <[email protected]>
@primeapple
Copy link
Collaborator Author

primeapple commented Oct 9, 2024

Hey @okuuva I'd now rebase this branch onto main and then create tag v1.0.0 on the head of main. The two commits on this branch will then be on main. Is this fine for you?

Sorry for this taking forever.

@okuuva
Copy link
Owner

okuuva commented Oct 10, 2024

Sounds good to me!

@primeapple primeapple merged commit 95544f7 into main Oct 10, 2024
2 checks passed
@primeapple primeapple deleted the first-breaking-changes branch October 10, 2024 19:56
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.

2 participants