-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Following HEAD: breaking changes on main #453
Comments
Repository owner
locked and limited conversation to collaborators
Jan 22, 2022
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Repository owner
unlocked this conversation
May 28, 2024
This comment has been minimized.
This comment has been minimized.
#1054 |
#1055 removed support for yadm |
#1056 removed
|
GaetanLepage
added a commit
to nix-community/nixvim
that referenced
this issue
Jun 23, 2024
GaetanLepage
added a commit
to nix-community/nixvim
that referenced
this issue
Jun 23, 2024
GaetanLepage
added a commit
to nix-community/nixvim
that referenced
this issue
Jun 23, 2024
GaetanLepage
added a commit
to nix-community/nixvim
that referenced
this issue
Jun 24, 2024
Repository owner
deleted a comment from
blueowlgreenfish
Jun 24, 2024
Repository owner
locked and limited conversation to collaborators
Jun 24, 2024
Repository owner
unlocked this conversation
Jan 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue tracks changes that may require users to update configuration or expectations.
Only intentional breaking changes are mentioned here.
We follow the Conventional Commits specification, so breaking changes will always be marked with a !. If you use packer.nvim, it'll highlight breaking changes on update.
If you find breaking changes too disruptive to your workflow, the recommendation is to follow the
release
tag which should point to the most recent release.The text was updated successfully, but these errors were encountered: