-
Notifications
You must be signed in to change notification settings - Fork 135
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
New Release #1345
Comments
There is no new way. The maintainers are just short staffed and didn't have time to cut a release. In the meantime, you can you use this repo as the dependency and composer require-dev the dev-main branch or a particular commit hash if you include the GitHub repo as a source in your composer.json file. |
I can understand that maintainers dont have the time to cut the release. I also just read in some other PR that the next release would be the next major version. So i would need to pick the 2.0.x branch i guess if i want to use right now the "latest" version? I saw there is already a 3.0.x branch. |
@DanielBadura you can savely ignore the branches 2.0.x and 3.0.x. Right now they are just placeholders for when the release is ready. Main is this the branch with the most current changes. But you also have to be aware that the main branch already contains BC. |
Just realised, cannot use the commit with deptrac-shim version which i wanted to use.. 😓 |
Hello there 👋
I tried to use the composer collector #1174 in my new project where i wanted to use deptrac and realised that this i not included in the last release. I'm using the shim version and the laste release is from december 2022. Is there a new way recommended to use deptrac?
The text was updated successfully, but these errors were encountered: