-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Upgrade programs.taskwarrior
to use taskwarrior3
#5310
Comments
since the I don't think a breaking change should be imposed on users without notice |
Thanks, @aktaboot. I see your point. I'm not sure how this is handled usually. Would you just wait for some time and then change it later, or how would you proceed? |
Yes, eventually it will roll out, but really unsure when. |
Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting. If you are the original author of the issue
If you are not the original author of the issue
Memorandum on closing issuesDon't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort. |
What about |
@mdietrich16 for taskwarrior3, you can just set |
Closes: nix-community#5310 Link: NixOS/nixpkgs#303632 Link: nix-community#5782
Support taskwarrior3 migration, following the approach in [1] to avoid breaking changes. [1]: NixOS/nixpkgs#303632 Closes: nix-community#5310 Link: nix-community#5782
Support taskwarrior3 migration, following the approach in [1] to avoid breaking changes. [1]: NixOS/nixpkgs#303632 Closes: nix-community#5310 Link: nix-community#5782
Support taskwarrior3 migration, following the approach in [1] to avoid breaking changes. [1]: NixOS/nixpkgs#303632 Closes: nix-community#5310 Link: nix-community#5782
Support taskwarrior3 migration, following the approach in [1] to avoid breaking changes. [1]: NixOS/nixpkgs#303632 Closes: nix-community#5310 Link: nix-community#5782
Support taskwarrior3 migration, following the approach in [1] to avoid breaking changes. [1]: NixOS/nixpkgs#303632 Closes: nix-community#5310 Link: nix-community#5782
Support taskwarrior3 migration, following the approach in [1] to avoid breaking changes. [1]: NixOS/nixpkgs#303632 Closes: nix-community#5310 Link: nix-community#5782
Support taskwarrior3 migration, following the approach in [1] to avoid breaking changes. [1]: NixOS/nixpkgs#303632 Closes: nix-community#5310 Link: nix-community#5782
Support taskwarrior3 migration, following the approach in [1] to avoid breaking changes. [1]: NixOS/nixpkgs#303632 Closes: nix-community#5310 Link: nix-community#5782
Currently,
programs.taskwarrior.package
defaults topkgs.taskwarrior
. A new version of Taskwarrior was released, so we should update the default topkgs.taskwarrior3
.The text was updated successfully, but these errors were encountered: