arctic 24.1.1 (new cask), deprecate final-cut-library-manager #170591
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bevanjkay
changed the title
final-cut-library-manager to arctic
bevanjkay
added
the
awaiting maintainer feedback
|
I'm thinking we should add this as a new cask, and deprecate the old one rather than rename. |
|
Yeah I think that's good. I initially thought the old wasn't available anymore, but it seems it is, as a free alternative. |
bevanjkay
force-pushed
the
bump-arctic-24.1.1-19-20240403132247
branch
from
489789c to
a25cf3a
Compare
bevanjkay
changed the title
final-cut-library-manager to arctic
p-linnane
approved these changes
Apr 4, 2024
p-linnane
removed
the
awaiting maintainer feedback
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See: https://blog.hedge.video/a-new-home-for-final-cut-library-manager/
The previous download is still available for now, so renaming may not be the best option.
We could deprecate the old instead.